Bio-Formats ORP charter and roster - #3
Conversation
Triage/write roles are currently left empty, as that reflects current work patterns. Maintainer roles should also reflect current work patterns. The admin roles are set to match the current state of the @ome/formats team in GitHub.
Intentionally omitted the ome-model/ome-model-documentation repositories since those should be covered under a different ORP.
|
The build failure is on trying to check links for https://github.com/ome/data_repo_config, which is understandable as that's not a public repo, but I would still like to be able to link to it here. |
👍 https://github.com/ome/governance/blob/main/.lycheeignore is the new & cool way to skip a link check. 😉 |
|
From an earlier discussion with @joshmoore, my understanding is that the expectation was to have all the ORPs under Should https://www.openmicroscopy.org/governance/projects/ also be updated to include a cross-reference and if yes to which document? |
|
As mentioned, happy to discuss, but when I was creating the URLs |
👍 I think this is now ready for a round of review by the OME Management Group |
|
--include |
|
@joshmoore I think what is happening is that the scc is ignoring this PR. It could/should be included in https://merge-ci.openmicroscopy.org/jenkins/job/WEBSITE-push/ but it is not. Could we add include flag or otherwise make it appear there please ? |
@joshmoore @sbesson @melissalinkert - Note that the above problem has been solved in #4 (comment) - basically teaching Jenkins that this submodule base branch is called This PR is built now successfully on https://snoopycrimecop.github.io/www.openmicroscopy.org/governance/ |
|
Thanks all for fixing the build here while I was away ❤️ Outwith this specific PR, I imagine we will want to not list each file on the main menu but have those under the "Projects Roster" page. I can take care of that separately. |
|
|
||
| - publicly, in GitHub pull requests and issues | ||
| - semi-publicly, in OME project-wide meetings which are [publicly minuted](https://ome-contributing.readthedocs.io/en/latest/team-communication.html#meetings) | ||
| - semi-privately, in dedicated weekly meetings which span the Core Model, |
There was a problem hiding this comment.
Trying to clarify some boundaries, should we say these meetings are for Core developers of these ORPs?
| - publicly, in GitHub pull requests and issues | ||
| - semi-publicly, in OME project-wide meetings which are [publicly minuted](https://ome-contributing.readthedocs.io/en/latest/team-communication.html#meetings) | ||
| - semi-privately, in dedicated weekly meetings which span the Core Model, | ||
| Bio-Formats and NGFF ORPs with minutes accessible to members of the OME Project |
There was a problem hiding this comment.
Possible link to https://www.openmicroscopy.org/teams/ for the list of members of the OME project with access to these minutes? Not this is a decision that goes beyond the scope of this individual ORP
| based on **sustained and substantial contributions**, as well as demonstrated | ||
| reliability in supporting the project. | ||
|
|
||
| ### **3.1 Steward (triage rights)** |
|
|
||
| Individuals with the *Maintain* role are responsible for the ongoing | ||
| development and direction of the project. This includes, in addition | ||
| to responsibilities for the Core Developer (*Write*) role: |
There was a problem hiding this comment.
Do you want this line changed too?
There was a problem hiding this comment.
Yes I would remove the Write mention
Co-authored-by: Sébastien Besson <sbesson@glencoesoftware.com>
4 participants
Written together with @sbesson, and as mentioned to @ome/formats and @erindiel. Feel free to add reviewers if I missed anyone.