Project team for the Rust Vision Doc 2025 effort

[nikomatsakis]

Context; this hackmd contains charter, expectations, and other info.

cc @jackh726

Charter

To author the Rust 2025 Vision RFC. See the Project Goal for more details.

Membership plan

Initial leads, charged with generally running the group and determining members and membership expectations.

• nikomatsakis
• jackh726

Expectations of membership

The expectation of a team member is that you will be an active participant in gathering and analyzing data. This means that you'll setup and drive at least 2 or 3 interviews and discussions during April -- can of course be way more! There are no pre-defined focus areas, it's up to you to identify the kinds of things you want to focus on.

Time expectation: 2-3h/wk

• Identify at least 2 or 3 interviews you would like to lead
  • Attend others as shadow interviewer
• Conduct interviews in alignment with our guidelines
• Attend regular sync meetings to discuss
• Actively paticipate in editoral discussions

[github-actions]

Dry-run check results

[WARN  sync_team] sync-team is running in dry mode, no changes will be applied.
[INFO  sync_team] synchronizing github
[INFO  sync_team] 💻 Team Diffs:
    ➕ Creating team:
      Org: rust-lang
      Name: project-vision-doc-2025
      Description: Managed by the rust-lang/team repository.
      Privacy: closed
      Members:
        Nadrieril: member
        baumanj: member
        ernestkissiedu: member
        jackh726: member
        joshtriplett: member
        nikomatsakis: member
        spastorino: member
        timClicks: member
        traviscross: member
        workingjubilee: member
    💻 Repo Diffs:
    ➕ Creating repo:
      Org: rust-lang
      Name: project-vision-doc
      Description: Project Vision Doc
      Homepage: Some("https://rust-lang.github.io/project-vision-doc/")
      Auto-merge: true
      Permissions:
        Giving team 'project-vision-doc-2025' maintain permission
        Giving user 'rustbot' write permission
        Giving user 'rfcbot' write permission
      Branch Protections:

[ZuseZ4]

@nikomatsakis The document gives a 403 Forbidden:
https://hackmd.io/@rust-vision-doc/SyfqOGGhye
Is that intended?

[nikomatsakis]

@ZuseZ4 no-- I don't understand that, I thought all those docs were public.

[nikomatsakis]

Heads up that we updated the charter and expectations of membership and I plan to add a few more folks to the list.

[nikomatsakis]

@ZuseZ4 I've inlined the charter into the PR description, seems better anyhow.

[Mark-Simulacrum]

@nikomatsakis Are we expecting a T-council decision to gate merging this? (I don't have a super strong opinion, but it feels a bit odd to allow almost top-level team creation without some team approving it. In this case it's mostly longstanding project members so I'm not too worried, but still :)

I'll mark this PR as draft, but please poke if we think this is only waiting on team repo admins...

[jackh726]

I hadn't quite thought about if this is needs some extra approval or not. I was just waiting on Niko to update the member list here and add a repo before merging.

[nikomatsakis]

@Mark-Simulacrum I believe the general approval was given here when the project goal was approved, so I don't feel the need for a formal check-off...

https://rust-lang.github.io/rust-project-goals/2025h1/rust-vision-doc.html#ownership-and-team-asks

...it's also not a project group, not a permanent team

[nikomatsakis]

@jackh726 I thought I had pushed that...huh

[nikomatsakis]

OK, pushed!

[traviscross]

This is nominated for council discussion on Friday:

• Discuss the vision doc project group 2025 leadership-council#165

[nikomatsakis]

Rebased and updated. Given that leadership council approved this concept, can we get this merged? Would be helpful.

[Mark-Simulacrum]

But looks like CI is failing... happy to get pinged on Zulip once that's fixed.