Skip to content

Blog#

News and announcements from the Django Commons community. You can subscribe via RSS or JSON.

Thank you Lacey

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.

The idea of "being supportive of taking breaks" is a key part of sustainability. While this can seem to apply only to the projects that are part of Django Commons, it applies to our admin team as well.

Which brings me to Lacey.

Lacey Henschel has been a key contributor to the Django Commons admin team since day one. She was "in the room" for our very first meeting, and for the better part of two years she had a hand in just about every part of how the organization works. A short list of what that looked like:

  • She drove our effort to bring Django REST Framework into Django Commons ... easily the most ambitious onboarding we've taken on. She kept the transfer playbook that Storm created up to date, coordinated the logistics with the DRF and Encode maintainers, and laid the groundwork for moving their sponsorship over to Open Collective (with Tim standing up the Open Collective project alongside her). The transfer hasn't crossed the finish line yet, but wherever it lands, it'll build on the groundwork she helped lay.
  • She built our admin recruitment pipeline ... the interest form, the recruitment posts, and the criteria discussion she led ... and she pushed us to bake diversity and inclusion into how we bring new people in.
  • She created our project check-in system, including the tracking spreadsheet and the regular check-in discussions that keep our member projects healthy instead of quietly going stale.
  • She opened the door to the DSF, drafting and sending the outreach that started our conversation about becoming a recognized working group, and partnering on our governance documentation.
  • She represented Django Commons out in the world, including a Lightning Talk at DjangoCon US 2024 that put the project in front of a much wider audience.

But that list undersells her.

More than any single deliverable, Lacey was often the conscience of the group. When we hit the hard calls ... like whether to step in on a project without its maintainer's blessing ... she was the one reminding us to respect maintainers, to weigh the trust of the community, and to not cross a line just because we could. That kind of judgment is a lot harder to put on a list than a playbook or a spreadsheet. It mattered just as much.

Lacey has decided to step down from being an admin. She will be missed greatly, but her stepping back also shows that what we're doing is working. Lacey let the other admins know that she needed to step away, and we all agree that an admin being able to do that ... cleanly, and without guilt ... is a big win. It shows that the ideas Django Commons is trying to accomplish are working.

So, thank you, Lacey. For the playbooks, the spreadsheets, the hard conversations, and for showing the rest of us that taking a break isn't a failure of the plan ... it's part of it.

Please welcome our new admins

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.

Daksh P. Jain

Daksh P. Jain is a freelance design engineer (read: full-stack engineer and UI/UX designer) with 3 years of professional experience building products people actually enjoy using. Based out of New Delhi, India, he works across backend systems, frontend, cloud, and product design. He is also an active part of the Python community, organizing PyDelhi (Delhi's local Python community), and helping out with Django India and EuroPython.

When he's not overthinking if a design is good, or messing up Django migrations, he's probably playing guitar or going down a rabbit hole in psychology, sociology, or philosophy (and occasionally writing about it too).

Tilda Udufo

Tilda is a software engineer and Developer Advocate with a background in open-source community building and mentorship. Through her work with Outreachy as a program organizer, she helped onboard and support dozens of mentoring organisations and hundreds of contributors each year, working to make open source more accessible to people from under-represented backgrounds. She has also mentored with both Outreachy and Google Summer of Code. Her open-source contributions span OCaml, Public Lab, Mozilla, and PyLadies, among others. Outside of tech, she unwinds with Lego builds and a good thriller.

Thanks to everyone who applied!

We also want to express our gratitude to all the people who applied to be an admin. Your time and energy was greatly appreciated. We look forward to engaging with you more in the future in the Django Commons and Django communities!

Looking forward

The admin team has been working towards this since last September when we did our team check-in. We had members who expressed an interest in stepping back if there were someone to take their place. This forced us to revisit what we expect out of admins, what gaps we had and who we wanted to bring in. So while our team is eight, the team may shift in size again as the new members become acclimated and others feel comfortable to step back.

The other change we made was to create two tiers of admins in the organization. We now have super admins and admins. The super admins are the people who have permissions to control PyPI and our sensitive internal operational controls. The admins retain elevated privileges in GitHub to manage the organization. After a yet undefined period of time, maybe six months, admins will be eligible to be elevated to super admin status if they’d like the responsibility.

Breaking the responsibilities up at the top level allows us to recruit people who aren’t in our direct networks and provides a clear pathway for people to step in and build that highest level of trust in the community.

We're recruiting new admins!

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

Read more about the admin team.

How will I know if I'm selected?

Applications must be submitted by March 16th, 2026 AOE. We will send a response to all applicants by April 1st, 2026 AOE.

Our aim is to onboard 1-3 new admins between now and April 30, 2026. Selection of new admin members will be made by the current admin team.

What qualifications do I need?

You must be a Django Commons member. You can join today! Beyond that, we don't have specific requirements. It's helpful, however, to have experience helping in open source communities. We are looking for people with experience as project maintainers, open source contributors, community organizers, conference organizers, community managers, Djangonaut Space participants, writers of docs, or people with other kinds of open source experience.

How do I apply?

Fill out this Admin Interest Form by March 16th, 2026 AOE.