search

openjs-foundation / cross-project-council

OpenJS Foundation Cross Project Council
https://openjsf.org/
MIT License
429 stars 149 forks source link

Document CoC Team selection process #1297

Open tobie opened 2 months ago

tobie commented 2 months ago

The CoC Team Charter is voluntarily non-prescriptive when it comes to selecting CoC Team members.

Our plan, discussed in the working session of April 23, is to document a process here as we run the first selection and formalize for next year.

Ideally it's lightweight, and close to other election mechanisms.

Consensus in the work session was to make it consensus-driven rather than an election process (this echoes -1 being a a blocker expressed in prior issues opened on the topic).

### Tasks
- [x] Open an issue to call for self nomination (nominees should clarify whether they want to be primary, secondary, or both, and confirm that they meet the elgibility requirements) (See #1298)
tobie commented 4 weeks ago

Following our private session to nominate CoC Community team members it became apparent that we needed to figure out the selection process before moving forward with the selection itself.

darcyclarke commented 4 weeks ago

@tobie On that note, one thing we should consider (if not already accounted for) is project representation. Given there are only 3 appointments to the CoC Team it would be good to ensure that one project does not represent more then 1 position on that team (excluding alternates). I think adding this stipulation would ensure we don't end up with homogeneous perspectives at multiple levels of governance.

tobie commented 4 weeks ago

That's a good point, @darcyclarke, slightly tangential to this issue, however. Opened a PR addressing it here: https://github.com/openjs-foundation/cross-project-council/pull/1318.

joesepi commented 1 day ago

Meeting notes: