Skip to content

DEP 0019 - Technical governance for the Django project#107

Open
tim-schilling wants to merge 1 commit intodjango:mainfrom
tim-schilling:dep-0019-technical-governance
Open

DEP 0019 - Technical governance for the Django project#107
tim-schilling wants to merge 1 commit intodjango:mainfrom
tim-schilling:dep-0019-technical-governance

Conversation

@tim-schilling
Copy link
Copy Markdown
Member

From the motivation section:

This is a revisitation of Django's technical governance in which a simplification and reduction was made to make it more approachable to more people. The goals of these changes are the following:

  • Make it easier to enact our governance.
  • Make it easier for others to understand our governance.
  • Make the governance more flexible, allowing more action with less procedure.

Related governance changes:

This is a simplification and reduction of the technical governance.
It is a merge of DEPs 10 and 12, acting as a single source of truth
for governance.

Add bugfix release mention.

Removes a lot of the extra context around the bugfix being
for a feature release. It's not referenced anywhere else and
may be noise.

Consolidate the steering council voting eligibility revocations.

This is a really long sentence now.

Added additional links for DEP process and new-features repo.

Allowed revisiting vetoed discussions and features at SC discretion.

Allowed DEPs during Steering Council elections

Add specific rationales for the changes to the relevant section.

Remove initial list of definitions in favor of links in the document.

Removed the CLA reference.

Remove the phrase minor consensus.

Add a reporting section that documents what reporting is occurring today.

Replace all references to the DSF secretary with the DSF Board.

Remove the paragraph about revoking the ability to vote.

Remove ability for board members to run for the steering council.

Add updated version of steering council eligibility requirements.

Remove voting as the steering council's decision making process.

Expand the technical direction section to call out ability to use DEPs
for things without using the new features repo.
----------------------------------------------

Everyone is encouraged to propose and provide feedback on new features
for Django at any time on the `new-features GitHub repository`_.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was wondering how this impacts discussions in the issue tracker and in the forums?

Previously, there has been an informal process where new features proposed on the issue tracker are often deferred for further discussion/feedback in the Forums.

Copy link
Copy Markdown
Contributor

@LilyFirefly LilyFirefly Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We now have a formal process that new features proposed on Trac are redirected to new-features instead of the forum. It's been a big success - previously good ideas were getting lost on the forum. With GitHub issues, now have much better visibility of what the open discussions are.

Comment on lines +762 to +764
.. _Mergers Team: https://github.com/django/dsf-working-groups/blob/main/active/mergers-team.md
.. _Releasers Team: https://github.com/django/dsf-working-groups/blob/main/active/releasers-team.md
.. _Security Team: https://github.com/django/dsf-working-groups/blob/main/active/security-team.md
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tim-schilling is this right? The links 404

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It will be - the Security Team WG doc is still being worked on.

Copy link
Copy Markdown
Member

@Stormheg Stormheg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tim-schilling this file is named final/0018-technical-governance-6x.rst, looks like an oversight or typo. This PR title and the DEP contents refer to it as DEP 19.

Copy link
Copy Markdown
Member

@Stormheg Stormheg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know a lot about Django's governance model and thus can't speak to any of the specific details in this DEP, but for what it is worth, I liked reading about how the steering council will be run.

I scanned the referenced DEP 10, and I find this new version much more accessible to read and understand. Thanks for proposing it.


* Be a DSF Individual member.

* Shared any of their corporate affiliations.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Have shared"


.. _DEP 44: https://github.com/django/deps/blob/main/accepted/0044-clarify-release-process.rst
.. _Mergers Team: https://github.com/django/dsf-working-groups/blob/main/active/mergers-team.md
.. _Releasers Team: https://github.com/django/dsf-working-groups/blob/main/active/releasers-team.md
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
.. _Releasers Team: https://github.com/django/dsf-working-groups/blob/main/active/releasers-team.md
.. _Releasers Team: https://github.com/django/dsf-working-groups/blob/main/active/releasers.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants