[ENH] add advisory group member table

[Remi-Gau]

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

  • listing of topics (BEPs) each advisory group member is linked to

[netlify]

✅ Deploy Preview for astounding-beignet-8ca2d6 ready!

Name	Link
🔨 Latest commit	8f25c09
🔍 Latest deploy log	https://app.netlify.com/sites/astounding-beignet-8ca2d6/deploys/65ef1ee32c828200086e32c8
😎 Deploy Preview	https://deploy-preview-272--astounding-beignet-8ca2d6.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sappelhoff]

This is pending a BIDS governance amendment that is planned to be put up for election in autumn 2023.

[VisLab]

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: ***@***.***>

[sappelhoff]

in the wake of

• [WIP][ENH] improve guidelines bids-extensions#28

and in some way also

• add technical committee bids-extensions#29

it'd be nice to complete this. What kind of help do you need to finish this, @Remi-Gau?

[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.

[sappelhoff]

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.

[sappelhoff]

@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.

[Remi-Gau]

@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...

[sappelhoff]

@claramoreau9 my email to you bounced unfortunately (I seem to have an old address). May you provide me with a working address, please?

[melanieganz]

Thanks @sappelhoff and @Remi-Gau this looks all good to me - the preview also!
And thanks for the e-mail @sappelhoff but there was no expiration date wrt - if you don't want to be part - let me know by XXX. Is that an issue?
One thing that came to my mind was if there is a time limitation on being part of the BEP Working Group Leads? One is encouraged to participate at least 2 years, but I guess everyone could participate forever? We agree that this group will hopefully keep growing and growing the more BEPs are added and the more people get involved, right?

[sappelhoff]

but there was no expiration date wrt - if you don't want to be part - let me know by XXX. Is that an issue?

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.

One thing that came to my mind was if there is a time limitation on being part of the BEP Working Group Leads?

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.

[Remi-Gau]

Would suggest we briefly discuss this at our next maintainers meeting before merging. Just to make sure everyone gets an update on this.

[effigies]

LGTM: https://deploy-preview-272--astounding-beignet-8ca2d6.netlify.app/governance#bids-advisory-group