...

You can validate this by looking for it in the list here!Some other labels you should add to these issues include:

...

Know that the individuals coming to look at the issues available will be new to the project , and will vary in their levels of experience. An issue is not a

A "good first issue" if it is not well documented, scoped, and clear on test methodologywill have the following key characteristics...

• The problem(s) and use case(s) are articulated.
• The scope and expectation of the outcome is clear.
• The methodology for determining if the issue is addressed is outlined.
• One or more people identified that could provide mentorship to the contributor.

Check out this article for advice on ensuring your project has good first issues that new contributors can easily start on.

Create a Project Specific Landing Page

This page, which can live directly on the project's repository, wiki page, or even website, should elaborate on any project-specific details not covered on the overall participant page. For example: specific build instructions, communication preferences, or details about project components that might not be obvious to newcomers. Check out XXX for an example of possibilities. 

Things that the page should have include:

• Specific build instructions ( you might already be able to reference this in documentation, but you could also detail any first-timers' gotchas ).
• Communication preferences for the project ( is it best to ping on Slack? Mailing Lists? What times are other project members generally available? )
• Anything non-obvious about the project or not well documented that would confuse a first-timer.

Register as a participating project

...