|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +title: "2024 Leadership Council Survey" |
| 4 | +author: The Leadership Council |
| 5 | +--- |
| 6 | + |
| 7 | +One of the responsibilities of the [leadership council](https://www.rust-lang.org/governance/teams/leadership-council), |
| 8 | +formed by [RFC 3392], is to solicit feedback on a yearly basis from the Project |
| 9 | +on how we are performing our duties. |
| 10 | + |
| 11 | +> Each year, the Council must solicit feedback on whether the Council is |
| 12 | +> serving its purpose effectively from all willing and able Project members and |
| 13 | +> openly discuss this feedback in a forum that allows and encourages active |
| 14 | +> participation from all Project members. To do so, the Council and other |
| 15 | +> Project members consult the high-level duties, expectations, and constraints |
| 16 | +> listed in this RFC and any subsequent revisions thereof to determine if the |
| 17 | +> Council is meeting its duties and obligations. |
| 18 | +
|
| 19 | +This is the council's first year, so we are still figuring out the best way to |
| 20 | +do this. For this year, a short survey was sent out to all@ on June 24th, 2024, |
| 21 | +ran for two weeks, and we are now presenting aggregated results from the |
| 22 | +survey. Raw responses will not be shared beyond the leadership council, but the |
| 23 | +results below reflect sentiments shared in response to each question. We invite |
| 24 | +feedback and suggestions on actions to take on Zulip or through direct |
| 25 | +communication to council members. |
| 26 | + |
| 27 | +We want to thank everyone for their feedback! It has been very valuable to hear |
| 28 | +what people are thinking. As always, if you have thoughts or concerns, please |
| 29 | +reach out to your council representative any time. |
| 30 | + |
| 31 | +## Survey results |
| 32 | + |
| 33 | +We received 53 responses to the survey, representing roughly a 32% response |
| 34 | +rate (out of 163 current recipients of all@). |
| 35 | + |
| 36 | +### Do you feel that the Rust Leadership Council is serving its purpose effectively? |
| 37 | + |
| 38 | +| Option | Response count |
| 39 | +|-------------------|--------------- |
| 40 | +| Strongly agree | 1 |
| 41 | +| Agree | 18 |
| 42 | +| Unsure | 30 |
| 43 | +| Disagree | 4 |
| 44 | +| Strongly disagree | 0 |
| 45 | + |
| 46 | +### I am aware of the role that the Leadership Council plays in the governance of the Rust Project. |
| 47 | + |
| 48 | +| Option | Response count |
| 49 | +|-------------------|--------------- |
| 50 | +| Strongly agree | 9 |
| 51 | +| Agree | 20 |
| 52 | +| Unsure | 14 |
| 53 | +| Disagree | 7 |
| 54 | +| Strongly disagree | 3 |
| 55 | + |
| 56 | +### The Rust Project has a solid foundation of Project governance. |
| 57 | + |
| 58 | +| Option | Response count |
| 59 | +|-------------------|--------------- |
| 60 | +| Strongly agree | 3 |
| 61 | +| Agree | 16 |
| 62 | +| Unsure | 20 |
| 63 | +| Disagree | 11 |
| 64 | +| Strongly disagree | 3 |
| 65 | + |
| 66 | +### Areas that are going well |
| 67 | + |
| 68 | +For the rest of the questions we group responses into rough categories. The |
| 69 | +number of those responses is also provided; note that some responses may have |
| 70 | +fallen into more than one of these categories. |
| 71 | + |
| 72 | +* (5) Less drama |
| 73 | +* (5) More public operations |
| 74 | +* (5) Lack of clarity / knowledge about what it does |
| 75 | + * It's not obvious why this is a "going well" from the responses, but it was |
| 76 | + given in response to this question. |
| 77 | +* (4) General/inspecific positivity. |
| 78 | +* (2) Improved Foundation/project relations |
| 79 | +* (2) Funding travel/get-togethers of team members |
| 80 | +* (1) Clear representation of members of the Project |
| 81 | +* (1) Turnover while retaining members |
| 82 | + |
| 83 | +### Areas that are not going well |
| 84 | + |
| 85 | +* (15) Knowing what the council is doing |
| 86 | +* (3) Not enough delegation of decisions |
| 87 | +* (2) Finding people interested in being on the council / helping the council |
| 88 | +* (1) What is the role of the project directors? Are they redundant given the council? |
| 89 | +* (2) Too conservative in trying things / decisions/progress is made too slowly. |
| 90 | +* (1) Worry over Foundation not trusting Project |
| 91 | + |
| 92 | +Suggestions for things to do in the responses: |
| 93 | + |
| 94 | +* (2) Addressing burnout |
| 95 | +* (2) More social time between teams |
| 96 | +* (2) More communication/accountability with/for the Foundation |
| 97 | +* (2) Hiring people, particularly for non-technical roles |
| 98 | +* (1) Helping expand the moderation team |
| 99 | +* (1) Resolving the launching pad issues, e.g., through "Rust Society" work |
| 100 | +* (1) Product management for language/compiler/libraries |
| 101 | + |
| 102 | +## Takeaways for future surveys |
| 103 | + |
| 104 | +* We should structure the survey to specifically ask about high-level duties |
| 105 | + and/or enumerate areas of interest (e.g., numeric responses on key questions |
| 106 | +like openness and effectiveness) |
| 107 | +* Consider linking published material/writing 1-year retrospective and that |
| 108 | + being linked from the survey as pre-reading. |
| 109 | +* We should disambiguate between neutral and "not enough information/knowledge |
| 110 | + to answer" responses in multiple choice response answers. |
| 111 | + |
| 112 | +## Proposed action items |
| 113 | + |
| 114 | +We don't have any concrete proposed actions at this time, though are interested |
| 115 | +in finding ways to have more visilibity for council activities, as that seems |
| 116 | +to be one of the key problems called out across all of the questions asked. How |
| 117 | +exactly to achieve this remains unclear though. |
| 118 | + |
| 119 | +As mentioned earlier, we welcome input from the community on suggestions for |
| 120 | +both improving this process and for actions to change how the council operates. |
| 121 | + |
| 122 | +[RFC 3392]: https://rust-lang.github.io/rfcs/3392-leadership-council.html |
0 commit comments