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

Document CoC Team selection process #1297

Closed
1 task done
tobie opened this issue Apr 23, 2024 · 9 comments · Fixed by #1373
Closed
1 task done

Document CoC Team selection process #1297

tobie opened this issue Apr 23, 2024 · 9 comments · Fixed by #1373
Labels
cpc-working-session cross-project-council-agenda TOPIC-code-of-conduct All issues related to the CoC update and process waiting-on-pull-request There's agreement as to what needs to happen, now someone has to do it.

Comments

@tobie
Copy link
Contributor

tobie commented Apr 23, 2024

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

@tobie
Copy link
Contributor Author

tobie commented Jun 11, 2024

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

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

tobie commented Jun 12, 2024

That's a good point, @darcyclarke, slightly tangential to this issue, however. Opened a PR addressing it here: #1318.

@joesepi
Copy link
Member

joesepi commented Jul 9, 2024

Meeting notes:

  • Private session two weeks ago wanting to choose team members but had issues to work through still
  • Working session last week revealed that the process was not broken but the decision/selection is particularly difficult for private reasons.
  • Will work on this more today in private session today

@tobie
Copy link
Contributor Author

tobie commented Aug 6, 2024

CPC call discussion:

  • loose agreement that we'd document a lightweight selection process through a PR

@tobie
Copy link
Contributor Author

tobie commented Aug 12, 2024

Note: don't forget to include updating membership to the [email protected] mailing list in the process.

@tobie
Copy link
Contributor Author

tobie commented Sep 3, 2024

CPC call: this is now waiting on a pull request. Alternatively this could be worked on during a working session.

This also needs to be added to the election calendar.

@tobie
Copy link
Contributor Author

tobie commented Oct 1, 2024

Notes from today's CPC call:

  • Working session
  • Would want to leverage existing election processes as much as possible here as this has proven very effective so far

@tobie
Copy link
Contributor Author

tobie commented Oct 15, 2024

Notes from today's CPC call:

tobie added a commit that referenced this issue Oct 15, 2024
Addresses parts of #1297

---------

Signed-off-by: Joe Sepi <[email protected]>
Co-authored-by: Tobie Langel <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cpc-working-session cross-project-council-agenda TOPIC-code-of-conduct All issues related to the CoC update and process waiting-on-pull-request There's agreement as to what needs to happen, now someone has to do it.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants