-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instructions for how to update the specification with a BEP #96
Comments
I know there's the BIDS Contributor Guide -- I think we decided against putting this in the starter kit, though I can't quite remember why -- maybe @KirstieJane would know ? Regardless, there's still a lot here that references google docs, and I'm not sure if the whole thing should be converted to Markdown ! |
Indeed the Contributor Guide explains the procedure and has been updated a while ago to mention the need for sending a Pull Request with the BEP in Markdown form. I think it is a great idea to improve the docs - starting from porting Contributor Guide to Markdown and incorporating it into this repo. |
As a first start, how about we add a section to the bids-specification docs for this, and just link to the google doc? |
Sounds good to me! |
Right now it's linked in the text under the table for current BEPs -- would
you think that part should all be moved to its own section ? Or just this
guide ?
…On Mon., Nov. 26, 2018, 22:39 Chris Holdgraf ***@***.*** wrote:
As a first start, how about we add a section to the bids-specification
website for this, and just link to the google doc?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#96 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOUk55USJ2Uuq9lOVw6_EaZf7tgFgVVCks5uzLQLgaJpZM4YzuoC>
.
|
Ahh I see it - IMO those could live in their own separate section so that they show up in the navbar on the left and are more discoverable that way. What if we:
(note that here I'm trying not to make the navbar title something like "BIDS Extensions" because I think it'll confuse people into thinking of "extension" as in "firefox or chrome extension" not as in "modifying the BIDS specification") |
I'd +1 having all of the BEPs (and the guide) as their own section from the navbar ! So that sounds good to me 👍 |
It looks like the links added here aren't rendering correctly :( https://bids-specification.readthedocs.io/en/latest/06-extensions.html |
ahhh I bet it's because of the line break that I added to try and not violate line length limits... |
Should we re-open this issue, @chrisfilo ? |
Is there a place with instructions for how to update the BIDS specification with a new BEP? I think we're ready to go soon with BIDS-iEEG, and wonder if we can use this as an opportunity to improve the docs around contributing to the markdown etc.
The text was updated successfully, but these errors were encountered: