Hello again from the Rust Leadership Council. In our first blog post, we laid out several immediate goals for the council and promised to report back on their progress. It has been about a month since our first update so we wanted to share how it's going and what we're working on now.
Accomplishments so far
In our first post, we wrote:
In the coming weeks we will be establishing the basic infrastructure for the group, including creating a plan for regular meetings and a process for raising agenda items, setting up a team repository, and ultimately completing the transition from the former Rust leadership structures.
We have made progress on each of these things.
For the last month we have been holding weekly meetings and will continue to do so for at least the next month. In the long term, we would like these meetings to become less frequent and rely more on public, asynchronous discussion and decision processes, but in the short term there has been plenty to discuss each week. We publish minutes from each meeting, and these are linked at the bottom of this post.
In order to be able to make progress without needing to involve all Council members, we've decided to establish small groups of people (called "committees") to focus on various specific work items. The committees then bring their work to the full council for discussion and consent. The two committees we've established so far are one to create a process for electing Project Directors to serve as our representatives on the foundation board, and one of council librarians to work on processes to document our actions and decisions.
We have created a GitHub repository for all our documentation, including procedures we have decided on and meeting minutes. There are issues for some tasks we hope to complete in the near future.
We discussed and approved RFC 3355, which establishes that we would like to have a Rust specification and that we would like the Foundation to hire an editor for the specification (note that this RFC does not actually approve any aspects of that specification yet, only starting the work to create the specification).
And we've been discussing all of this work in the public council stream on Zulip if you'd like to follow along or contribute to the discussion.
Looking forward with your feedback
We have a lot of ideas on problems of the Rust Project we could work on, but we know we, as a council, can only realistically make progress on a few topics at the same time.
We've come up with a proposed list of our first three priorities, and we'd like the project's feedback on whether this matches your expectations. This is a starting place for iterative improvement over time; we're planning on re-evaluating whether these priorties are still the right ones about every two months or so.
The type of feedback we're most interested in is hearing about topics or issues you think are more important or urgent than one or more of the following three priorities, and why we should tackle that topic instead of what we have listed here. If this list sounds good to you, we'd like to hear that as well!
Each team representative on the council will be reaching out to their team specifically for feedback on this list, but we also welcome feedback from the Rust community in the "#council/Feedback on priorities" Zulip topic or via email to email@example.com.
The priorities we're proposing we concentrate on first are:
- Documenting and improving processes for interaction with the Rust Foundation including formalising the role of project directors in this process (the trademark policy process may be part of this).
- Establishing plans for how to strengthen the moderation team (i.e., 2 is not a sustainable number and we currently have no contingent moderators) and strengthen moderation policies.
- Figuring out the "shape" of the Rust Project. The Leadership Council needs to reflect the will of the Rust Project so it is important to know who that includes.
If you're interested in the items under consideration that we think aren't as high priority as these, you can read the full, unsorted list in this document.
We are also interested in delegating other work that the council won't have bandwidth to take on; if you have proposals for something you'd like to work on which will eventually need the council's support/approval, please reach out!
Again, we are most interested to hear if there's something you think the Leadership Council should be working on that's more important or urgent than these items. Thank you for your help!
We publish minutes from all Council meetings to the Leadership Council repo. For convenience, we've also directly linked to the minutes from our first few meetings here.