Skip to content

Commit 03d29e2

Browse files
authored
Merge pull request #476 from nikomatsakis/governance-2019-12-10
governance wg status update
2 parents 9fb8ddb + 24a1ee1 commit 03d29e2

File tree

2 files changed

+69
-1
lines changed

2 files changed

+69
-1
lines changed

posts/inside-rust/2019-12-03-governance-wg-meeting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
layout: post
33
title: "Governance Working Group Update"
44
author: Nell Shamrell-Harrington
5-
team: The Governance WG <https://github.com/rust-lang/wg-governance>
5+
team: the Governance WG <https://github.com/rust-lang/wg-governance>
66
---
77

88
Hello everyone! Two weeks ago the governance working group met. Here are the large issues we discussed and information on our next meeting.
Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
---
2+
layout: post
3+
title: "Governance Working Group Update"
4+
author: Niko Matsakis
5+
team: the Governance WG <https://github.com/rust-lang/wg-governance>
6+
---
7+
8+
Hello everyone! The governance working group met last week to discuss
9+
writing out a policy for access privileges on our Github
10+
repositories. This blog post summarizes that meeting and also
11+
announces the topic of our next meeting, which takes place on Tuesday,
12+
December 17, 2019 ([calendar event]).
13+
14+
[calendar event]: https://calendar.google.com/event?action=TEMPLATE&tmeid=MnNuZDc0NzkzYTBkcDNzY2FkbWgzNjk3a2hfMjAxOTEyMTdUMjIwMDAwWiBtb3ppbGxhLmNvbV85YzZmYzNsNmJoZzhiY3A4Y2FmcnZrM29mNEBn&tmsrc=mozilla.com_9c6fc3l6bhg8bcp8cafrvk3of4%40group.calendar.google.com&scp=ALL
15+
16+
Also, this week we have a [video recording
17+
available](https://youtu.be/CyYwretwM8E). (We're going to generally
18+
try and record meetings when possible.)
19+
20+
## Next meeting
21+
22+
The next meeting will be discussing project groups and their integration into
23+
the lang team. This is building on a few different posts and ideas:
24+
25+
* XAMPPRocky's draft RFC [clarifying our terminology around working groups](https://github.com/rust-lang/wg-governance/blob/master/draft-rfcs/working-group-terminology.md)
26+
* My [Shepherds 3.0](http://smallcultfollowing.com/babysteps/blog/2019/09/11/aic-shepherds-3-0/) blog post
27+
* The embedded working group's [shepherded projects RFC](https://github.com/rust-embedded/wg/pull/378)
28+
* My recent blog post about [an improved pre-RFC
29+
process](http://smallcultfollowing.com/babysteps/blog/2019/12/03/aic-improving-the-pre-rfc-process/)
30+
31+
## Access rights policy
32+
33+
I'll summarize our conclusions here. Consult the [wg-governance]
34+
repository to find more [detailed minutes] from our conversation.
35+
The key conclusions were:
36+
37+
* Where possible, we should stick to a single org ([`rust-lang`]).
38+
* In particular, team-specific organizations like
39+
[`rust-dev-tools`] and [`rust-community`] ought to be merged
40+
into [`rust-lang`].
41+
* Using a single organization makes it much easier to administrate.
42+
* Note that we've already deprecated the [`rust-lang-nursery`] org
43+
* As an exception, we will for now continue having each domain working group
44+
operate outside of its own org (e.g., [`rust-embedded`]). Those orgs
45+
are quite active and have a diverse membership and we don't want to
46+
disturb that for now.
47+
* However, it would be good if each such org added the `rust-lang-owner` bot
48+
as an owner, so that the rust infra team has access.
49+
* For repositories, we will avoid giving access to individuals, and instead try to
50+
give access only to entities (teams, working groups, etc) that are created and
51+
managed by the Rust [team] repository.
52+
* In general, it is not recommended to give owner or admin access; write access suffices.
53+
* (Unfortunately, read and triage access is often not sufficient for us.)
54+
55+
We also enumerated a number of [action items] to putting this policy
56+
in to practice. We'll be revisiting the topic periodically to check on
57+
progress.
58+
59+
[wg-governance]: https://github.com/rust-lang/wg-governance/
60+
[detailed minutes]: https://github.com/rust-lang/wg-governance/blob/master/minutes/2019.12.03.md
61+
[wg-governance]: https://github.com/rust-lang/wg-governance/
62+
[`rust-dev-tools`]: https://github.com/rust-dev-tools/
63+
[`rust-community`]: https://github.com/rust-community/
64+
[`rust-lang`]: https://github.com/rust-community/
65+
[`rust-lang-nursery`]: https://github.com/rust-lang-nursery/
66+
[`rust-embedded`]: https://github.com/rust-embedded/wg
67+
[team]: https://github.com/rust-lang/team
68+
[action items]: https://github.com/rust-lang/wg-governance/blob/master/minutes/2019.12.03.md#action-items

0 commit comments

Comments
 (0)