Proposal: Create Test (or Test Team) in WordPress GitHub Teams

[huzaifaalmesbah]

Similar to existing teams like AI, Gutenberg, and Performance, propose creating a dedicated Test (or Test Team) in the WordPress GitHub organization to improve collaboration and access management.

GitHub Teams: https://github.com/orgs/WordPress/teams

Problem

Testing contributors are currently added individually as collaborators, which is time-consuming and hard to manage across repositories.

Proposal

Create a Test (or Test Team) to manage contributors and repository access in one place.

Benefits

• Centralized repository access
• No need to manage users individually
• Easy communication via like @test-team mentions
• Contributors can request to join
• Ability to manage dedicated repositories for testing tools or plugins

Scope

• Create Test (or Test Team)
• Add maintainers
• Grant access to relevant repositories
• Update documentation

Outcome

Simpler access management, faster onboarding, improved collaboration, and easier management of testing tools and plugins.

[mehrazmorshed]

I am in favor of this proposal. Having a dedicated Test Team can make contribution and collaboration more manageable. I would be happy to contribute to testing.

[ozgursar]

@huzaifaalmesbah what is the process of creating a Test Team in WordPress GitHub Teams? Are there any rules to follow or specs to meet?

[huzaifaalmesbah]

Hi @ozgursar,
To create a Test Team in the WordPress GitHub organization, someone with Owner permissions is required. For example, people like Dion Hulse(dd32) can help create the team and assign repositories.

Once the team is created, if a few of us are added as maintainers, we can then manage members (add/remove) and handle team activities ourselves.

GitHub Teams also support predefined roles such as:

• Read – Read and clone repositories. Open and comment on issues and pull requests.
• Triage – Read permissions plus manage issues and pull requests.
• Write – Triage permissions plus read, clone and push to repositories.
• Maintain – Write permissions plus manage issues, pull requests and some repository settings.
• Admin – Full access to repositories including sensitive and destructive actions. Modify Admin Role

Based on the assigned role, all team members will get the appropriate level of access to repositories.

If we create a team with Write access, all members will automatically have Read, Triage, and Write permissions.
However, if we want to give some contributors only Triage access (so they can manage issues and PRs without code access), then we should create a separate team specifically for that role.

Thanks!

[huzaifaalmesbah]

I think we should create two teams: one Test Team with Maintain access, and another Test Triage Team with Triage access.

[ozgursar]

Testing contributors are currently added individually as collaborators, which is time-consuming and hard to manage across repositories.

Is this how the current Test Team members gained write access to the Test Handbook repository?

[huzaifaalmesbah]

Testing contributors are currently added individually as collaborators, which is time-consuming and hard to manage across repositories.

Is this how the current Test Team members gained write access to the Test Handbook repository?

Yes.

[juanmaguitar]

Great idea @huzaifaalmesbah. Thanks for opening this issue!

I think we should create two teams: one Test Team with Maintain access, and another Test Triage Team with Triage access.

I would start with just one team and will create a separate one if we consider is really needed

[ozgursar]

Thanks @juanmaguitar for creating the GitHub Team. Should we document it on the handbook or just close this issue?

[huzaifaalmesbah]

Test Team has been created, so no further action is needed. Closing this issue.