A valuable resource for thinking about work the Council should be doing in its first year can be found [in the Council RFC appendix](https://github.com/rust-lang/rfc-leadership-council/blob/main/text/3392-leadership-council/initial-work-of-the-council.md). ### Existing (Long Term) * Librarians: * ensuring that Council output (meetings, decisions, pending work items, backlog, etc.) are documented properly. ### Existing (Ephemeral) * Project Director Elections Process: * Design the election process for the next set of Rust Foundation Project Directors (ratified by the Leadership Council) ### Possible Additions (Long Term) * Communications * while the librarians ensure the details of Council output are well documented, this committee ensures the proper high-level awareness of Council output through blog posts, social media, emails to all@, etc. * Roadmaps * Helping teams establish clear roadmaps and supporting cohension among roadmaps. Potentially additionally establishing a project wide roadmap. * Diversity * Understanding, communicating, and improving the Project's situation when it comes to diversity of participants. * Feedback * Establishing and running feedback channels for project participants to give feedback on their Council representative and the Council as a whole. * Continuing Education * Establishing ways for project participants to receive training in areas relevant to their roles in the project (especially non-technical trainings) ### Possible Additions (Ephemeral) * Foundation Relationship * establishing the processes by which the Council (and by extension the project as a whole) interact with the Rust Foundation (including solidifying the role of the Project Directors) * Foundation Executive Director Evaluation * Establish the process (together with the Foundation) for how Project feedback should be included in the annual evaluations of the project directors performance. * Trademark working group * Establish a formal trademark policy working group for ensuring that project feedback is properly incorporated into the Rust trademark draft proposal. * Organizational Cleanup * The shape of the Rust project organization has largely been a mix of deliberate choice and happy accident. Lots of decisions become much easier when it's possible to define the boundaries of what constitutes "the Rust Project". This group makes proposals for how to do that. * Ensuring that teams have clear purviews and that gaps and overlaps in purviews are well understood and documented. * Bootstrapping Launching Pad * Help establish the processes, policies, etc. of the Launching pad team. * Solidify moderation * Help establish a more sustainable moderation team structure (i.e., more than just two folks) * Ownership and permissions * Working together with the infra team to establish clear policy and procedure around who has access to what and who ultimately "owns" things such as credentials * RFC process improvements * The RFC process is quite old and many believe it needs to be evaluated and at least partially reconsidered.