-
-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃 Re-think our Categories #1135
Comments
@jefftriplett I like this idea a lot. What if there was a category for what would be the best / easiest way to get the packages from the Other category to do an analysis of their various attributes? |
@ryancheley Packages support trove classifiers if we want to get fancy. We should also figure out a good way to create a bigger test database to work off of. That might help us run some local stats on packages and grids. |
I usually use the APIv4 to fetch data from djangopackages.org locally and populate the database with a script, It works quite well for me if I need to test (rarely) with larger datasets. |
I did a cursory review of the Other category and found:
It seems like one or both of those might be good categories. For the Django CMS / Wagtail how to we help people know when to add a package to one of those categories versus Frameworks? |
Here is another datapoint based on the the pypi url: >>> Package.objects.all().count()
5308
>>> Package.objects.exclude(pypi_url__in=[None, ""]).count()
4297 R: For the Django CMS / Wagtail how to we help people know when to add a package to one of those categories versus Frameworks? I'm not sure. It feels like those two are big enough (they even have pypy trove classifier tags) that we could enforce an opinion to make it easier? |
@jefftriplett after the conversation during office hours yesterday I was thinking that packages like |
@ryancheley on that note, how do you feel about a Django CMS and a Wagtail categories since we have trove classifiers for those? It might be something we can keep updated with a script. |
While there isn't a Django REST Framework trove classifier, it's big enough to warrant one, too. |
@jefftriplett I think those all make sense. If we can get to 8 categories and Other then we have a nice 3 x 3 grid for categories as well 馃槃 Right now it looks like we have 7 (plus Other) so we鈥檙e only one short
|
How about we add a new category for Django testing tools? |
Django Packages currently has four categories:
settings.INSTALLED_APPS
, are not frameworks or sites but still help Django in some way.Now that "Other" is our second-biggest category, I wonder if we should dive into that a little and figure out if we should have a fifth category.
I suspect we have a mix of general Python third-party apps like ruff, black, and celery which might be of value if they are on pypi vs. awesome-django which is a good community resource.
Also, would Wagtail make a good Category or Django CMS because they both have dedicated pypi trove classifiers?
The text was updated successfully, but these errors were encountered: