From 9394dbee42e7450dffd88014668d5780d6f6b2f4 Mon Sep 17 00:00:00 2001
From: valgrimm <56933147+valgrimm@users.noreply.github.com>
Date: Sun, 31 May 2020 11:58:07 +0200
Subject: [PATCH 1/4] Added description of Project Groups
As based on RFC 2856, as requested in WG Governance meeting of 21 May 2020.
---
src/governance/README.md | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/src/governance/README.md b/src/governance/README.md
index 060b75a54..d31a6539b 100644
--- a/src/governance/README.md
+++ b/src/governance/README.md
@@ -128,6 +128,26 @@ subteam to decide, but:
related to their area. Ideally, this would be done in part via a dashboard
like [the Homu queue](http://buildbot.rust-lang.org/homu/queue/rust).
+## Project Groups
+
+* Definition and rationale
+These groups are dedicated to specific projects within the context of a Rust team. The goal of a project is to build or formalise a community to discuss and work on a particular feature or need in the organisation. Previously a lot of the discussion and iteration for large features would happen in the initial RFC thread, which is especially unwieldly when work on a feature takes months and years.
+
+* Essential characteristics
+Unlike a Rust Team, Project Groups don't have formal decision making power, though often they are charged with creating prototypes and drawing up recommendations, RFCs, or other documents to inform a final decision. They are associated with a parent team and have a charter outlining their scope and goals, appointed lead, team liaison(s), members, an associated repository, and dedicated streams on Zulip or a channel on Discord (ideally the group should use the same platform as their parent team).
+
+* Duration
+Some project groups are are ephemeral, meaning that they are archived once work is complete. Others continue to develop and maintain their project over time. Examples of ephemeral groups focused on a specific feature include [FFI Unwind], [Inline ASM], and [Safe Transmute]. Examples of groups engaged in continual work include [Triage] and [Rustup].
+
+* Charter - This document explains the group's scope and goals, individuals involved, membership requirements, and its relationship to the parent team and community.
+* Liaison - A member from a official Rust team. Acts as a point of contact between the team and the group. Either directly involved or syncing with the group periodically. Able to represent Project Group work in meetings with the Rust team. Maintains awareness of situations where this Project Group's work may intersect with work outside the Project Team. A liaison may also be a lead, but this is not a requirement.
+* Member - Individuals who regularly participate in work of the Project Group. Initial team membership should preferably include people who have already been participating regularly and productively in related work and discussion.
+* Repository - Hosted under the rust-lang organization, includes the charter and instructions for how community members can monitor or participate in the group.
+
+* Lifecycle
+Detailed instructions for forming, running, and archiving groups are provided in the [Project Groups RFC] (https://github.com/rust-lang/rfcs/blob/master/text/2856-project-groups.md).
+
+
## Decision-making
### Consensus
From 499ec4013346cfccb2d2e8dfaa299128f80b2880 Mon Sep 17 00:00:00 2001
From: valgrimm <56933147+valgrimm@users.noreply.github.com>
Date: Sun, 31 May 2020 12:03:17 +0200
Subject: [PATCH 2/4] Link fix
I keep forgetting to remove the space between an inline link and its actual URL. Just fixed this. *facepalm*
---
src/governance/README.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/governance/README.md b/src/governance/README.md
index d31a6539b..93d6259a1 100644
--- a/src/governance/README.md
+++ b/src/governance/README.md
@@ -137,7 +137,7 @@ These groups are dedicated to specific projects within the context of a Rust tea
Unlike a Rust Team, Project Groups don't have formal decision making power, though often they are charged with creating prototypes and drawing up recommendations, RFCs, or other documents to inform a final decision. They are associated with a parent team and have a charter outlining their scope and goals, appointed lead, team liaison(s), members, an associated repository, and dedicated streams on Zulip or a channel on Discord (ideally the group should use the same platform as their parent team).
* Duration
-Some project groups are are ephemeral, meaning that they are archived once work is complete. Others continue to develop and maintain their project over time. Examples of ephemeral groups focused on a specific feature include [FFI Unwind], [Inline ASM], and [Safe Transmute]. Examples of groups engaged in continual work include [Triage] and [Rustup].
+Some project groups are are ephemeral, meaning that they are archived once work is complete. Others continue to develop and maintain their project over time. Examples of ephemeral groups focused on a specific feature include [FFI Unwind](https://github.com/rust-lang/project-ffi-unwind), [Inline ASM](https://github.com/rust-lang/project-inline-asm), and [Safe Transmute](https://github.com/rust-lang/project-safe-transmute). Examples of groups engaged in continual work include [Triage](https://github.com/rust-lang/team/blob/master/teams/wg-triage.toml) and [Rustup](https://github.com/rust-lang/team/blob/master/teams/wg-rustup.toml).
* Charter - This document explains the group's scope and goals, individuals involved, membership requirements, and its relationship to the parent team and community.
* Liaison - A member from a official Rust team. Acts as a point of contact between the team and the group. Either directly involved or syncing with the group periodically. Able to represent Project Group work in meetings with the Rust team. Maintains awareness of situations where this Project Group's work may intersect with work outside the Project Team. A liaison may also be a lead, but this is not a requirement.
@@ -145,7 +145,7 @@ Some project groups are are ephemeral, meaning that they are archived once work
* Repository - Hosted under the rust-lang organization, includes the charter and instructions for how community members can monitor or participate in the group.
* Lifecycle
-Detailed instructions for forming, running, and archiving groups are provided in the [Project Groups RFC] (https://github.com/rust-lang/rfcs/blob/master/text/2856-project-groups.md).
+Detailed instructions for forming, running, and archiving groups are provided in the [Project Groups RFC](https://github.com/rust-lang/rfcs/blob/master/text/2856-project-groups.md).
## Decision-making
From bb5e75d8e3409452328e20316714b54fdff29950 Mon Sep 17 00:00:00 2001
From: valgrimm <56933147+valgrimm@users.noreply.github.com>
Date: Sun, 31 May 2020 12:05:30 +0200
Subject: [PATCH 3/4] line breaks
sigh. also forgot these.
---
src/governance/README.md | 17 +++++++++--------
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/src/governance/README.md b/src/governance/README.md
index 93d6259a1..b50e9d80e 100644
--- a/src/governance/README.md
+++ b/src/governance/README.md
@@ -130,21 +130,22 @@ subteam to decide, but:
## Project Groups
-* Definition and rationale
+* Definition and rationale /
These groups are dedicated to specific projects within the context of a Rust team. The goal of a project is to build or formalise a community to discuss and work on a particular feature or need in the organisation. Previously a lot of the discussion and iteration for large features would happen in the initial RFC thread, which is especially unwieldly when work on a feature takes months and years.
-* Essential characteristics
+* Essential characteristics /
Unlike a Rust Team, Project Groups don't have formal decision making power, though often they are charged with creating prototypes and drawing up recommendations, RFCs, or other documents to inform a final decision. They are associated with a parent team and have a charter outlining their scope and goals, appointed lead, team liaison(s), members, an associated repository, and dedicated streams on Zulip or a channel on Discord (ideally the group should use the same platform as their parent team).
-* Duration
+* Duration /
Some project groups are are ephemeral, meaning that they are archived once work is complete. Others continue to develop and maintain their project over time. Examples of ephemeral groups focused on a specific feature include [FFI Unwind](https://github.com/rust-lang/project-ffi-unwind), [Inline ASM](https://github.com/rust-lang/project-inline-asm), and [Safe Transmute](https://github.com/rust-lang/project-safe-transmute). Examples of groups engaged in continual work include [Triage](https://github.com/rust-lang/team/blob/master/teams/wg-triage.toml) and [Rustup](https://github.com/rust-lang/team/blob/master/teams/wg-rustup.toml).
-* Charter - This document explains the group's scope and goals, individuals involved, membership requirements, and its relationship to the parent team and community.
-* Liaison - A member from a official Rust team. Acts as a point of contact between the team and the group. Either directly involved or syncing with the group periodically. Able to represent Project Group work in meetings with the Rust team. Maintains awareness of situations where this Project Group's work may intersect with work outside the Project Team. A liaison may also be a lead, but this is not a requirement.
-* Member - Individuals who regularly participate in work of the Project Group. Initial team membership should preferably include people who have already been participating regularly and productively in related work and discussion.
-* Repository - Hosted under the rust-lang organization, includes the charter and instructions for how community members can monitor or participate in the group.
+* Definitions /
+ -- Charter - This document explains the group's scope and goals, individuals involved, membership requirements, and its relationship to the parent team and community.
+ -- Liaison - A member from a official Rust team. Acts as a point of contact between the team and the group. Either directly involved or syncing with the group periodically. Able to represent Project Group work in meetings with the Rust team. Maintains awareness of situations where this Project Group's work may intersect with work outside the Project Team. A liaison may also be a lead, but this is not a requirement.
+ -- Member - Individuals who regularly participate in work of the Project Group. Initial team membership should preferably include people who have already been participating regularly and productively in related work and discussion.
+ -- Repository - Hosted under the rust-lang organization, includes the charter and instructions for how community members can monitor or participate in the group.
-* Lifecycle
+* Lifecycle /
Detailed instructions for forming, running, and archiving groups are provided in the [Project Groups RFC](https://github.com/rust-lang/rfcs/blob/master/text/2856-project-groups.md).
From 37cf4ea896bfb41b88f8891bab66565693afc181 Mon Sep 17 00:00:00 2001
From: valgrimm <56933147+valgrimm@users.noreply.github.com>
Date: Sun, 31 May 2020 12:09:23 +0200
Subject: [PATCH 4/4] last fixes . . .
Preview changes button is definitely something I'll use more later. Used wrong
, thought this was different in Markdown. Live and learn.
---
src/governance/README.md | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/src/governance/README.md b/src/governance/README.md
index b50e9d80e..a71e4aaef 100644
--- a/src/governance/README.md
+++ b/src/governance/README.md
@@ -130,22 +130,22 @@ subteam to decide, but:
## Project Groups
-* Definition and rationale /
+* Definition and rationale
These groups are dedicated to specific projects within the context of a Rust team. The goal of a project is to build or formalise a community to discuss and work on a particular feature or need in the organisation. Previously a lot of the discussion and iteration for large features would happen in the initial RFC thread, which is especially unwieldly when work on a feature takes months and years.
-* Essential characteristics /
+* Essential characteristics
Unlike a Rust Team, Project Groups don't have formal decision making power, though often they are charged with creating prototypes and drawing up recommendations, RFCs, or other documents to inform a final decision. They are associated with a parent team and have a charter outlining their scope and goals, appointed lead, team liaison(s), members, an associated repository, and dedicated streams on Zulip or a channel on Discord (ideally the group should use the same platform as their parent team).
-* Duration /
+* Duration
Some project groups are are ephemeral, meaning that they are archived once work is complete. Others continue to develop and maintain their project over time. Examples of ephemeral groups focused on a specific feature include [FFI Unwind](https://github.com/rust-lang/project-ffi-unwind), [Inline ASM](https://github.com/rust-lang/project-inline-asm), and [Safe Transmute](https://github.com/rust-lang/project-safe-transmute). Examples of groups engaged in continual work include [Triage](https://github.com/rust-lang/team/blob/master/teams/wg-triage.toml) and [Rustup](https://github.com/rust-lang/team/blob/master/teams/wg-rustup.toml).
-* Definitions /
- -- Charter - This document explains the group's scope and goals, individuals involved, membership requirements, and its relationship to the parent team and community.
- -- Liaison - A member from a official Rust team. Acts as a point of contact between the team and the group. Either directly involved or syncing with the group periodically. Able to represent Project Group work in meetings with the Rust team. Maintains awareness of situations where this Project Group's work may intersect with work outside the Project Team. A liaison may also be a lead, but this is not a requirement.
- -- Member - Individuals who regularly participate in work of the Project Group. Initial team membership should preferably include people who have already been participating regularly and productively in related work and discussion.
- -- Repository - Hosted under the rust-lang organization, includes the charter and instructions for how community members can monitor or participate in the group.
+* Definitions
+-- Charter - This document explains the group's scope and goals, individuals involved, membership requirements, and its relationship to the parent team and community.
+-- Liaison - A member from a official Rust team. Acts as a point of contact between the team and the group. Either directly involved or syncing with the group periodically. Able to represent Project Group work in meetings with the Rust team. Maintains awareness of situations where this Project Group's work may intersect with work outside the Project Team. A liaison may also be a lead, but this is not a requirement.
+-- Member - Individuals who regularly participate in work of the Project Group. Initial team membership should preferably include people who have already been participating regularly and productively in related work and discussion.
+-- Repository - Hosted under the rust-lang organization, includes the charter and instructions for how community members can monitor or participate in the group.
-* Lifecycle /
+* Lifecycle
Detailed instructions for forming, running, and archiving groups are provided in the [Project Groups RFC](https://github.com/rust-lang/rfcs/blob/master/text/2856-project-groups.md).