Governance Proposal

I made some changes for grammar consistency changing "-ing" and imperative forms.

I emphasized the main duty bullet points with bold formatting and indented the membership key points.

I expanded the DA and CWG to be defined rather than using acronyms.

Kristen Pol → made their first commit to this issue’s fork.

Should the example of "Recruits mentors." be expanded to "Recruits mentors and recommends MCWG membership"?

Thank you for reviewing the charter during DrupalCon, Kristen. I think we can make a merge request into the fork main branch as well by visiting https://git.drupalcode.org/issue/mentoring-3445579/-/merge_requests/new, changing the source branch to 3445579-kristen, changing the Target branch remote to "issue/mentoring-3445579" and branch to "main".

A clear and defined scope for all Mentoring coordination with an effective plan for new members and a documented path

what does this mean?

for all contribution events.

Agreed. I think it should be a complete sentence.

Maybe something like the following..?

"We define a clear and defined scope for coordination of mentoring with an effective plan to join and leave the working group so that the members of the Drupal community understand our process."

The Mentoring Coordinators Working Group applies (?)

Maybe we should clarify "The Mentoring Coordinators Working Group charter applies to its members, the lead coordinators..."?

Responds to inquiries about mentoring to local organizers. (how is this related to initiatives?)

Hmm, maybe the duty is now classified as "Works with the Drupal community"?

#mentoring Slack channel.

I think I did not hash the channel name because it may change in the future. Maybe a change from "the mentoring Slack channel." to "the mentoring Slack channels." or "in real-time communication channels used to organize mentoring activities (e.g. Slack).". I don't think we have any plans to change from Slack though.

I plan to get this done by the end of this week to update the MR

Ugh :( This fell off my radar… not sure if I can review again until my Friday which sounds like it’s too late… I’ll add an alarm from Friday in case it’s not

Honestly, this looks great to me.

Actually, made a couple of tiny language changes, just to make it read better around activities.

Also, changed organising “summits” to “training” as there are many ways to train a mentor.

mradcliffe → credited alisonjo → .

Alison is providing feedback at GovCon 2024.

Reviewing the charter as well as Matthew's suggestions (#7)...

Scope:

I like this (from #7):

The Mentoring Coordinators Working Group charter applies to its members, the lead coordinators

Duties:

First duty in the list, "Organizes contribution events (DrupalCon, DrupalCamps, etc.)":

Runs workshops for first-time contributors at DrupalCons, Camps, and events.

How about:

Runs workshops for first-time contributors at Drupal conferences, camps, and other events.

Third duty, "Maintains the mentoring ecosystem":

Maintains the drupal.org Mentoring project issue queue.

Should this be linked to the Mentoring project (or the actual issue queue)?

Last/fourth duty, I like this, from Matthew (#7) -- "Works with the Drupal community" seems like a fitting rename of this duty.

Membership:

Actively participating in multiple mentoring events and helps them execute well.

The second half of the sentence isn't right, but I haven't figured out how to rephrase yet -- OR, maybe remove the second half, because it's covered in the next line??

Regularly volunteering for contribution mentoring events and help to lead parts of those events(for example, helping with communications at an event, etc...).

So, "Actively participating in multiple mentoring events and helps them execute well." => "Actively participating in multiple mentoring events."

Avoiding the specific "#" makes sense to me (again, #7), and I'd say "in" not "at" -- i.e.

Regularly participates in mentoring meta meetings in mentoring Slack channels.

They bring new ideas, skills
and suggested processes to the team.

How about remove "new," and then just "processes"? -- "They bring ideas, skills, and processes to the team."

-------

I'm thinking about the wording under Vision; I asked a question on Slack during today's meta meeting, will keep thinking.

-------

(Meanwhile, I did a commit with some punctuation and language things.)

I forgot to double-check user names.

A week later than I mentioned I would get to this from the last meeting, I made Alison's and my edits to Kristen's branch, and merged into Chris' main branch.

Partial review, gotta go for now!

-------
(1) Perfect world.....

We define a clear and defined scope for coordination of mentoring with an
effective plan to join and leave the working group so that the members of the
Drupal community understand our process.

We'd not say "define/defined" so close together, and I think we can drop "effective"?

-------
(2) The word "Charter": use capital or lowercase "C" in both instances (right now, it's a mix; maybe the first one is capitalized because it's in a heading; if that's the case, lowercase it, per content style guide → ; if it's actually a proper noun, capitalize it in the first sentence of the Scope section).

-------
(3) Scope, part 1 -- use the group acronym? -- so:

The Mentoring Coordinators Working Group charter applies to

Replace "The Mentoring Coordinators Working Group" with "The MCWG"

-------
(4) Scope, part 2:

The Mentoring Coordinators Working Group charter applies to its members, lead
coordinators listed on Maintainers.txt, and their roles in contribution events,
community work, and planning throughout the year.

Totally might just be me, but! I think it's unclear that the MCWG members are the same as the lead coordinators (and I just ran out of time to attempt a rewrite).