I understand the tension between wanting to do it right on the one hand and just do something on the other.
I think we need to prioritise just doing something in this case.
@wsvincent and I talked with @pauloxnet about getting 20tab onboard back in the summer of 2022. (This was on the back of two years, or more, of totally failing to get any momentum up doing it the volunteer way, but let’s take the 2022 date.)
Knowing how Django rolls, I was very keen to try and get the existing board then to Green Light a just do it iterative approach to updating the site. Timing didn’t quite work, the board elections came, and the new board came in, and they — absolutely rightly — wanted to get up to speed, and take a more measured approach.
But that was three years ago, even taking the 2022 date. And the homepage hasn’t changed at all.
I think we need to be honest about our capacity — or lack of it — to push through projects doing it right on the volunteer effort that we have available.
Otherwise we’ll be here in another three years, still with nothing changed.
I get that we want it all. But we’re frozen. We need to get out of our own way.
§
Meanwhile, the same refrain continues to be heard — Django is in existential danger from its inability to compete with the Next.jses, FastAPIs, or whatever — put in your own one — of the world.
This was the exact same angst we faced in 2022 (and earlier). The exact same points. The exact same concerns.
The biggest challenges aren’t technical. (@FarhanAliRaza is busy proving that) They’re that we’re not communicating what Django has to offer. If we’re losing share™, that’s why.
I take the long view. I’m not particularly worried about Django. I think the concerns are overplayed, and that if there’s a more popular Python web framework, that’s OK. (It’s old as Django itself that Django faces imminent death.) Nonetheless I keep hearing talks and reading posts about how folks are concerned. (And maybe eventually the predictions of doom turn out right.
)
BUT this question here. Are we capable of updating the website? is the big one. It’s the most pressing topic Django faces.
I put it to you that doing it right has proven to be too slow. I suggest we authorise @adamghill (and a small team) to just do something — it won’t be bad! — and we adopt a policy of making iterative changes, rather than continuing to wait for all the "i"s to be dotted and all the "t"s to be crossed.
All that work is important — but there are obvious changes that could have been made years ago already.