-
-
Notifications
You must be signed in to change notification settings - Fork 403
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
Quality facet - Add a "forbidden" words quality rule #1025
Comments
I disagree to build a new quality facet as there will be many false positives -- e.g. 7 products use "couille" as part of their name; 1689 products use "bites" in their name; etc. There should be another process. Example:
I think ideally:
|
I prefer a quick and dirty facet with false positives to RT notifications with false positives with a feedback loop that probably won't be implemented. |
Me either! But why do you think a better solution won't be implemented? There are many developers that could do that. And we can start with RT notifications without keeping false positive information. If our needs are clearly explained, it shouldn't be so long and difficult. |
I can work on this if you guys want. I think what @teolemon proposed is a good initial plan. Start with a simple quality facet first and then we can think about adding RT Slack notifications. |
@zigouras you can start working on it! I'm assigning you. |
Ok, we had a much more problematic issue which stayed undetected for several months. |
Found the N word tonight, and obviously not on the product itself |
What
Sources
Part of
The text was updated successfully, but these errors were encountered: