BEP Process WG updates - #831
Conversation
Co-authored-by: Eric Earl <eric.earl@nih.gov>
|
I converted this PR to draft, once you have the visual overview ready we can convert back to open PR |
|
Text reads fine to me @christinerogers, but I feel like I'm missing some context after reading @julia-pfarr 's last comment. |
bendhouseart
left a comment
There was a problem hiding this comment.
Text is fine as mentioned and website looked okay assuming the mermaid charts get rendered later, they don't seem to correct on the preview. But, I realize we do a lot of weird stuff that might not get captured there
|
@julia-pfarr This diagram? (still in draft state, but nearing completion)
|
Yes, I think it would be worth waiting until this figure is complete and then updating all together with this PR. It should be done very soon, no? It was already almost done in Bordeaux... |
| A BEP transitions from one phase to another by passing a review process with the BIDS Maintainers. BEP contributors are welcome to join BIDS Maintainer meetings to schedule or discuss their BEP review status. | ||
| A BIDS Maintainer BEP steward, assigned during the BEP process, will actively guide each BEP team from the point of initial BEP idea review through the process outlined here, to provide feedback and guidance. Review discussions are typically followed with specific feedback on the relevant document (GitHub pull request or Google Doc), or by email if preferred by the BEP leads. | ||
|
|
||
| Please note the [community consultation requirements](FILL IN THE BLANK LINK) at each phase. BEP leads are encouraged to connect with the BIDS Maintainers in case of questions or challenges. The BIDS Maintainers are available to support discussions and facilitate convergence towards inclusive solutions for the BIDS community. |
There was a problem hiding this comment.
can someone insert this link?
There was a problem hiding this comment.
@julia-pfarr I think we should just remove that small sentence. I didn't readily see the "community consultation requirements" anywhere on the website, so I think it might have just been a not-completed idea from @christinerogers in April, left behind on accident. It doesn't lose any value to remove that sentence without a link.
|
I think we should also mention the new BEP community meetings, wdyt? I'm presenting the plan to steering this Thursday and then we can publish it |
Do we still need the mermaid diagram if we use the figure that Eric linked? |
| In rare cases, it may be necessary to update: | ||
|
|
||
| - the BIDS validator to properly validate new content from a BEP; | ||
| - the BIDS website. |
There was a problem hiding this comment.
Is this really so rare? Maybe phrase it as these are deliverables that are done by the maintainers, the required deliverables are mainly responsibility of the BEP team
There was a problem hiding this comment.
@julia-pfarr Was this comment of yours addressed?
|
@neuromechanist @christinerogers @julia-pfarr Just a self-reminder, these are website updates to reflect the current process, and as such I think we should get them in ASAP. The biggest action item here is a final draft of the "current" BEP Process Workflow Diagram, which is mostly complete, but needs one last look-over. Once we have that and include it in this PR, I think we're good here.
I'll finish it off in the next 2-3 weeks.
I think the new BEP community meetings announcement/site page should go in a separate PR.
I think the mermaid charts are for different things, but the most essential thing is the colorful workflow diagram. Ignoring doing updates to the mermaid charts should be fine for this PR. |
|
@christinerogers @julia-pfarr @bendhouseart How's this? I'm satisfied with this being the interim diagram until the new BEP process is established.
|
|
@ericearl do you want to wait for the feedback of the others or should I convert to "ready for review" and merge? Do you want more feedback after this draft PR was converted to "ready for review"? |
|
@julia-pfarr It looks like Mark made some suggestions that can be batched and committed here. After those are included, I think this PR's good to be reviewed/merged. This is the current BEP process. It would be nice for it all to be present on the website instead of just what's there now. |
julia-pfarr
left a comment
There was a problem hiding this comment.
apply suggestions from @markmikkelsen
Co-authored-by: Mark Mikkelsen <mark.mikkelsen@gmail.com>
Co-authored-by: Eric Earl <eric.earl@nih.gov>
Co-authored-by: Mark Mikkelsen <mark.mikkelsen@gmail.com>
+10, I am independently moving away from them specially for public-facing materials. |



First pass based on #770
WIP because committing to / referencing the visual BEP process roadmap breakdown would help this move forward with better clarity.
e.g. I added the
BEP_idealayer in one diagram (to clarify when an idea becomes a draft and gets a BEP number).If anything looks wonky, let me know for quick fixes
📚 Documentation preview 📚: https://bids-website--831.org.readthedocs.build/en/831/