Identify 3-5 "starter" tasks or bugs in any Moja Gbloal projects

[Patamap]

Come up with 3-5 bugs or simpler tasks to work on any Moja Gobal project especially main core projects like FLINT, Modules, About Moja Global; clearly label them as "good first issues" and leave them open for new contributors to try working on

How to do it
Across core projects, come up with shortlist of small / quick improvements or fixes wanted, but not urgently needed
File new issues/update existing ones to explain easier tasks
Explain the problem, clearly explain the deliverable / desired result
Label these tasks clearly with a "new comer" label
Keep them open for new contributors or team members to work on (core / active contributors shouldn't take these tasks)

Why do it
When people come wanting to contribute, we need to help guide their first steps. Simple or "easyfix" tasks are great ways to introduce a new contributor to your project by giving them a small, manageable area to focus on or work. This supports a marginal improvement to your project but also delivers purpose to someone navigating your code for the first time. These tasks get them more comfortable with the project and could edge someone towards contributing bigger things. But it's easier to start with a smaller piece first.

@leitchy @malfrancis @kaskou @mfellows @gmajan @RobboW

[Patamap]

@sulays @abhineet97 @abhi211199 @parth-gr @smorken @HarrisLawYF @juliancabezas @yjko2

as discussed in the moja global TSC meeting in July. Refer to #78

[abhineet97]

Hello @Patamap.

Thanks tagging me. I wanted to ask what label should we use for tagging these starter issues?

It seems that good first issue (without hyphens) is the most popular label (as shown by the huge amount of issues that are listed here). Also, this label integrates very well with GitHub (as described here).

So, I would like to suggest that we use this label org-wide for tagging starter/first timer issues.

[gmajan]

Excellent point. I think it is great to find first-timer issues in other repos and get contributors to work on those. The key here is that you share your newly acquired knowledge about FLINT and its paraphernalia to the next generation of contributors.