I have one question about referring to relevant, fairly well established, open source third party packages that are very helpful for common tasks like say… updating django in official django posts.
Adam’s Johnson’s Django Upgrade package is a godsend, and used by loads of people. Here’s the link:
Is there a required threshold for usage, longevity before 3rd party projects might be mentioned in official blog posts from django?
It would also be nice to recognise Adam’s work, and using the django blog to support the ecosystem would be a nice way to spread the love.
If this is a thing you’d be supportive of as a reader of the django blog, would you chime in below?
I’d like to propose it to the DSF, once I’ve figured out the best way to do so.
Absolutely. There’s no reason we… no hang on… stronger than that… we absolutely should be linking out to ecosystem resources more than we have done historically. (It’s a different world than it was)
Django Upgrade is a great aid, and I’d like us to make the decision to include it as a recommended resource for Django release posts and notes, and the upgrading How To.
+1 to that. I think there should be (a lot) more willingness to say “this thing is a community package but lots of people like it and use it” in official Django materials, and this is a perfect example where that could really benefit people looking for help.
There has been a previous discussion on this topic.
See the thread at Proposal: add officially endorsed packages to Django docs. In particular, I’d like to draw your attention to Andrew’s response at #6, and Adam’s response at #8 to see some of the potential downsides that have been identified.