Skip to content

Commit f556911

Browse files
authored
Merge pull request #1254 from ehuss/council-selection
Add post kicking off March Council selections
2 parents b5147ba + 3933598 commit f556911

File tree

1 file changed

+70
-0
lines changed

1 file changed

+70
-0
lines changed
Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
---
2+
layout: post
3+
title: "Leadership Council March Representative Selections"
4+
author: Leadership Council
5+
team: Leadership Council <https://www.rust-lang.org/governance/teams/leadership-council>
6+
---
7+
8+
The selection process for representatives on the [Leadership Council] is starting today.
9+
10+
Every six months, half of the council terms end.
11+
Since this is the first rotation since the formation of the Council in June 2023, we have chosen the following teams (and their current representatives) to establish who will start this process:
12+
13+
* [Compiler][Eric Holk]
14+
* [Crates.io][Carol Nichols]
15+
* [Devtools][Eric Huss]
16+
* [Launching Pad][Jonathan Pallant]
17+
18+
We are aiming to have the teams confirm their choices by March 22, 2024, and for any possible new members to be ready to join the Council meetings starting March 29th.
19+
20+
[Leadership Council]: https://www.rust-lang.org/governance/teams/leadership-council
21+
[compiler]: https://www.rust-lang.org/governance/teams/compiler
22+
[crates.io]: https://www.rust-lang.org/governance/teams/crates-io
23+
[devtools]: https://www.rust-lang.org/governance/teams/dev-tools
24+
[launching pad]: https://forge.rust-lang.org/governance/council.html#the-launching-pad-top-level-team
25+
[Eric Holk]: https://github.com/eholk
26+
[Carol Nichols]: https://github.com/carols10cents
27+
[Eric Huss]: https://github.com/ehuss
28+
[Jonathan Pallant]: https://github.com/jonathanpallant
29+
30+
## Criteria for representatives
31+
32+
Any member of the top-level team or a member of any of their subteams is eligible to be the representative.
33+
See [candidate criteria] for a description of what makes a good representative.
34+
35+
[candidate criteria]: https://forge.rust-lang.org/governance/council.html#candidate-criteria
36+
37+
There is a limit of at most two people affiliated with the same company or other legal entity being on the Council [^affiliates].
38+
During the selection process, the Council will consider the affiliation of candidates to decide if all choices will be compatible with that constraint.
39+
Note that the Council is currently investigating clarifications and changes to affiliation limits, but we do not expect these changes to be ready before this selection process is over.
40+
41+
Representatives may serve multiple terms if the team decides to choose the same representative again.
42+
There is a soft limit of three terms.[^limit]
43+
It is recommended that teams rotate their representatives if possible to help avoid burnout and to spread the experience to a broader group of people.
44+
45+
[^affiliates]: See [Limits on representatives from a single company/entity](https://forge.rust-lang.org/governance/council.html#limits-on-representatives-from-a-single-companyentity)
46+
47+
[^limit]: See [Term limits](https://forge.rust-lang.org/governance/council.html#term-limits).
48+
49+
## What do Representatives do?
50+
51+
A representative provides a voice on the Council to represent the interests of their teams and contribute to the long-term success of the Rust Project.
52+
Some examples of the activities that representatives take are:
53+
54+
* Participating in Council meetings every other week.
55+
* Responding to proposals needing a decision.
56+
* Work on the policies and proposals concerning the Council itself.
57+
* Communicate activities and decisions to the team and subteams, and the Project as a whole.
58+
* Coordinate with the Foundation and the Foundation Project Directors to represent the needs of the Project to the Foundation.
59+
60+
The amount of time the position takes varies depending on which initiatives the representative participates in, and how frequently decisions are brought to the Council.
61+
In general you may expect to spend at least a few hours a week on Council tasks.
62+
63+
## How should teams make their selection?
64+
65+
We currently don't have a recommended process that teams should use to make their selection.
66+
In the meantime, teams may want to consider the [consensus selection process] which some teams used during the initial selections of the Council.
67+
Team members should consult with their team leads if they are interested in being nominated.
68+
We hope that in the future we can formalize a recommended process.
69+
70+
[consensus selection process]: https://github.com/rust-lang/rfcs/pull/3392#issuecomment-1505697944

0 commit comments

Comments
 (0)