-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[META] We *need* issues moderators #3227
Comments
I agree. I think if certain issues that are shown to be useful as well they should be pinned. Might make the process of writing the documentation back up. |
You are right ! Maybe we should create a new doc, or at least improve the existing one. And Maybe make the installation instructions i18n ? |
Well we can submit PRS to the readme, but until the devs are finished tweaking the bottom I don't know whether that would just be more hassle for them - maybe they'd want to write it themselves to keep it consistent I dunno... |
Bot* |
Devs can't do everything :x |
We definitely need help managing the issue tracker. We haven't discussed on the team how we want to add more people to manage this. @PokemonGoF/pokemongo-bot-team, what are your thoughts? |
I'm happy to help out with moderation and documentation where I am able if the devs decide to instate some extra mods. |
👍 |
1 similar comment
👍 |
I can help. Already cleaned up PokemonGo-Bot-Desktop issues. |
I could help with the wiki, and with issues (currently, I can't close other people's issues) |
I'd happily be a janitor |
@TheSavior I think we already have some issue managers. Problem of adding random people as issue managers is that they need to have write access to the repository to be able to manage issues. And we also need people with some knowledge about Python and the project itself to be able to close issues and support people correctly for whatever is not really a bug. |
For the acces to the code you can setup an issue only repo. This way you can split the people who have acces to the code, the issues or both. Github also has a page about this: https://help.github.com/articles/issues-only-access-permissions/ And maybe you can make a simple test to decide which people are able to help you with the issue handling. BTW: I also would happily help as a janitor for the issue's (or the wiki) |
I think the biggest downside of an issue only repo is whether people from this repo will be able to find it. If we can have a satisfactory solution to that problem, I think I'm on board with that approach. |
That is true, but it would we the only sollution to give issue moderators only acces to the issue and not the code. Maybe send people to this repo with a giant link at the top of the README.md and maybe a link during the startup of the bot? So people are aware of this repo. This is not the best sollution, but maybe a better sollution than to open up this repo... |
Or closing any new issue (using a bot) with a link redirecting to the new repo ? |
External issue system? |
@douglascamata I'd rather stay on Github due to people already having accounts and our ability to easily cross link and mention people. |
@jrjhealey Are you on slack? Can you message me there and we will get you sorted out? |
Call for moderators: https://github.com/PokemonGoF/PokemonGo-Bot-Issues/issues/1 |
@TheSavior sorry man been busy so hadn't kept up this the thread. I do use slack bit hadn't joined the bot group, will sort that out today. I see from my emails you've already sorted it by the looks of things so do you still need me to drop you a message? |
@jrjhealey Yes please, if you could shoot me a message on slack that would be great. We want to bring our moderators together in a slack channel for everyone to discuss and figure out the best approaches going forward. |
Could you paste the http for the slack group? A quick skim of the wiki turned up nothing and googling for it gives loads of other hits to different pokemon bots |
It's on our readme, but here is the link: https://pokemongo-bot.herokuapp.com/ |
I'm 👍 to this blog post: "Why you must not ask questions on Github issues" / https://medium.com/@methane/why-you-must-not-ask-questions-on-github-issues-51d741d83fde |
#3363 |
Yep, thanks. |
TL;DR : We need mods
Well, due to the big attention the project receive, I strongly suggest selecting a few members, and marking them as contributors so they can close issues that aren't well detailed, already have a solution, or don't belong to the project.
We also, I think, need to classify issues into groups, so it will be easier for actual developers to see real bugs, features requests...
What do you think ?
Just as a quick note : I'm not advertising myself as one of these moderators, I just think the project needs some. For now, I am not applying for this position.
The text was updated successfully, but these errors were encountered: