Request classifier Hydrology: Topic :: Scientific/Engineering :: Hydrology

[raoulcollenteur]

Request to add a new Trove classifier.

The name of the classifier you would like to add

• Topic :: Scientific/Engineering :: Hydrology

Why do you want to add this classifier?

There has been a steady increase in the use of Python in Hydrology, becoming one of the major programming languages used. It would be nice to centrally document all the packages to keep track as a community. I would expect between 50-100 packages in a short time frame (one year), based on a list I maintain of Python packages: https://github.com/raoulcollenteur/Python-Hydrology-Tools

It would be great for our community if this classifier would be supported!

[jamadden]

Hi! Thanks for the well written request. The PyPI moderators are in the process of developing a few guidelines for the creation of new classifiers. Because removing classifiers is very difficult, and the longer the classifier list gets the harder it is to browse, I think we're expecting the bar to add new ones to be relatively high. Currently, we're looking at these guidelines:

• New 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. I think the information you've already provided establishes that there is plenty enough interest in the topic to consider it notable.

As to the other guideline ('immediate use to existing projects'), it's been suggested that

• Requestors can demonstrate this by providing links to 10 or more existing PyPI projects that will use the classifier; or
• Another way to demonstrate notability would be to have 10 or more other existing PyPI project maintainers submit comments on the requesting issue about their desire to use the classifier.

I spot checked a number of entries on the list you pointed to and was able to locate at least 10 existing PyPI projects that have published releases in the last 6 months or so.

I think we can consider all the guidelines met. I'll plan to add the classifier in a few days, to allow any other @pypa/pypi-moderators a chance to weigh in.

(If nothing has happened in a week, feel free to ping me to remind me!)

[theacodes]

I'm +1 on this classifier.

…

On Thu, May 16, 2019, 1:55 AM Jason Madden ***@***.***> wrote: Hi! Thanks for the well written request. The PyPI moderators are in the process of developing a few guidelines for the creation of new classifiers. Because removing classifiers is very difficult, and the longer the classifier list gets the harder it is to browse, I think we're expecting the bar to add new ones to be relatively high. Currently, we're looking at these guidelines: - New 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. I think the information you've already provided establishes that there is plenty enough interest in the topic to consider it notable. As to the other guideline ('immediate use to existing projects'), it's been suggested that - Requestors can demonstrate this by providing links to 10 or more *existing PyPI projects* that will use the classifier; or - Another way to demonstrate notability would be to have 10 or more other *existing PyPI project* maintainers submit comments on the requesting issue about their desire to use the classifier. I spot checked a number of entries on the list you pointed to and was able to locate at least 10 existing PyPI projects that have published releases in the last 6 months or so. I think we can consider all the guidelines met. I'll plan to add the classifier in a few days, to allow any other @pypa/pypi-moderators <https://github.com/orgs/pypa/teams/pypi-moderators> a chance to weigh in. (If nothing has happened in a week, feel free to ping me to remind me!) — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#5728>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAB5I42KGIUXTNUGUAMF2RLPVUOQJANCNFSM4HHMKVZQ> .

[raoulcollenteur]

That is great! Thanks for looking into this issue and (hopefully) adding the classifier. I'll make sure to reach out to the community and have package maintainers add the classifier once it has been added.

I agree it is a good idea to specify what "notably" means by adding the two additional guidelines that are suggested to avoid any discussion on when a classifier is notable.

As for your comment that the

"longer the classifier list gets the harder it is to browse"

I would think this might be something that could be solved by changing the way we browse for packages on https://pypi.org/search/. For example, not opening all the sub-categories by default in the "topic" tab might already improve the ease to browse for users.

Just my two cents :)

[jamadden]

Topic :: Scientific/Engineering :: Hydrology has been added to pypi.org and test.pypi.org