Skip to content
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

New labels to tag issues that need help #11298

Closed
fernandojsg opened this issue May 8, 2017 · 18 comments
Closed

New labels to tag issues that need help #11298

fernandojsg opened this issue May 8, 2017 · 18 comments

Comments

@fernandojsg
Copy link
Collaborator

fernandojsg commented May 8, 2017

I believe threejs should adopt a similar kind of tags as many projects are using right now to guide people that want to help to the project.
For example in https://github.com/aframevr/aframe we've: help wanted (easy) used to tag simple bugs or feature requests focused on newcomers to start contributing without being overwhelmed or afraid to take a bigger task to start with. We also have help wanted (hard) for harder issues but that will be easy to spot for people that have the knowledge but don't know where they could do to help to the project.
Similar approach is used by the https://github.com/servo/servo project and many others.

I feel that when newcomers or more advanced users come to three.js, people don't know where they could help to improve the project so many interesting features needed by the engine are left undone because people don't know what is needed to be implemented as here we don't have a clear roadmap.
So you should read all the issues and try to guess and measure what you could do.

Starting with a tag as proposed, let's say as the one used in aframe or whatever you feel it could fit, people could just filter by these tags and start contributing.

@fernandojsg fernandojsg changed the title New labels to tag issues that needs help New labels to tag issues that need help May 8, 2017
@Mugen87
Copy link
Collaborator

Mugen87 commented May 13, 2017

I like the idea. This should make things more transparent.

BTW: There is actually a developer's todo list (see https://github.com/mrdoob/three.js/wiki/Developer%27s-TODO-list) but it is not actively maintained.

@fernandojsg
Copy link
Collaborator Author

Yep, probably having the tags could help to populate that TODO-list with link to the issues and people could find the relation between them all

@mrdoob
Copy link
Owner

mrdoob commented May 14, 2017

Sounds good to me 👍

@Mugen87
Copy link
Collaborator

Mugen87 commented May 15, 2017

Okay, let's do it! I've created two new labels for the project: Help Wanted (easy) and Help Wanted (hard).

@Mugen87
Copy link
Collaborator

Mugen87 commented May 15, 2017

I think we can gradually change the label Enhancement to Help Wanted(*) for some issues e.g. #10932.

@jostschmithals
Copy link
Contributor

jostschmithals commented May 16, 2017

In fact a good idea, but IMO Help Wanted(*) could be easily misunderstood - in the sense of Help (please use Stackoverflow); I needed a moment to realize that Help was was meant the other way round in this case.

I think Contribution desired(*) would be less ambiguous.

(I'm no native English speaker, but "Wanted" (especially with capital W) looks to me a little dangerous - like "Wanted - dead or alive"; so I would replace it by "desired" 😉)

@fernandojsg
Copy link
Collaborator Author

fernandojsg commented May 16, 2017

No strong opinion about any of them, but what about renaming Help (please use stackoverflow) to Question (...)?

@Mugen87
Copy link
Collaborator

Mugen87 commented May 16, 2017

There is already a Question label. It's intended for issues where users don't ask for help but have e.g. conceptual questions about the library.

@fernandojsg
Copy link
Collaborator Author

Ok, so I don't know, it's up to you I'm happy with whatever name you could propose ;)

@Mugen87
Copy link
Collaborator

Mugen87 commented May 16, 2017

Maybe we can change Help (please use stackoverflow) just into Please Use Stackoverflow?

@fernandojsg
Copy link
Collaborator Author

That's sound great to me

@WestLangley
Copy link
Collaborator

WestLangley commented May 16, 2017

I think these labels may be too confusing. It must remain clear this is not a help site.

I would go with Help (please use stackoverflow), Enhancement, and Enhancement (easy).

I think that is sufficient. Enhancement (hard) serves no purpose.

Contributors can be directed towards Enhancement tags.

@Mugen87
Copy link
Collaborator

Mugen87 commented May 16, 2017

I'm okay with this. So we actually have to create only Enhancement (easy).

@fernandojsg
Copy link
Collaborator Author

fernandojsg commented May 16, 2017

Following the same approach as the mentioned projects, help wanted (*) (or whatever name) will be used not just for enhancement but also for bugs or whatever kind of tag we could add in the future.
It's to guide contributors on what they could do, solving an easy bug or implementing an easy feature for example.

Also I expect that tag to be added for "approved" suggestions, so they're suggestions that are considered useful enough for the core to be implemented or added to the roadmap/to-do list.

So I could create both tags and add them to the issues as they're "validated". We could have issues with [Bug, needhelp] [Enhancement], [Enhancement, needhelp(easy)], ...

@WestLangley
Copy link
Collaborator

No additional help tags please. Adding Bug (easy) is OK.

@fernandojsg
Copy link
Collaborator Author

Yep, that could works, just adding Enhancement/Bugs(easy)

@Mugen87
Copy link
Collaborator

Mugen87 commented May 16, 2017

Ok, i've added now Enhancement (easy) and Bug (easy).

Please check the complete list of labels here: https://github.com/mrdoob/three.js/labels

@fernandojsg
Copy link
Collaborator Author

Perfect, thanks! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants