Investigate ways to embrace the culture of creating good-first issues

Created by: valerybugakov

Context

During the Hacktoberfest 2021, one of the most time-consuming tasks was creating a good-first issues list for external contributors to pick up because we didn't have anything in the pipeline before the preparation.

What can we do to drive this as a culture in engineering to consider defining and tagging good first issues constantly?

Succes criteria

The steps that can help to address the question above are documented and the process (if applicable) automated.

Notes

Two components might help here: champions and communication.

1. Champions are engineers or engineering managers that would create/encourage to create good first issues.
2. The communication that emphasizes that investing time into good first issues is not only about the core product contributions but also about a smooth onboarding experience for new Sourcegraph employees: a pull of issues to pick up during a couple of first weeks, better documentation, friendly local development environment.

Another important aspect is ensuring that good-first-issues are actually picked up and worked on. If devs know there's a possibility that their issue might be completed, they'll be a lot more inclined to add the label.