Finding opportunities to contribute to Django
- schillingt
- Dec. 16, 2025
When folks want to get involved in open source, they tend to want a very specific set of directions to accomplish that. π Which makes sense, they want to start on their journey and there are likely checkpoints or markers for it. β¨ They should be able to follow those all the way to, umm, open source involvement? π
Which brings up a big challenge in helping people get started with open source software. π If you're giving a person directions on where to go, you sort of need to know where they want to go. But that person likely doesn't know. πͺ I know I still don't! So how do you help this person navigate the entirety of open source without knowing their destination? π
By providing them a map of course! πΊοΈ Think of an amusement park or a museum. They don't know what you want to see, but they know what they can provide and where to go for that experience. π Perhaps they want to stare and be confounded, so they use the map to find the tea cups ride or the abstract oil paintings. π
This leads me to my proposal for the community. π We should provide a map for newcomers to find their way. π
Or at least the next leg of their adventure. β¨
The physical map!
Obviously a map is a tangible thing and we should be able to physically represent it! πΊοΈ
I'm imagining a isometric, cartoonist map. π¨ It has in the center is a series of giant construction equipment that is then being worked on by artisans. There is scaffolding and cranes. Pieces being moved around and things being built. ποΈ This is where Django core is maintained. π
Off to the side is a great communal forum. People are standing about chatting, discussing and listening. π¬ As you suspect, this is the Forum. β¨
There would be an area of carnivals for the DjangoCons, with people dancing, frolicking, having a good time. πͺ
There should be several small forts, each of slightly varying size and robustness. π° These are the local meet up groups. π
There should be a launchpad on the map for Djangonaut Space. π You should be able to see Djangonauts boarding a rocket while there's another circling around above the Django core area. πΈ
There should be an entire section that's more wilderness with a random piece of large equipment. π² This realm is the third party package area. This area should have Awesome Django, Django Packages, Django Commons and Jazzband identifiable. π
Part of the map would need to identify the commercial users of Open Source. Perhaps it can identify a few long-term partners. Perhaps a city representation would be best. π’ It definitely would need to show the Django Newsletter as a town crier. π’
There should be Django Girls, the board, the working groups, the teams, the groups of people who do things for the community without designation, the online communities, the office hours, and everything. It should be beautiful in both illustration and intricacy. π
A more reasonable start
Even if we don't get that fancy visual, perhaps we can start somewhere. π I think a list of groups that summarizes what they do, how that role benefits the volunteers and has a link to learn more. π
The way I envision this working is that a prospective contributor browses to the page and they are presented with a wizard that allows them to select various things they want to achieve by contributing to open source. π The point is to be light-weight and allow people to explore. They don't need to set their course in stone, but they should be able to see what a journey may look like given a particular choice. π
When they select a interest/tag/topic, a grid of relevant opportunities below would appear below. ποΈ These opportunities would include basic information, such as what it is, what it does for the community, what skills it would help a person develop, and where to go to learn more. β¨
From there they could decide if there's anything they'd like to pursue! π
Beyond a map
There's another goal to this that's probably a bit obscured. π It goes beyond improving the visibility of projects/initiatives/teams. It nudges those groups towards considering their on-boarding and their governance. π
If you're in charge of a repo/org/team and you have a pipeline of people coming to your org wanting to contribute, but knowing how, how would you do things differently? π€ Would you setup a specific page for them? Would you hold quarterly webinars on contributing? π‘ Would you route them to a FAQ on what the involvement actually looks like? Maybe you're especially interested in people that have certain skills? β¨
None of those questions can only be answered with a where-to-contribute map. πΊοΈ But perhaps, that map will encourage people to come up with better answers. π
Add to the map
Do you have a contribution opportunity for Django?
π Take a look at our map, and create a PR to add your opportunity! πͺ