He reported the problem on github. Luckily the issue was temporary, but it started an interesting discussion about the bug tracker and I would like to listen to others, too!
Because you ask me, I will be sincere. I really don’t know where to post a bug report. I came from a project where the bug report software is a central place in the development environment, with rules to respect.
I see here three places to do a bug report, discourse, redmine, github… There can be only one
We should start all the discussions here, bugs too and keep GitHub just for track issues, code and pull requests.
It has worked until now so it might be the right way. People don’t like to check many places and here it’s easier to discuss than on GitHub, it’s more inclusive as well.
When somebody files a bug on github there’s a template to fill with the required information to build a correct bug report.
Starting the bug discussion here helps to gather that information and involves more people to reproduce the bug. It is a triage stage. It also avoids filing duplicates, and invalid bugs. It keeps the bug tracker clean.
So where to file a bug? The rule is simple: here! But if all required info are known, you can also file it directly on github. However posting here helps to inform other people.
Same rule for redmine, the old tracker for bugs affecting ns6.
I’d say, same rule for problems affecting the infra, too: mirrors, packages.nethserver.org, www…
Keep in mind that a lot of bugs aren’t actually bugs but support requests, moving the category here is very simple.
Finally, several Communitties are doing the same, moving away from Github for discussions and triaging
Github is useful for its strong connection with code, PR and stages (testing, released, ecc)
Good question, we can just use “community” and tag it with "infrastructure"
I don’t think they deserve a category, I feel that they are not so numerous