You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From now on we only had a generic framework classifier Framework :: Masonite. We would like to track Masonite related packages on PyPi and have as Django a classifier for each minor version.
Hi! Thanks for the request. Because removing classifiers is very difficult, and the longer the classifier list gets the harder it is to browse, the bar to add new ones is relatively high. Currently, PyPI moderators primarily examine two guidelines for Framework classifiers:
New Framework classifiers should be created if they are "notable" and
They will be of immediate use to existing projects (in other words, no creating classifiers simply in anticipation of future uses)
We understand that "notability" is subjective and we'd appreciate help judging that. Information like level of adoption (# of users), packages/projects that use this framework would be useful for this.
As to the other guideline ('immediate use to existing projects'), the best way we've found to demonstrate that is to have 10 or more other project maintainers submit comments on the requesting issue about their desire to use the classifier. Is that something you could assist with?
changed the title [-]Add new Masonite version classifiers[/-][+]Add `Framework :: Masonite :: 4.0` and `Framework :: Masonite :: 4.1`[/+]on Jan 14, 2022
Activity
pradyunsg commentedon Jan 14, 2022
Hi! Thanks for the request. Because removing classifiers is very difficult, and the longer the classifier list gets the harder it is to browse, the bar to add new ones is relatively high. Currently, PyPI moderators primarily examine two guidelines for Framework classifiers:
We understand that "notability" is subjective and we'd appreciate help judging that. Information like level of adoption (# of users), packages/projects that use this framework would be useful for this.
As to the other guideline ('immediate use to existing projects'), the best way we've found to demonstrate that is to have 10 or more other project maintainers submit comments on the requesting issue about their desire to use the classifier. Is that something you could assist with?
[-]Add new Masonite version classifiers[/-][+]Add `Framework :: Masonite :: 4.0` and `Framework :: Masonite :: 4.1`[/+]