Closed KirstieJane closed 6 years ago
I could do that or I could give you write access to https://github.com/bids-standard/bids-specification and bep001 issues could be managed via a dedicated bep001
tag and (optionally) a project board (which spans all repos in the organization - so you could mix spec and validator issues).
What would you prefer?
Sorry for the slow reply @chrisfilo! I'm pretty overwhelmed with all the notifications in the bids-specification repo so it would be nice to keep this one separate as we have the various discussions 😄
Would you mind transferring us to bids-standard
please? (or let me know if I have that power!)
You should have the power (unless some permissions on INCF side are missing). Please let me know if you run into issues.
It would be great if the repo was renamed to bep006
for consistency.
PS It might be good to start planning turning the Google doc into Markdown and opening a PR at bids-specification
Thanks @chrisfilo - I'll give it a bash.
Was the bep006
a typo? Are we no longer bep001
?
Totally fine with changing to lowercase whichever number we are!
yes bep001 Best, Chris
On Wed, Nov 7, 2018 at 10:30 AM Kirstie Whitaker notifications@github.com wrote:
Thanks @chrisfilo https://github.com/chrisfilo - I'll give it a bash.
Was the bep006 a typo? Are we no longer bep001?
Totally fine with changing to lowercase whichever number we are!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/INCF/BEP001/issues/5#issuecomment-436729137, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOkp-uK7wBE4HDp0Sl09XYCfo7fbskpks5usybLgaJpZM4XFeLg .
Phew! I was super confused for a minute there 👾
Done! ✅
Hi @chrisfilo - please could you transfer this repository into the
bids-standard
organisation? Then we're all nicely lined up with the other repositories.If you'd like to re-name it to
bep001
that's totally fine with me (and I don't think @Gilles86 will be super mad...although I've tagged him now to double check!)