rust-lang / rust-lang/team

Add remaining Zulip user groups

Open
#826 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
363
Forks
369
Avg merge
1d 54m
Merged PRs (30d)
59

Description

The following are the remaining Zulip user groups that are not yet synced between the team repo and the Zulip instance.

Please review the user groups and send pull requests adding them to the team repo (see below for instructions).

Once these are added, the Zulip user groups will be completely managed by the team repo.

Instructions

To add a working group follow the documentation here. More than likely this will simply involve adding the following lines to your team's toml config:

[[zulip-groups]]
name = "T-awesome-zulip-team" # Make sure to change this! 

If you need to add or remove people from the baseline of team membership, you can use the extra-people and excluded-people fields.

If someone you've added does not have a zulip-id field in their personal configuration file, you will need to add it. You can find some instructions on where to find their zulip-id here

As an example, you can see how the compiler team's configuration is set here.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with docs/toml-schema.md at the Zulip group instructions and compare the existing teams/compiler.toml configuration. Review the listed unchecked groups and their ownership or activity notes, then inspect the relevant team and personal configuration files, using the README instructions if a zulip-id is missing. Done means the remaining active groups are represented in the team repository and inactive groups have a documented disposition.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.