Add Triage and Review team charter. by tim-schilling · Pull Request #79 · django/dsf-working-groups

tim-schilling · 2026-03-03T00:33:53Z

This is part of the DSF's effort to standarize the technical teams (#28)

This is largely a reproduction of the documented processes in DEP 10. However there are some small changes:

Explicit mention of monitoring active contributors to be invited as team
PyCharm licenses mention

nessita

Thank you for working on this!

nessita · 2026-03-10T12:15:40Z

active/triage-and-review.md

+
+## Scope of responsibilities
+
+The objective of the team is to help spread work beyond the [Mergers](https://www.djangoproject.com/foundation/teams/#mergers-team) and into the wider contributor community. The team has elevated permissions in Trac and GitHub to allow them to triage and maintain tickets and pull requests. A pull request approval from a member of the Triage and Review team allows a Merger to merge a minor change that they, themselves have primarily authored.


Just a few notes on this paragraph, maybe no change is needed but I figured I'd mention this:

anyone can triage tickets in Trac as long as they login, a member of the R&T team has no extra privileges there (they can add people as cc in a ticket which a regular user can't, but that's all)

for GH the extra perm for a R&T member is to add labels to a PR.

I think the broad statement of "The team has elevated permissions in Trac and GitHub" covers both of those cases (being able to CC someone is an elevated permission). I'm not sure we should list the permissions explicitly in this document. The benefit of not having the explicit permissions listed is that we're more flexible if there are permission changes in the future.

Agree with Tim, the team can also close duplicate/nuisance PRs, too, which is great, but doesn't need to go in the charter.

active/triage-and-review.md

priyapahwa

Appreciate the efforts that have gone into drafting these charters. Thanks a lot, Tim 🙌

active/triage-and-review.md

priyapahwa · 2026-03-27T20:18:08Z

active/triage-and-review.md

+Anyone actively engaging in discussions on GitHub, the Forum and/or the new-features repository will be eligible to join the Triage and Review Team.
+
+The membership will operate as follows:
+- Any existing member can invite an active contributor to join the team


Although this is already captured on the wiki (“Once there is agreement from the team that the new member is suitable to join”), restating it in the charter that team consensus is required before member invitations would improve clarity. It would also be useful to specify the approval threshold or percentage required for acceptance.

Suggested change

- Any existing member can invite an active contributor to join the team

- Any existing member can invite an active contributor to join the team with a second from an existing team member

Consensus is defined as +2 in the team's wiki. I'm fine adding that here, but I suspect that's not how things work. @jacobtylerwalls I think you've added people recently, can you clarify this when you have time please?

I can't locate which part of the wiki you mean.

In my experience, nominations have been so careful that I've never seen a dissent. I've seen one set of nominations get stalled because it had several candidates, so the +1s rolled in separately. I'm actually going to resurrect that thread now.

It's more like "any objections?"

Sorry, that wasn't so clear. Yes I think the proposed "second" is fine.

The wiki link is: https://code.djangoproject.com/wiki/TriageReviewTeam#HowtoaddamembertotheTriageReviewTeam

priyapahwa · 2026-03-27T20:23:27Z

active/triage-and-review.md

+
+There is no budget, but requests can be made to the Board as needs arise.
+
+Django has some professional PyCharm licenses that we can share with our contributors. Team members are eligible to receive these.


Are these licenses meant to be lifetime or time-limited? Both ways, adding a brief note that they are dependent on availability or subject to change would help set expectations, since access may not be guaranteed indefinitely.

Additionally, "... share with our contributors" - here, contributors refer to the members of WG, right? We can mention that too explicitly.

Are these licenses meant to be lifetime or time-limited? Both ways, adding a brief note that they are dependent on availability or subject to change would help set expectations, since access may not be guaranteed indefinitely.

Can those details be handled by the team and/or board itself? I don't know if the charter needs to capture that level of detail.

Additionally, "... share with our contributors" - here, contributors refer to the members of WG, right? We can mention that too explicitly.

No, I didn't meant that. Contributors is meant to be interpreted in a general sense beyond this team. Your concern regarding members of the WG should be covered by the following sentence: "Team members are eligible to receive these."

Whoops, I didn't answer your question! Sorry. I don't know the duration of those licenses.

PyCharm renews them for "some time" based on goodwill; let's just keep it vague.

Alright, thanks for the info.

@priyapahwa did you want to see changes here still? Not sure where we landed based on your response.

I think we’re good to leave it as-is. Thanks for checking!

Co-authored-by: Priya <pahwa.priya19@gmail.com>

active/triage-and-review.md

jacobtylerwalls · 2026-04-01T16:24:40Z

Updated the member list (pardon me if I shouldn't have). Is it a frozen list, or should we just link to the "live" version: https://www.djangoproject.com/foundation/teams/#triage-review-team

jefftriplett

Great work! This charter has been approved by the board. We appreciate the time, care, and effort that went into developing it, and understand that changes may still occur before it is finalized. We also plan to follow up with a recommendation for a chair or co-chair, even if the role primarily serves as a central point of contact for the board.

Add Triage and Review team charter.

fa23325

This was referenced Mar 3, 2026

Add Triage and Review team charter. tim-schilling/dsf-working-groups#6

Closed

Added a new technical governance DEP. tim-schilling/deps#2

Open

tim-schilling added the ready for board approval label Mar 6, 2026

nessita approved these changes Mar 10, 2026

View reviewed changes

JaeHyuckSa reviewed Mar 17, 2026

View reviewed changes

active/triage-and-review.md Show resolved Hide resolved

Add JaeHyuck Sa to the members.

ea373f0

priyapahwa reviewed Mar 27, 2026

View reviewed changes

tim-schilling and others added 2 commits March 27, 2026 16:42

Update active/triage-and-review.md

3e2cda7

Co-authored-by: Priya <pahwa.priya19@gmail.com>

Update active/triage-and-review.md

d56621f

Co-authored-by: Priya <pahwa.priya19@gmail.com>

jacobtylerwalls reviewed Mar 27, 2026

View reviewed changes

active/triage-and-review.md Show resolved Hide resolved

This comment was marked as resolved.

Sign in to view

Add additional members

8262fe1

AfiMaameDufie approved these changes Apr 9, 2026

View reviewed changes

jefftriplett approved these changes Apr 9, 2026

View reviewed changes


		## Scope of responsibilities

		The objective of the team is to help spread work beyond the [Mergers](https://www.djangoproject.com/foundation/teams/#mergers-team) and into the wider contributor community. The team has elevated permissions in Trac and GitHub to allow them to triage and maintain tickets and pull requests. A pull request approval from a member of the Triage and Review team allows a Merger to merge a minor change that they, themselves have primarily authored.

	- Any existing member can invite an active contributor to join the team
	- Any existing member can invite an active contributor to join the team with a second from an existing team member


		There is no budget, but requests can be made to the Board as needs arise.

		Django has some professional PyCharm licenses that we can share with our contributors. Team members are eligible to receive these.

Conversation

tim-schilling commented Mar 3, 2026

Uh oh!

nessita left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

priyapahwa left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

tim-schilling Mar 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

This comment was marked as resolved.

Uh oh!

jacobtylerwalls commented Apr 1, 2026

Uh oh!

jefftriplett left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

tim-schilling Mar 27, 2026 •

edited

Loading