On the importance of DjangoCons

I mentioned this on Django Chat this week, but I wasn’t pleased with how I remember it1. I don’t know if I communicated my opinions and ideas as well as I’d like. So I’m going to use this post to express my opinions more fully. There are several motivating factors for this.

  1. I’m on the board of directors for Django Events Foundation North America (DEFNA)
  2. I’ve been an organizer for DjangoCon US the past two years
  3. DjangoCon Europe had some difficulties finding organizers
  4. DjangoCon Africa is coming back for 2025
  5. DjangoCon US had fewer sponsors
  6. DjangoCon US attendance hasn’t risen to pre-pandemic levels
  7. The Django Software Foundation (DSF) board elections are in about one month
  8. The Django Steering Council (SC) elections are in five months

The benefits to an individual

The benefits for contributors

The benefits for the community

The benefits for a company sending its people

What to do understanding the importance of DjangoCon

Hopefully, I’ve convinced you that DjangoCons are a critical component to the Django community. I feel that those of us who are in community organizer roles should revisit our approaches to DjangoCon.

Warning, personal opinions inbound

In my ideal world, all the following would be true:

  1. The DSF and all DjangoCons have a large, multi-year sponsorship opportunity

    Sponsorship is challenging. At times, we’re being told we’re not asking for enough money. And we’re also being asked to provide even more benefits. I think the DSF having an arrangement with at least one company for a multi-year sponsorship that results in a baseline level of sponsorship for each DjangoCon would help tremendously. There are several details that would need to be resolved. This is also likely something we’d need an Executive Director for, but it’s something I’d love to see.

  2. DjangoCons are well attended by community leaders and be available to folks

    Being able to meet and talk to folks you look up to is one of the major benefits to a DjangoCon. I think it’s important for our community organizers to be aware of the impact you may have on others and to pay it forward when it’s sustainable. I’d argue this is near critical for any elected members of the community. To help make this an easier choice for folks, the DSF should have a line item to cover at least a portion of an elected member’s travel to one DjangoCon.

  3. DjangoCons and various community groups are better coordinated for collaboration and cross-marketing

    The DjangoCons can do a better job of helping people identify their local Django and Python meetups. We could start by reaching out to those communities to ask if they are sending anyone to the conference and if they’d like to be listed on the conference website. In return, they’d be asked (not required) to announce key dates on behalf of the conference (CFP, tickets on sale, talks announced, talks published). From here, my hope would be that the regular communication would evolve into something more robust and collaborative. Potentially making it easier to find volunteers to host a DjangoCon in the future.

  4. DjangoCons are more prominently marketed on the djangoproject.com and various community groups’ pages

    When a person is looking to get involved in the community, we should be telling them when the next major and regional Django events are happening. Additionally, I think it’d be a good idea to normalize package maintainers and community organizers to be able to advertise their presence at the conference. This could be a simple list of affiliation, name and link on the particular DjangoCons page. On the community member side, it should be more common to announce that you will be at said public event. This can improve both your opportunities for collaboration and discovery. It also benefits the DjangoCon by lending it additional legitimacy by showing that looked up to community members find it important enough to announce their attendance.

I understand some of these can only be implemented by a select number of people. However, with elections coming up, it’s essential to consider what you want to see out of the Board for the future of Django. The others are more accessible. Anyone can open a PR against djangoproject.com. Anyone can be an organizer for a conference to help on the website and community teams.

Personally, I will be attempting to do a better job of #3. It’s an easy win, and I’m currently well positioned to improve that. So if you’re a community organizer that would like to improve collaboration with DjangoCon US, please let me know.

You can find me on the Fediverse, Django Discord server, or reach me via email.

  1. I haven’t actually listened to it yet. 

  2. Or maybe we should normalize it. 

  3. Ideally we wouldn’t be purely volunteering our time and would be compensated, but I’m discussing what the typical reality is currently. 

  4. I feel like the sporadic cadence and fleeting nature of a conference contributes to this effect. If we met more often, we’d be less likely to rush to say everything we have wanted to each other. 

  5. It feels like a conference could provide a process for employers to have a sign-up sheet with time slots and a list of their top 3 desired technical skills.