Gerrit

Depends on https://crbug.com/gerrit/10976.

Mentioning the new CM project members page section -from [1]; include direct link to Doc.?

[1] https://gerrit-review.googlesource.com/c/homepage/+/225992/4/pages/site/members.md

Also to consider mentioning our CM ways, to make them transparent alongside the usage of [2]:

[2] https://bugs.chromium.org/p/gerrit/issues/list?q=component:Community

An email to contact the community managers is now available (gerritcodereview-community-managers@googlegroups.com).

[Empty comment from Monorail migration]

[Empty comment from Monorail migration]

[Empty comment from Monorail migration]

@Matthias: Should we post a similar email on repo-discuss to announce the CMM minutes of our last meeting which is now deployed on the Gerrit homepage?
=>
@Marco: I propose to mention that we'll be uploading such notes too, every once in a while, in that first CM post [1] for me to send out soon.
I can simply mention such usage of the News section for posts like ours, that way.
It is otherwise odd to send that post about our first notes before introducing ourselves (and the survey).
Now, if a specific post is noteworthy enough, we can of course post it also to the community mailing list (as ESC does).

Here is the post I propose for your review and once the survey https://crbug.com/gerrit/10979 is done reviewing:

Hi!

So we would like to introduce ourselves as your new Community Managers for Gerrit in 2019! :)
Preliminary activities started already but now is the time for us to become formally introduced.
We are a CM trio for this year's term:
- Edwin (Google),
- Marco (Ericsson) and
- Matthias (SAP).

The Gerrit community managers act as stakeholders for this community and focus on its health.
We are also there to support community processes improvement and ways of working.
Our full names and this new governance role are further detailed under [1], below.
Minutes of our regular trio meetups when newsworthy are posted under [2].

As for our transparent backlog, it can be found under [3].
Sensitive topics are to be privately discussed using [4,5], though.
-This is a group that remains private between the individual community member and us managers.
Everyone is welcome to confidentially share needful feedback with CM (us 3), using that limited group.

We would also like to invite you/every Gerrit community member to fill our first CM survey out, [6].
The terms of that survey can be found under [6].
We need your input to 1. help us initialize and 2. feed the 2019 European Summit Retrospective event with it.
Your individual answers remain private to us managers though, throughout.
-Thanks, and sharing with you all again soon!

[1] https://www.gerritcodereview.com/members.html#community-managers
[2] https://www.gerritcodereview.com/news.html
[3] https://bugs.chromium.org/p/gerrit/issues/list?q=component:Community
[4] gerritcodereview-community-managers@googlegroups.com
[5] https://groups.google.com/forum/#!forum/gerritcodereview-community-managers
[6] TODO: Once ready then made publicly available.

We will also need to persist some of this new CM doc through homepage and/or gerrit markdown changes.

> So we would like to introduce ourselves as your new Community Managers for Gerrit in 2019! :)
> Preliminary activities started already but now is the time for us to become formally introduced.
I'd move this sentence down below list of us three and omit the second half.
> We are a CM trio for this year's term:
I would avoid using an acronym, in this sentence CM can be omitted
> - Edwin (Google),
> - Marco (Ericsson) and
> - Matthias (SAP).

> The Gerrit community managers act as stakeholders for this community and focus on its health.
I don't see us as stakeholders, or do I misunderstand this word ? I'd say foremost our role is,
as we also said in the first meeting minutes, like scrum masters for the Gerrit project and the people
involved with it. We try to identify impediments and look for ways to improve how we collaborate
within the project and also with other projects we depend on, e.g. JGit and Bazel.
> We are also there to support community processes improvement and ways of working.
> Our full names and this new governance role are further detailed under [1], below.
> Minutes of our regular trio meetups when newsworthy are posted under [2].
Link to the first minutes here ?

> As for our transparent backlog, it can be found under [3].
I'd say: Find out our backlog under [3].
> Sensitive topics are to be privately discussed using [4,5], though.
using the mailing list [4,5]
> -This is a group that remains private between the individual community member and us managers.
> Everyone is welcome to confidentially share needful feedback with CM (us 3), using that limited group.
I would avoid "needful", and use community managers instead of an acronym

> We would also like to invite you/every Gerrit community member to fill our first CM survey out, [6].
I think it's not a CM survey but a community survey

> The terms of that survey can be found under [6].
> We need your input to 1. help us initialize and 2. feed the 2019 European Summit Retrospective event with it.
.. the community retrospective scheduled for the 2019 European Gerrit Summit in Gothenburg.
> Your individual answers remain private to us managers though, throughout.
AFAIR we said we don't want to gather email addresses so we should mention that the participants stay anonymous.
> -Thanks, and sharing with you all again soon!
I don't understand this sentence

Thanks. I'm working on a resulting change for review that will consider your comments and further simplifications.

[Empty comment from Monorail migration]

[Empty comment from Monorail migration]

https://gerrit-review.googlesource.com/c/gerrit/+/229952
-related but not core to this Issue.

Edits were made to reflect the following in Monorail: auto-CCs.