I love that you published this as a blog post @pauloxnet, those ideas are pretty inspiring in their own right already.
–
For everyone involved, I’ve made a few changes to the form I’ve sent you:
The “Your availability” question is now towards the top. We have the meeting provisionally scheduled about a week from now, either 29th or 30th, so if intend to join and haven’t already please take a moment to fill this in. I have greatly reduced the number of slots so people have an easier time picking.
“Link to your ideas document” is now optional, if you wanted to participate without submitting ideas of your own ahead of time (that’s completely fine).
The meeting
For people looking forward to next week’s session, here’s a demo of the format we will use for the meeting. With so many of us involved, this will only work if:
Everyone has access and reviews everyone else’s submitted ideas a day or so ahead of time, so there’s time for people to read everything if they want to.
Most of the interactivity during the meeting will be via voting or other similar types of things we can do on a shared document all at the same time.
To make the most of this voting, you will have to be logged into a Google account. Anonymous voting will be possible but it won’t work nearly as well.
There won’t be back-and-forth discussions, unless we have time at the very end. I’ll invite people to share their thoughts on the proceedings at multiple times, but no other “back and forth”.
At the end of the meeting, if all goes well, we’ll have a list of 3-5 quick wins and 3-5 big project ideas, each with a sense of how to make it happen. And I will publish the doc in the format we used during the meeting.
I hope this all makes sense – next step will be for me to collate all ideas, hopefully this Friday. Please do add controversal ones, wild ones, tiny ones, things that aren’t just Django features! We want people thinking outside the box here.
@sabderemane and I are presenting an in-person session very similar to this roadmap workshop, today, at 18:00 CET, at the Django Meetup Cologne. I’m told this will also be available online. Our format will certainly work great for online participants too.
for people intending to join, I’ll set a deadline of tomorrow evening to reply to the form and Doodle I’ve set up. Then I’ll book the exact time of the meeting.
If you’ve already responded, I’d also appreciate you taking another look at the Doodle and double checking your availability so we have as many people as possible attending.
Sorry for the abrupt ending, though I’m happy we definitely ended on time! Thank you again to everyone who submitted ideas and joined the meeting!
I’ve now marked the document as comment-only, will keep it as-is in case I make mistakes, and set up a copy with all of our work structured more nicely for wider sharing. It’ll then be shared here, simple as that.
Please use our brand new feedback form if you have thoughts about how the session went / if you want to see more of this in the future.
Some of these have no “make it happen” steps defined nor any “next step” – that’s fine, it just means we’ll need someone else to pick them up.
The document allows commenting if anyone wants to assign themselves an action or make minor tweaks. For further discussion of the ideas, I would recommend creating a forum thread.
Further interesting items
The following items weren’t discussed but they all received more than one vote, and we would have gone through them if there had been more time:
Here as well, if any specific idea feels interesting to people I’d recommend starting a new forum thread about it (or finding an existing thread).
We want to keep the momentum up, so do all keep posting here, on social media, Discord, etc if you want to report your progress on your actions . And thanks again for taking part in this!
There’s no-one working on it per se. It’s something I’ve been thinking about, so put my hand up to draft up a post about some of the obvious considerations to get the ball rolling. That’s currently on my back-burner bubbling away.
Meanwhile, there are lots of folks working in the space. On passkeys, I know @ryanhiebert is thinking about it heavily. There’s work on the Kagi package (not the search engine). I saw AllAuth got some funding to work on it too. So lots going on. (A good impetus builder is a review and summary of all that activity to help bring threads together.)
I’m very much interested in Make some recommendations about front end 3, and I can see it’s assigned to the accessibility team. But where could I see current discussions and progress about this task?
I think the “Making it happen” are key stakeholders rather than an assignee.
Above Thibaud mentioned:
if any specific idea feels interesting to people I’d recommend starting a new forum thread about it (or finding an existing thread).
So, you could start a forum thread on this topic and share your ideas as to how to approach this.
Some thoughts:
Django follows Diataxis. To me, this sounds like we need an “explanation” (Explanation - Diátaxis) and we could have a new topic in our docs for “Frontend approaches”.
Decide clear goals for the documentation (what will the reader get from this?)
Use the Developer Survey results to drive decisions as to which frameworks are worth specifically mentioning (Django Developers Survey 2022 Results) like React, htmx, Vue (etc.)
Circling back to this some time later — and I’m impressed with myself it’s the same calendar year and everything — I made a commitment to write up my thoughts on evolving auth.User.
That’s now available to read here:
It’s quite long. Sorry. — I think we need to rethink how we’re doing some things, so I had to make the case at length. It’s probably not as tight as I’d like either, but I reached the limits of what I had for it right now.
I’m not sure if anyone is going to agree with what I have to say, any or all of it, but hopefully it can act as a starting point for discussion.
@thibaudcolas I’d like to thank you again for organising this workshop. As slow as things move, I think it was awesome, and exactly what Django needs!
Just wondering - should that discussion be here, or should it be a topic of its own? (I’m inclined to believe the latter, but only because there are other topics here that may deserve further conversation and that this topic could become unwieldy as a result.)
Thank you again to everyone who submitted ideas and joined the meeting!
10 
1
— I think we need to rethink how we’re doing some things, so I had to make the case at length. It’s probably not as tight as I’d like either, but I reached the limits of what I had for it right now.
