Adding a note about the Github teams to the repository management docs

[youknowriad]

Everything is in the title.

[nerrad]

Good to have something about the teams in the doc. However, based on the description, its appears that the Gutenberg team is just a distinction type team (i.e. you've meaningfully contributed to 2/3 of the project here's a badge). I'm assuming that's not the case, so could the purpose of the Gutenberg team be expanded a bit?

Also, I think there's potential for confusion between the two teams, should the names given the teams be more distinctive?

[youknowriad]

I'm not great at writing docs :). The gutenberg team is also about having access to the repository (labeling, creating branches, avoid working on forks.

I think it's too late to change branches and we also can't avoid "gutenberg" in the team names as the teams are global to the WordPress org.

If anyone is willing to give this a stab and clarify more, please do.

[gziolo]

i.e. you've meaningfully contributed to 2/3 of the project here's a badge

I think the idea is 2 or 3 PRs merged with the help of the contributor to be promoted to member :)

Gutenberg Core team is a subset of Gutenberg team which gives you some additional capabilities. One of them is that you get notified when someone uses (at)WordPress/gutenberg-core. It's a great way to bring the attention of the core team member in PRs or issues which need some technical guidance. The other use case I personally find rarely useful is the ability to force-push PR even when Travis is not green or to push directly to master. There are some justifications (fix broken tests, do Lerna publish) to do it even though in general it's considered a very bad practice.

[chrisvanpatten]

Two small nits but overall nice to have this clarification!

[mapk]

Looks good, Riad! Thanks for writing this up.

[nerrad]

Looks good for now. Let's get this merged.

Changed applied