Skip to content
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

[ENH] add advisory group member table #272

Merged
merged 11 commits into from
Mar 21, 2024

Conversation

Remi-Gau
Copy link
Contributor

@Remi-Gau Remi-Gau commented Jan 21, 2023

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

@Remi-Gau Remi-Gau marked this pull request as ready for review January 21, 2023 11:53
@netlify
Copy link

netlify bot commented Jan 21, 2023

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

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 sappelhoff marked this pull request as draft June 21, 2023 20:14
Copy link
Member

@sappelhoff sappelhoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

_data/advisory.yml Outdated Show resolved Hide resolved
_data/advisory.yml Outdated Show resolved Hide resolved
@VisLab
Copy link
Member

VisLab commented Oct 31, 2023 via email

_data/advisory.yml Show resolved Hide resolved
_data/advisory.yml Outdated Show resolved Hide resolved
Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>
Copy link
Member

@sappelhoff sappelhoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

@Remi-Gau
Copy link
Contributor Author

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
Copy link
Member

sappelhoff commented Feb 29, 2024

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 <effigies@gmail.com>
Copy link
Member

@sappelhoff sappelhoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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
Copy link
Contributor Author

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

_data/advisory.yml Outdated Show resolved Hide resolved
_data/advisory.yml Outdated Show resolved Hide resolved
_data/advisory.yml Outdated Show resolved Hide resolved
# - title: BEP018 Genetic information
# leads:
- name: Clara Moreau
git: claramoreau9
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@melanieganz
Copy link
Contributor

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
Copy link
Member

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.

@sappelhoff sappelhoff marked this pull request as ready for review March 11, 2024 15:10
@Remi-Gau
Copy link
Contributor Author

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

Copy link
Contributor

@effigies effigies left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sappelhoff sappelhoff merged commit fe58072 into bids-standard:gh-pages Mar 21, 2024
7 checks passed
@Remi-Gau Remi-Gau deleted the advisory branch April 11, 2024 13:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants