[ENH] add advisory group member table #272
Conversation
✅ Deploy Preview for astounding-beignet-8ca2d6 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
I would be happy to participate. I originally contacted Chris about
integrating HED tags into BIDS. At that time the process for modifications
of the BIDS spec was less formalized.
…On Tue, Oct 31, 2023 at 3:35 AM Stefan Appelhoff ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In _data/advisory.yml
<#272 (comment)>
:
> + - name: Marco Castellaro
+ git: marcocastellaro
+
+# - title: Electroencephalography (EEG)
+# leads:
+ - name: Cyril Pernet
+ git: CPernet
+ - name: Stefan Appelhoff
+ git: sappelhoff
+ - name: Robert Oostenveld
+ git: robertoostenveld
+
+# - title: Hierarchical Event Descriptor (HED) Tags
+# leads:
+ - name: Chris Gorgolewski
+ git: chrisgorgo
Even if Chris is with us, I think that @VisLab <https://github.com/VisLab>
would be a great person to additionally include in the BIDS advisory group
for HED tags
—
Reply to this email directly, view it on GitHub
<#272 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJCJOSR7I5N5B2BUN2XXT3YCCZ4RAVCNFSM6AAAAAAUCLNI3WVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTOMBVG4YTANJSGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Co-authored-by: Yaroslav Halchenko <[email protected]>
There was a problem hiding this comment.
in the wake of
and in some way also
it'd be nice to complete this. What kind of help do you need to finish this, @Remi-Gau?
|
We would need to first get confirmation of al the people named there that they are OK to be part of this advisory groups and find replacements if not. |
okay, I'll prepare emails. @ BIDS maintainers --> I'll cc the bids maintenance gmail account so you can check there. |
Co-authored-by: Chris Markiewicz <[email protected]>
There was a problem hiding this comment.
@Remi-Gau I have added all other completed BEPs -- including those that were not merged into the BIDS specification.
We'd need to discuss whether only those leads of "merged BEPs" are eligible for joining the group, or also those leads of BEPs that "found a different end" (e.g., were cancelled, became a tool, merged into another BEP, etc.)
The simplest and least ambiguous solution would indeed be to only accept the former.
I would say only "merged BEPs" as long as this covers things like BIDS stats model, BIDS execution... |
| # - title: BEP018 Genetic information | ||
| # leads: | ||
| - name: Clara Moreau | ||
| git: claramoreau9 |
There was a problem hiding this comment.
@claramoreau9 my email to you bounced unfortunately (I seem to have an old address). May you provide me with a working address, please?
|
Thanks @sappelhoff and @Remi-Gau this looks all good to me - the preview also! |
I don't think so -- once we have let a period of a few business days since the email pass, we can merge this PR. People may then notify us that they want to drop out at any time.
I would not say that we need an upper time limit to being a member of this group, I agree that hopefully this group will stay a stable source of knowledge. People who move on will hopefully then inform us of replacements. |
|
Would suggest we briefly discuss this at our next maintainers meeting before merging. Just to make sure everyone gets an update on this. |
preview
https://deploy-preview-272--astounding-beignet-8ca2d6.netlify.app/governance.html#bids-advisory-group
based on the content of the leads of previously merged beps
need to check that people listed here are ok with it
potentially find replacement otherwise
nice to have