You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update GOVERNMENT.md to explain that small PRs can be reviewed by only Maintainers, but Maintainers are welcome to ask for the Steering Committee's review for more significant changes → @sreekanthkura7
Update RELEASE.md to detail how we will do semantic versioning going forward: first number update = breaking changes; second number update = specs change; third number update = hotfix (typos, etc.) → @DamianNeurode
Add to README.md that we recommend to start and watch the repository, as well as subscribe to the SfNIRS newsletter to be notified whenever there is a new release → @DamianNeurode
Take down the unused GitHub pages (remove the pages GitHub action), and update the URL of the repo to point to the snirf_specification.md of the latest release → @emiddell
Rename the master branch to dev and create a release branch that will become the default (remember to update GitHub actions) → @HanBnrd
Create a SNIRF Wikipedia page?
Long term actions:
Workflow makeover: instead of creating the specs in markdown and then derive the validator from it, use Pydantic to define the spec with validation and then derive the markdown from it → Pydantic schema validator #181
Following the Steering Committee and Maintainers meeting on 8th July 2026...
Short term actions:
Long term actions:
Finally: