Blog on Django Commons

Policy changes for better community maintenance

Wed, 14 Oct 2026 00:00:00 +0000

The Django Commons Admins Team adopted new governance policies around project maintenance and a new default security policy.

These changes were made to empower our organization to support our community-maintained packages.

Project Maintenance Governance

Originally, Django Commons would only accept actively maintained projects. These changes allow the organization to accept projects that are archived or lack active project admins. It also defines what the Django Commons Admins can do when a maintainer is no longer active. A project is considered dormant when, for example, its project admins have been inactive for six months, or it hasn’t had a release within six months of a new major Django version.

Admins Meeting Notes: 2026-09-30

Wed, 30 Sep 2026 00:00:00 +0000

Actions

Brian: Add to Best Practices suggested guidelines for releasing support for updated versions of Django / Python (Brian)
Brian: Look into ReadTheDocs domain hijacking for packages that don’t use RTD.
Daksh: Update media page with Daksh’s lightning talk from EuroPython
~~Tim: Draft public notes LLM action and initial~~
~~Tim: Update best practices funding.yml https://github.com/django-commons/controls/issues/77~~
~~Tim: Remove Storm’s remaining access~~
~~All: Review the open issues, see if anything should be closed or if there’s something of interest to you~~

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.

Admins Meeting Notes: 2026-09-16

Wed, 16 Sep 2026 00:00:00 +0000

Actions

Brian: Add to Best Practices suggested guidelines for releasing support for updated versions of Django / Python (Brian)
Brian: Look into ReadTheDocs domain hijacking for packages that don’t use RTD.
Daksh: Update media page with Daksh’s lightning talk from EuroPython
~~Daksh to create a meeting poll for an open issues discussion~~
~~Tim: Review Storm post draft~~
- https://github.com/django-commons/membership/pull/562
~~Tim: Follow up with Daniel, Tilda, Brian on public notes~~
Tim: Draft public notes LLM action and initial
All: Review the open issues, see if anything should be closed or if there’s something of interest to you
[TBD]: Explore limited control for DNS records with django unicorn
[TBD]: Draft initial public notes and action
[TBD]: Draft message for the community around policy changes

Agenda

Storm stepping down
- Storm has a new full-time job that is taking up the previous OSS time
- Review Storm Post Draft
- DNS
  - desec.io - confirmed working
- Is planning for the end of the month Sep 30th.
Revise contribution guidance controls PR:
- https://github.com/django-commons/controls/pull/99
- On adding PyPI metadata for description on meaningful metrics
  - Tim: suggestion to remove basing it on the meaningful metrics
  - Storm: Concern with adding it to PyPI because releases don’t get cut often
    - Tim: The changes don’t necessarily need to fit into the existing release flow
    - There would be an issue going from active to dormant, there could be changes that haven’t been released. We would need to decide if those get released or not.
  - Badges on PyPI could have the images updated
    - How does caching work with this?
      - Would need to see what the cache level is
      - What would be the impact of this
    - Is changing the underlying files worth the work
- Daksh: Would a maintainer be opposed to including a badge in the README
  - Not sure, we haven’t tried doing this before.
  - We should have consistency in our projects on badges and README notice about Django Commons
  - Communication plan
    - Draft a message for the maintainers on what we want to change around readme, badges, pypi
    - Update the best-practices repo
    - Create PRs and make it optional
Tim: Public notes
- DSF Board has public and private comments, along with confidential information that they are hidden.
- Storm/Ryan: Could publish public meeting notes as blog posts on the site, then share in other places
- The four of us are in agreement, not quite sure on where it should go
- Tim: I would like it if we have notes published in the forum so that the whole community can find things in the same place
- Storm: I’d prefer a markdown file in a repo to follow-along
- Proposed Logistics
  - Do the meeting minutes in the docs website
  - Use an LLM action to convert from google to markdown
  - Publish to the site
  - Share on the forum
Tim: Review controls repo open issues: https://github.com/django-commons/controls/issues
- Ryan: We can try to review these before next month’s meeting and do some triaging and/or discuss

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