Creating canonical Django packages - Part 2

I have been pondering more about my topic from Friday, especially as an email from Caleb Porzio announcing that FluxUI is now live dropped into my inbox this afternoon. To quote the lead paragraph

The official Livewire component library.

While FluxUI is one step removed from Laravel itself (though Livewire), Livewire is hosted on a subdomain of Laravel.

To me this begs the question (which is another spin on Friday's post). What is the definition of something being "official" in the Django ecosystem?

Some probably mean it's a feature being in core, others probably think it's being hosted by the Django Github organisation. Finally there is something just being recommended through out the community which is fuzzy at best!

I think clarifying what makes something 'official' and then what support these packages get (from the DSF or a working group maybe?), this could be some budget, promotion on djangoproject.com in the appropriate place and a subdomain? I guess what I am proposing is something of a package that we as a community could take to the maintainers of the relevant packages to help them keep maintaining the packages they maintain. Something of a marketing bundle or the beginnings of one. Thinking about it, Ithink this would be a perfect thing for the draft packaging working group to consider.

Ok, that's enough for today. Tomorrow some more Django thoughts coming your way!