Good first issues for new developers?

[ehogan]

Hi @ESMValGroup/esmvaltool-developmentteam :)

Iris use a Good First Issue label to identify "good issues to take on if you're just getting started with Iris development". How would everyone feel about doing something like this in ESMValTool / ESMValCore?

In the meantime, does anyone know of any good first issues in either ESMValTool or ESMValCore, please? :)

[zklaus]

I think it's a good idea. Perhaps we can go through the list of issues in one @ESMValGroup/technical-lead-development-team meeting?

[bouweandela]

Are you looking to get started with some easy issues yourself @ehogan? Most people who contribute to the tool have very specific issues they would like to fix, because they need those. It's quite rare for people to pick up something random.

[ehogan]

@bouweandela I wanted to give our new industrial placement something to do that demonstrates working with GitHub and the development workflow process, and I thought it would be great if they could contribute something useful to ESMValTool in the process :)

[bouweandela]

Maybe she/he could start with ESMValGroup/ESMValTool#2337, ESMValGroup/ESMValTool#2002? Any contributions that make the documentation easier to understand/navigate for newcomers would also be very welcome.

[ehogan]

I just stumbled across GitHub Docs: Encouraging helpful contributions to your project with labels, which recommends applying "the good first issue label to issues in your repository to highlight opportunities for people to contribute to your project", so GitHub thinks this is a good idea too! 😉

When I visit https://github.com/ESMValGroup/ESMValTool/issues, I see:

The label itself doesn't appear to be listed at https://github.com/ESMValGroup/ESMValTool/labels, but if we did choose to add it then issues with that label will show up in https://github.com/ESMValGroup/ESMValTool/contribute :)