Actually, you’re right. Sometimes we are used to making testing everywhere so I agree.
I’d like to know what others think, especially our moderators: @dnutan@Jim@stephdl@m.traeumner@dnutan@enzoturri
This category is for topics related to testing on NethServer: testing new modules or rpms, discussions about QA on dev.nethserver.org
It could be changed to make aware of new rules, for instance:
Do not use the “testing” category, it’s obsolete
For “discussions about QA” => use “community” category
For “testing new modules or rpms” => use “testing” tag
@alefattorini can you “close” the Testing category, preventing its assignment to a thread?
As alternative, we could remove the testing category and massively assign the “testing” tag. But we should select a new category for each thread… It does not seem a good idea!
People involved in an issue tracked by GitHub/Dev post messages in the issue tracker. If the issue is related to a discussion here it already has a category assigned: usually Bug, Feature or Support request.
If the QA discussion is not related to an issue tracked by GitHub/Dev and does not fall in the categories above it’s probably about the QA team, thus Community.