Django Commons

Thank you, Storm

Mon, 21 Sep 2026 00:00:00 +0000

One of the things we say a lot at Django Commons is that sustainability has to include the people, not just the packages. It’s easy to say. It’s harder to mean it when someone who has carried real weight decides it’s time to step back. Storm Heg is stepping down from the admin team, and just like we did when Lacey stepped away, we want to send him off the right way: with gratitude, and without any suggestion that leaving is a failure.

Thank you Lacey

Mon, 06 Jul 2026 00:00:00 +0000

Django Commons has some very lofty goals for open source. One of our goals is Sustainability. While this can mean many things for the Django Commons organization, it means:

The community seeks to make contributing to open source and the community itself a sustainable activity. This involves clear expectations on roles, being supportive of taking breaks and creating space for others. Our processes and code should be documented, be maintainable and easily searchable.

Please welcome our new admins

Tue, 21 Apr 2026 00:00:00 +0000

Hello Django community!

Django Commons has some exciting news. Our team has grown to eight members. Please help us in welcoming our new admins: Brian Kohan, Daksh P. Jain, and Tilda Udufo!

Brian Kohan

Brian is a software engineer with 19 years of experience in the aerospace sector. He’s been squashing web-shaped problems with Django for the last 9 of those years and is the maintainer of 5 open source Django packages. He lives in Los Angeles with his family where he devotes the balance of his time to organizing his community’s response to homelessness.

We're recruiting new admins!

Tue, 03 Feb 2026 00:00:00 +0000

The Django Commons admin team is recruiting new members. If you’re interested in being an admin of Django Commons, please fill out this Admin Interest Form by March 16th, 2026 AOE.

What does the admin team do?

The admin team takes care of the administrative work of managing Django Commons and supporting its projects and members. This includes things like:

Membership responsibilities: approving new members in GitHub and assigning them to the right teams, handling PyPI access, and checking in with project teams
Project maintenance: Onboarding incoming repos and reviewing them for readiness, configuring settings and actions in GitHub, more PyPI actions
Community management: answering questions in online spaces, responding to requests, outreach
Website maintenance: adding new projects to the website, adding and maintaining information
Administrative and funding tasks: governance decisions and docs, Terraform tooling, manage contributions on Thanks.dev and Open Collective, branding updates

Decision Record

Mon, 01 Jan 0001 00:00:00 +0000

This document is a record of all formal decisions the Django Commons admins have made. The purpose is to provide transparency and information to future administrators.

Template

- DATE: SHORT_TITLE
 LONGER_DESCRIPTION (at most 4 sentences)

Decisions

2026-08-07: Adopt new project maintenance governance. This adds governance around managing projects that have gone dormant or are archived. The purpose of these changes are to allow us to accept dormant and archived projects, as well as provide a pathway for projects to go that route within Django Commons.
2025-12-18: Revise admin qualifications. The admin team and super admin team qualifications have been revised reflect the reality of who we are looking for those roles and their likely qualifications. Admins can be anyone while the super admins must be the trusted members since they will have the privileged access.
2025-11-21: Remove the Security team. There is little regular support from the team currently. The new process will be the admins will be notified of a security advisory and then they can reach out to community members based on the context of the issue.
2025-10-10: Create “super admins” team. Create a “super admins” team for people with elevated permissions across GitHub and PyPI to allow new-to-Django-community people become admins.
2025-10-10: Retire PyPI team in favor of all admins
2025-10-10: 2025 admin team reaffirmations. Admin team reaffirmed status for next year if we increase the size of the team, otherwise people are interested in switching with new people.
2025-10-10: Finalized selection of the new Django Commons logo. PR
2024-11-01: Retain project admins as PyPI Owners. The repository’s admins will be retained as PyPI Owners. This provides the project team greater autonomy and allows a repository to be moved out of Django Commons without the admins involvement in extreme cases.

Django Commons Governance

Mon, 01 Jan 0001 00:00:00 +0000

For Django Commons to function effectively, we need trusted volunteers to step up and take responsibility for certain aspects that require ongoing attention and a certain level of trust from our community. These volunteers are organized into teams, each with a specific focus.

Relation to the Django Software Foundation

Django Commons is an independent initiative from the Django Software Foundation (DSF). We are here for the third-party packages that complement Django. We are here as a community for and by Django users.

Django Commons Projects

Mon, 01 Jan 0001 00:00:00 +0000

These are the projects that have joined Django Commons and the dates they joined. This list is manually curated, it’s possible there are newly transitioned projects listed in repositories.tfvars file.

Django Commons Values

Mon, 01 Jan 0001 00:00:00 +0000

Django Commons seeks to embody the following values. These are central to the organization’s existence and influence how we make decisions. These are listed in alphabetical order.

Inclusivity

The community seeks to be welcoming, kind, inclusive and diverse. Any person who embodies the values of Django Commons is welcome in the community and should be treated with respect.

The community seeks to openly share information about all areas it is involved in so that others can easily adopt them. Information can be on community organizing, package maintenance or sharing code.

Free Resources for Django Commons Maintainers

Mon, 01 Jan 0001 00:00:00 +0000

This page contains resources for django-commons maintainers. If you know of additional resources available to maintainers that are not listed here, please create a pull request to add them!

deSEC domains

Django Commons projects can get a free domain from desec.io. This is a great option for projects that want to have a custom domain for their documentation or website.

Contact the Django Commons admins for more information.

AWS Open Source Credits

AWS provides free credits for open source maintainers. To apply for credits, visit this post and check out the section How do I apply?

Frequently Asked Questions

Mon, 01 Jan 0001 00:00:00 +0000

What are the differences between Django Commons and Jazzband?

Django Commons and Jazzband have similar goals, to support community-maintained projects. There are two main differences. The first is that Django Commons leans into the GitHub paradigm and centers the organization as a whole within GitHub. This is a risk, given there’s some vendor lock-in. However, the repositories are still cloned to several people’s machines and the organization controls the keys to PyPI, not GitHub. If something were to occur, it’s manageable.

Funding for Django Commons projects

Mon, 01 Jan 0001 00:00:00 +0000

Django Commons does not place restrictions on projects’ ability to seek outside sponsorship or funding. You are welcome to seek sponsors for your project through whatever method you choose. At this time, Django Commons is not able to manage your funding for you, so any fundraising you do will need to be managed by the project’s maintainers.

Thanks.dev

We know we have a few projects who seek sponsorship on Thanks.dev. We have discovered an issue with Thanks.dev that may impact your desire to seek sponsorship through them.

Media

Mon, 01 Jan 0001 00:00:00 +0000

Below is a collection of Django Commons content. They may be blog posts, videos or podcasts. If you’ve mentioned Django Commons, please let us know and we’ll get it added to the list!

“Behind the Commit” interview with Daniel Moran
"#466: PSF Lands $1.5 million" by PythonBytes: Brian Okken and Michael Kennedy review a blog post discussing django-click and django-typer from Lacey and mention they are supported by Django Commons.
Django Commons YouTube
Django Tasks Scheduler project overview with Daniel Moran Daniel Moran provides an introduction of django-tasks-scheduler to Ryan Cheley and Tim Schilling.
Django Brew Episode 4: Spoiler Alert: DjangoCon US Recap, Open Source Maintenance, and Other Spooky Stories
“Endorsing Django Packages” by Andy Miller
“Django Commons” by Ryan Cheley: An introduction to Django Commons, explaining its goals, structure, and benefits for maintainers.
“Django Commons” by Simon Willison: Simon highlights Django Commons on his blog and what he’s looking forward to.
“Introducing Django Commons!” by Lacey Henschel: A lightning talk from DjangoCon US 2024 introducing Django Commons.
“Django Commons - A home for community-maintained Django packages” by Tim Schilling: A call for help to start Django Commons.

Project Maintenance Governance

Mon, 01 Jan 0001 00:00:00 +0000

Overview

Django Commons creates the conditions for maintainership to transfer smoothly so that when maintainers step back, the community has a clear path to step in.

This document will outline the various states a project can be in, how a project transitions between them, and where support is provided.

Maintenance States

Healthy

A project has a responsive maintainer, clear ownership, regular releases, and an active repository.

Dormant

A project has an unresponsive maintainer, a lack of forward compatibility, and potentially community complaints.

Response Timeframes

Mon, 01 Jan 0001 00:00:00 +0000

The table below defines the timeframes in which we expect a maintainer to respond to a reported security vulnerability. For the purposes of ‘responsiveness’ an acknowledgement is sufficient. There isn’t an expectation that a fix will be implemented within the time frames below.

CVE Level	Timeframe
Critical	1 week
High	2 weeks
Medium	4 weeks
Low	8 weeks
None	16 weeks

Team

Mon, 01 Jan 0001 00:00:00 +0000

The membership of Django Commons can be viewed on GitHub.

Current Admins

Django Commons is currently administered by the following people. If you’d like to join them, please open a “New admin” issue at django-commons/membership.

Brian Kohan

2026 -

Django Commons

Thank you, Storm

Thank you Lacey

Please welcome our new admins

Brian Kohan

We're recruiting new admins!

What does the admin team do?

Decision Record

Template

Decisions

Django Commons Governance

Relation to the Django Software Foundation

Django Commons Projects

Django Commons Values

Inclusivity

Free Resources for Django Commons Maintainers

deSEC domains

AWS Open Source Credits

Frequently Asked Questions

What are the differences between Django Commons and Jazzband?

Funding for Django Commons projects

Thanks.dev

Media

Project Maintenance Governance

Overview

Maintenance States

Healthy

Dormant

Response Timeframes

Sponsors

1Password

deSEC

Team

Current Admins

Brian Kohan

Django Commons

Thank you, Storm

Thank you Lacey

Please welcome our new admins

Brian Kohan

We're recruiting new admins!

What does the admin team do?

Decision Record

Template

Decisions

Django Commons Governance

Relation to the Django Software Foundation

Django Commons Projects

Django Commons Values

Inclusivity

Knowledge Sharing

Free Resources for Django Commons Maintainers

deSEC domains

AWS Open Source Credits

Frequently Asked Questions

What are the differences between Django Commons and Jazzband?

Funding for Django Commons projects

Thanks.dev

Media

Project Maintenance Governance

Overview

Maintenance States

Healthy

Dormant

Response Timeframes

Sponsors

1Password

deSEC

Team

Current Admins