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

Rename "Easy to Fix" label to "good first issue" #13465

Open
ylemkimon opened this issue Oct 17, 2017 · 10 comments
Open

Rename "Easy to Fix" label to "good first issue" #13465

ylemkimon opened this issue Oct 17, 2017 · 10 comments
Labels

Comments

@ylemkimon
Copy link
Member

ylemkimon commented Oct 17, 2017

GitHub has added "help wanted" and "good first issue" labels to their default labels, and states:

Now, GitHub will help potential first-time contributors discover issues labeled with help wanted or good first issue

Also, excerpted from servo/servo#18905:

The keynotes at GitHub Universe indicated that they intend to do a lot of future work using these default labels to surface appropriate issue for new contributors. It is probably a good idea for us to get in the habit of using these standard labels, to take full advantage of the future tools that might become available and the training that prospective contributors get when working with other repositories.

It currently suggests it at the top of issues page for first-time contributors like:

issue

As we are already using "Easy to Fix" label to flag issues appropriate for new contributors, I think we should rename "Easy to Fix" to "good first issue" or add "good first issue" to those with "Easy to Fix" where appropriate.

@ylemkimon ylemkimon changed the title Rename "Easy To Fix" label to "good first issue" Rename "Easy to Fix" label to "good first issue" Oct 17, 2017
@gxyd
Copy link
Contributor

gxyd commented Oct 17, 2017

BTW, can any contributor add 'help wanted' label to his PR?

@asmeurer
Copy link
Member

It would be great if GitHub could support making it so that we don't have to rename the labels. We have a lot of developer documentation and mailing list posts and so on that say "easy to fix". If we change the label name the links will break and it will be confusing to new users.

@ylemkimon
Copy link
Member Author

ylemkimon commented Oct 17, 2017

@gxyd No, still those with write access can apply labels. From documentation:

To create, edit, apply, or delete a label, you must have write access to the repository.

help wanted: Indicates that a maintainer wants help on an issue or pull request

@asmeurer Maybe we can create an issue with both "Easy to Fix" and "good first issue" and redirect to one label, or use both labels simultaneously.

@asmeurer
Copy link
Member

@ylemkimon a redirect issue sounds like a simple solution until they make it configurable.

@ylemkimon
Copy link
Member Author

@asmeurer Should we move all “Easy to Fix” issues to “good first issue” or leave as is?

@asmeurer
Copy link
Member

I would leave it as-is for now. Let's open a meta-issue with "good first issue" that points to "Easy to Fix" for now. Too much of our new user documentation references "Easy to Fix".

@ylemkimon
Copy link
Member Author

I've created #13520. Any suggestions on the title and contents are appreciated.

@oscarbenjamin
Copy link
Contributor

This came up recently on the mailing list.

I think it would be reasonable to change from Easy-to-fix to Good-first-issue except that it's difficult to get everyone to understand a change when many people are involved. The question that needs answering is: how important is this?

@himanshugupta11002
Copy link

@oscarbenjamin , The Good-first-issues highlights opportunities for people who are new to open source and contribute to your projects.

@Mokshith1708
Copy link

I am new to open source and would love to start with this issue if it is open. I think i will be able to do it with a little bit of guidance. Can I take up this issue?

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

No branches or pull requests

6 participants