2025 council survey

Author: Mark-Simulacrum

surveys/micro/leadership-council-2025.md

@@ -0,0 +1,122 @@
+# Survey questions
+
+One of the responsibilities of the [leadership council](https://www.rust-lang.org/governance/teams/leadership-council),
+formed by [RFC 3392](https://rust-lang.github.io/rfcs/3392-leadership-council.html),
+is to solicit feedback on a yearly basis from the Project on how we are performing
+our duties.
+
+> Each year, the Council must solicit feedback on whether the Council is
+> serving its purpose effectively from all willing and able Project members and
+> openly discuss this feedback in a forum that allows and encourages active
+> participation from all Project members. To do so, the Council and other
+> Project members consult the high-level duties, expectations, and constraints
+> listed in this RFC and any subsequent revisions thereof to determine if the
+> Council is meeting its duties and obligations.
+
+This is a quick annual survey for Rust-lang project members to provide feedback
+on the Leadership Council. Your feedback is appreciated to help steer the
+Council activities. As always, if you have specific questions or feedback that
+you would like to provide, feel free to reach out to any Council member with
+questions.
+
+This survey is anonymous. The Council will go through all answers and release a
+summary after the survey is complete, similar to the one published
+[last year](https://blog.rust-lang.org/2024/08/26/council-survey/).
+
+## Leadership Council Effectiveness
+
+For each of the key [duties] outlined in RFC 3392 (quoted below), we'd like your
+input on how well the Council is performing against that duty.
+
+[duties]: https://rust-lang.github.io/rfcs/3392-leadership-council.html#duties-expectations-and-constraints-on-the-council
+
+### Tracking and delegating work
+
+> Identifying, prioritizing, and tracking work that goes undone due to lack of
+> clear ownership (and not due to the owners’ explicit de-prioritization,
+> placement in a backlog, etc.).
+>
+> Delegating this work, potentially establishing new (and possibly temporary)
+> teams to own this work.
+
+FIXME: Maybe link to work we've done in this category?
+
+Type: select one (optional)
+
+- Strongly Agree
+- Agree
+- Unsure
+- Disagree
+- Strongly Disagree
+- Not enough information to comment.
+
+### Project-wide coordination
+
+> Coordinating Project-wide changes to teams, structures, or processes.
+
+FIXME: Maybe link to work we've done in this category?
+
+Type: select one (optional)
+
+- Strongly Agree
+- Agree
+- Unsure
+- Disagree
+- Strongly Disagree
+- Not enough information to comment.
+
+### Accountability
+
+> Ensuring top-level teams are accountable to their purviews, to other teams,
+> and to the Project.
+
+FIXME: Maybe link to work we've done in this category?
+
+Type: select one (optional)
+
+- Strongly Agree
+- Agree
+- Unsure
+- Disagree
+- Strongly Disagree
+- Not enough information to comment.
+
+### Providing resources for teams
+
+> Ensuring where possible that teams have the people and resources they need to
+> accomplish their work.
+
+FIXME: Maybe link to work we've done in this category?
+
+Type: select one (optional)
+
+- Strongly Agree
+- Agree
+- Unsure
+- Disagree
+- Strongly Disagree
+- Not enough information to comment.
+
+### Taking official positions
+
+> Establishing the official position, opinion, or will of the Rust Project as a
+> whole. 
+
+FIXME: Maybe cut this -- not sure how distinct it practically becomes from the previous point.
+
+Type: select one (optional)
+
+- Strongly Agree
+- Agree
+- Unsure
+- Disagree
+- Strongly Disagree
+- Not enough information to comment.
+
+### Are there areas of the Leadership Council that you think are going well?
+
+Type: free text (optional)
+
+### Are there areas of the Leadership Council that you think could be improved or efforts that should be prioritized?
+
+Type: free text (optional)