-
Notifications
You must be signed in to change notification settings - Fork 703
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tag naming / checking #399
Comments
Stemming and case insensitive searches are not rocket science... I don't see any problems here. |
PRs to clean up tags are always welcome! |
At the very least, can "nim" and "nimrod" be removed as tags? They're rather pointless as every package is going to involve Nim anyway. |
Sure On Monday, 29 August 2016, Adam Chesak notifications@github.com wrote:
|
Can we close this one - tags are really the author's call. If they put in junk tags, it does their own package a disservice since it will show up for random searches. I presume tags are also reviewed when packages are added. |
Having just started adding my package to the package list, I was looking at the existing tags to see which were most appropriate. I found a lot of duplication. A few examples from the start of the alphabet:
The list goes on (and even includes "Nim", "nim" and "nimrod"!)...
If these tags are ever selected as the means of trying to search/filter packages, it's going to be very hard to actually find anything useful I suspect.
The text was updated successfully, but these errors were encountered: