-
Notifications
You must be signed in to change notification settings - Fork 44.7k
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
Grant capability to label bugs as such #469
Comments
I have reached out to @Torantulino to see if he's willing to grow the number of people with some kind of write access to the github repo so more people can help out. |
I wonder if we can setup a secondary repo of a sort where we can merge all pull requests @Torantulino approves. So that we help and it's safe in the sense that we can't do harm. I guess with the 13k stars he woke up a celebrity overnight and it's hard for him to manage it all in all senses, including both technical and personal. |
Or just an experimental branch, with different push permissions. It's very early days with lots of people keen to contribute. I'm sure it's something he's thinking about. |
I think we really need a label ":skull:JSON" |
This is now in hand. @Torantulino has started a small team of collaborators and we will be working on this going foward. |
@richbeales I recommend using emoji in the labels - the eye is immediately attracted to them and it also makes tags more unique. |
Duplicates
Summary 💡
Many of the issues aren't defects. I'm willing to help you by marking bugs as such in the tracker using labels. I will only add "bug" labels to bug reports at the moment so you see my capability and I don't disrupt anything.
But ATM I lack permissions.
Examples 🌈
This same issue is hard to separate from bugs
Motivation 🔦
The project is poorly managed and there are many types of reports lumped to gether. I can help with the project organization.
The text was updated successfully, but these errors were encountered: