Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Propose project-goals team #1641

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

nikomatsakis
Copy link
Contributor

propose goals team

Charter and other documentation available on the rust-project-goals repository. As of this PR:

Goals team

The Rust goals program is administered by the Goals team.
This document serves as the team charter.

Mission

Our mission is to focus the Rust programming language efforts by running and administering an inclusive and dynamic goals program. We work with the project teams to identify the highest priority items and to make sure that the teams are budgeting adequate time and resources to ensure those items are successful. For new contributors who have an idea they'd like to pursue, we work to provide a welcoming "front door" to Rust, connecting their proposal to the maintainers whose support will be needed to make it reality. For existing maintainers, we help them to document the work they are doing and to find new contributors.

Role and duties of team members

Team members perform some subset of the following roles:

  • Attending short sync meetings.
  • When preparing a new goal slate:
    • Advertising the goal program to teams and soliciting participation
    • Reviewing incoming goal proposals for quality and accuracy
    • Seeking feedback on behalf of outsiders' goals
    • Authoring the RFC and hounding team leads to check their boxes
    • Deciding which goals to propose as flagship goals.
  • During the year:
    • Authoring round-up blog posts highlighting progress
    • Updating and maintaining the web-site
    • Checking in with the goal points of contact that are not reporting progress to see if they need help

Role of the lead

The team lead is the owner of the program,
meaning that they take ultimately responsible for ensuring the goals program moves forward smoothly.
They perform and and all of the member functions as needed, delegating where possible.
In the event of conflicts (e.g., which goals to propose as flagship goals in the RFC), team lead makes the final decision.

Niko Matsakis and others added 2 commits January 13, 2025 15:03
charter and other documentation available on
the [rust-project-goals repository][r]. As of
this writing:

The Rust goals program is administered by the Goals team.
This document serves as the team charter.

Our mission is to focus the Rust programming language efforts by running and administering an inclusive and dynamic goals program. We work with the project teams to identify the highest priority items and to make sure that the teams are budgeting adequate time and resources to ensure those items are successful. For new contributors who have an idea they'd like to pursue, we work to provide a welcoming "front door" to Rust, connecting their proposal to the maintainers whose support will be needed to make it reality. For existing maintainers, we help them to document the work they are doing and to find new contributors.

Team members perform some subset of the following roles:

* Attending short sync meetings.
* When preparing a new goal slate:
    * Advertising the goal program to teams and soliciting participation
    * Reviewing incoming goal proposals for quality and accuracy
    * Seeking feedback on behalf of outsiders' goals
    * Authoring the RFC and hounding team leads to check their boxes
    * Deciding which goals to propose as flagship goals.
* During the year:
    * Authoring round-up blog posts highlighting progress
    * Updating and maintaining the web-site
    * Checking in with the goal points of contact that are not reporting progress to see if they need help

The team lead is the [owner](../about/owners.md) of the program,
meaning that they take ultimately responsible for ensuring the goals program moves forward smoothly.
They perform and and all of the member functions as needed, delegating where possible.
In the event of conflicts (e.g., which goals to propose as flagship goals in the RFC), team lead makes the final decision.

[r]: https://github.com/rust-lang/rust-project-goals/blob/3ed26fd345698de857bdb67cafdd698c863a0c65/src/admin/team.md
@nikomatsakis
Copy link
Contributor Author

cc @nandsh @joshtriplett @lqd

teams/goals.toml Outdated Show resolved Hide resolved
@ehuss
Copy link
Contributor

ehuss commented Jan 13, 2025

I'm not sure if it is intentional, but you may want to give the team permissions on https://github.com/rust-lang/team/blob/HEAD/repos/rust-lang/rust-project-goals.toml

@nikomatsakis

This comment was marked as resolved.

@nikomatsakis
Copy link
Contributor Author

OK, @ehuss I think I did that =)

@jamesmunns
Copy link
Member

jamesmunns commented Jan 13, 2025

Wearing my Launching Pad council rep hat (as there is no launching pad lead to formally approve/accept this team), I don't have any objections to having Project Goals as a team under the launching pad (and it likely is the most reasonable place today), but it will mean I'll immediately add it to my to-do list for "finding launching pad teams a new home".

Noting that this was discussed on Zulip, and there wasn't a hard approval from the council, nor was there a hard objection.

@nikomatsakis
Copy link
Contributor Author

@jamesmunns +1, and it occurs to me we could even make a project goal for that :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants