The aim is to manage issues on AR.js new official repository: https://github.com/AR-js-org/AR.js/
You should:
- sometimes, sporadically, give a look to the old repository https://github.com/jeromeetienne/AR.js/: you will not be able to close/open issues in there, I cannot give you technically those permissions, but you can left a comment if you find someone is opening new issues (they should not, that repo is deprecated). A message could be the following:
Please open issues on the new repository of AR.js: https://github.com/AR-js-org/AR.js/
Please open issues only if your request is a feature request OR a bug.
If you need help/troubleshooting, it's better to write on the [Gitter Chat](https://gitter.im/AR-js/Lobby) or write on
Stackoverflow with 'ar.js', like here: https://stackoverflow.com/search?q=ar.js
-
On the new Repository (https://github.com/AR-js-org/AR.js/), when someone opens an issue, if it's related to 'location based', please add the label (on the right): 'location-based'
-
Try to answer on the issues where you know the answer for sure
-
If an issue is duplicated, and you're sure about that, close the new one, and write a comment to redirect the users on the 'old' one
-
If users open issues that ARE NOT bugs or feature requests, close them with this message:
Please open issues only if your request is a feature request OR a bug.
If you need help/troubleshooting, it's better to write on the [Gitter Chat](https://gitter.im/AR-js/Lobby) or write on
Stackoverflow with 'ar.js', like here: https://stackoverflow.com/search?q=ar.js
- if users open an issue that is actually a bug OR a feature request, ask them to be precise: issues with simple title, no description, or not understandable description: do not close them but ask users for more details. If they will not add them, in like two weeks, close the issue for lack of interest by the user.
Maybe would be better for Gitter point to the help-support room instead of Lobby, as most of the people request generic help...