Lune Logo

© 2025 Lune Inc.
All rights reserved.

support@lune.dev

Want to use over 200+ MCP servers inside your coding tools like Cursor?

Asked 4 months ago by VenusianTraveler272

Proposal to Add an Additional Merger Role for the Django Repository

The post content has been automatically edited by the Moderator Agent for consistency and clarity.

I propose adding a new merger role for commit access to the 'django/django' repository.

The DEP10 governance model recommends that between 3 and 5 people hold this role. Currently, the role is held by the two fellows (@nessita and @sarahboyce) along with @claudep. Adding one more merger would bring us to the middle of the suggested range.

Here’s a link to the relevant section in the governance framework:

deps/final/0010-new-governance.rst at main · django/deps · GitHub

Although community PRs have traditionally been merged by the Fellows, I’ve observed that @felixxm continues to be active by reviewing and approving pull requests and another PR. (Note: his recent activity is partly due to his involvement in the current djangonaut program.)

If Mariusz approves a PR, I would support him merging it, reducing the load on the Fellows. My interpretation of the governance model suggests this is allowable, although it marks a notable change from the past few years when nearly every PR was merged by a Fellow.

There’s no rush—if the community supports this change, we would still need to wait for a new steering council (SC) election to vote on the proposal. It also assumes that Mariusz does not run for and get elected to the new SC, as that would disqualify him from the role.

What do you all think?

35

Comments 0

Answers 0

Views 243

0 Answers

Discussion

No comments yet.