Skip to content

Commit b36ee0d

Browse files
Add council survey
1 parent 9cd39a0 commit b36ee0d

File tree

1 file changed

+31
-0
lines changed

1 file changed

+31
-0
lines changed

content/Council-survey-2025.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
+++
2+
path = "inside-rust/2025/06/30/Council-Survey-2025"
3+
title = "2025 Leadership Council Survey"
4+
team = "Leadership Council"
5+
aliases = ["inside-rust/2025/06/30/Council-Survey-2025.html"]
6+
+++
7+
8+
One of the responsibilities of the [leadership council](https://www.rust-lang.org/governance/teams/leadership-council),
9+
formed by [RFC 3392](https://rust-lang.github.io/rfcs/3392-leadership-council.html),
10+
is to solicit feedback on a yearly basis from the Project on how we are performing
11+
our duties.
12+
13+
> Each year, the Council must solicit feedback on whether the Council is
14+
> serving its purpose effectively from all willing and able Project members and
15+
> openly discuss this feedback in a forum that allows and encourages active
16+
> participation from all Project members. To do so, the Council and other
17+
> Project members consult the high-level duties, expectations, and constraints
18+
> listed in this RFC and any subsequent revisions thereof to determine if the
19+
> Council is meeting its duties and obligations.
20+
21+
We are runnning a quick annual survey, primarily for Rust project members to
22+
provide feedback on the Leadership Council. However, even if you are not a
23+
member, feel free to fill out the survey too -- we welcome input from those
24+
interacting with the Council in other capacities.
25+
26+
This survey is anonymous. The Council will go through all answers and release a
27+
summary after the survey is complete, similar to the one published
28+
[last year](https://blog.rust-lang.org/2024/08/26/council-survey/).
29+
30+
Please fill out the survey [here](TODO). It will be open for 3 weeks, closing
31+
on 2025-07-21.

0 commit comments

Comments
 (0)