Discussion thread for "Django’s technical governance challenges, and opportunities" blog post

We’ve just published a blog post about the current technical governance of the Django project, the upcoming Steering Council, and what’s coming next - please take a look:

Here’s a thread for discussion/questions – if you have questions ask 'em here! You can also reach out to the board privately at foundation@djangoproject.com. Or finally, you can come discuss with us at our regular Office Hours, every Wednesday at 6PM UTC. Contact me (or any other board member) for the joining info if you need it.

3 Likes

No question but more of a comment :wink: Just wanted to say thank you to all the people who have been working behind the scenes to help our community navigate those challenges. It’s not all been great, but certainly I know a lot of our community members have a positive outlook on Django’s direction. As board members, we felt it was important to publicly state the challenges / threat, and our commitment to getting those resolved. But despite the tone, we feel great about the prospect of newly-elected Steering Council members resolving those issues.

Personally – I’m really looking forward to those upcoming early Steering Council elections, and even more so to Django in 2025

4 Likes

I don’t know how much it’s intended here to get into the long-grass of an actual governance change, but there was one bit that really stuck out to me:

There’s a lot about the Steering Council that is good and might only need minimal changes.

I think that’s right. The main problem I saw (first as Fellow and then as not-Fellow) was the voting mechanism acted to both remove the SC from discussion and shut down discussion, whereas ideally the SC needs to be involved, and (somehow) facilitate the exploration towards consensus. :thinking:

I’d try to make the formal vote a kind of last-line type thing, if we can work out how to phrase that.

I’d also ease the voting requirement at each step of a DEP’s progression. It proved painful. (A clear Let’s advance and then a difficult voting process to manage, taking at least a week minimum…)

Finally, a more organic vote should be available, even if we get to that stage: it seems reasonable to say “Exact wording A isn’t right, but can we tweak to…” without needing to scrap the vote and start again.

All of those are immediately long-grass, so we might want to just put those on the shelf for now. The essence of it is slightly less formal though. We’re a small org; we should leverage that.

However, the overall question of the Steering Council’s remit, and how it approaches technical leadership for the Django community, needs to be resolved.

I think we need the SC to be more involved. A couple of times we had a situation where we needed/wanted SC guidance but the response was (along the lines of) we can’t really speak without a formal vote being proposed — which didn’t help. All four members were/are experienced community members and their opinion is valuable, and can help guide the discussion.

I don’t think the SC can or should do everything or decide everything but if they can act as a focus to facilitate (or delegate facilitating) the discussions (beyond the small day-to-day, which runs itself) I think that would help us. I guess that ties into the word “Roadmap” that appeared in the post (and was one of the points not really implemented from DEP 10).

Thanks for posting, and getting the discussion started! :gift:

11 Likes

Couldn’t agree more, but I’d broaden things. The Steering Council need to take ownership of the end-to-end contributor journey. Or leave it to the Board if they don’t think it’s their remit. From people using Django for their first time and having feedback or an idea, to leadership positions.

I made the point in a forum discussion a year ago that we need to be more respectful of people’s time. The roadmap is one thing but there’s also the thousand cuts. Can’t tell you how gut-wrenching it feels when you work with a newcomer on a great bug report and you hit Trac’s spam filter, which thinks you’ve just been a bit too thorough with your linking to relevant resources.

Anyway, we’ve announced our 6.x Steering Council elections :rocket: now and that’s the clearest opportunity for people who want to change this and have the requisite time and energy available. And we also have our live 2024 Django Developers survey with more questions than in past years about ideas to evolve Django.

2 Likes