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

Optimize issue workflow for new contributors #33

Closed
3 tasks done
sypets opened this issue Nov 26, 2018 · 1 comment
Closed
3 tasks done

Optimize issue workflow for new contributors #33

sypets opened this issue Nov 26, 2018 · 1 comment
Assignees

Comments

@sypets
Copy link
Contributor

sypets commented Nov 26, 2018

  • Add new label "good first issue", use TYPO3 color: #f49800 (use same in all TYPO3 documentation repos)
  • Add some new issues that are actually "good first issues" and mark them
  • link to this from "How you can help"

see https://help.github.com/articles/helping-new-contributors-find-your-project-with-labels/

@sypets sypets self-assigned this Nov 26, 2018
@sypets
Copy link
Contributor Author

sypets commented Nov 26, 2018

Problem is, Github is a little fuzzy about labels "good first issue" and "help wanted" (and you can use this any way you want, but I think we can stick to best practices that people can inuitively understand and use correctly.)

See also messages you get on Issues tab in some projects:

symfony-docs-issues2

So it looks like you can use either "help wanted" or "good first issue", but I think "good first issue" is much clearer and I have used "help wanted" for things where help was wanted and which weren't necessarily good first issue.

Am proposing this: Use "good first issues" for good first issues for new contributors. Use "help wanted" only sparingly, because unclear and ambivalent.

@sypets sypets closed this as completed Nov 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant