Django Commons a year later
A year ago, I put out a call for help with Django Commons, a community organization to support Django and Python package maintainers. As of today, there are five admins (Daniel Moran, Lacey Henschel, Ryan Cheley, Storm Heg and Tim Schilling) and eight projects within the community.
Quick side note: if you’re not a member already, please join!
The admin team has been meeting every two weeks. There was a long effort to put together our governance documentation. I sincerely appreciate Storm and Lacey for seeing that through for us.
We’ve had several discussions in the organization. Admittedly, these seem to be siloed off from the rest of the Django community. We’re considering ways to get more people involved in these discussions, but have no concrete plans yet.
In my original announcement, I identified five areas that I’d like to see Django Commons grow into in the future:
- Identify and announce packages needing help
- Normalize and support maintainers stepping back
- Support and encourage new contributors to step up
- Provide best practices for package maintainers
- Compensate maintainers
Surprisingly, we’ve made inroads on some of these already!
- We’ve been working on project introduction videos (first video)
- There’s a project to define best practices for Django Commons repositories
- Maintainers can accept funding through thanks.dev and Tidelift
- django-debug-toolbar donated $100 back to the DSF on May 8th
The admin team met last week to define some of our goals for the next three months. One of our goals was to get the website in a working state!
If you have any questions about Django Commons, please reach out to us on GitHub in our discussion area. If you have thoughts, comments, or questions, please let me know! You can find me on the Fediverse, Django Discord server or via email.