[laurent123456]

If an issue takes a lot of time to write, then it's probably not a good first issue. For my project, I found there are all kind of small things that are easy to do but I don't have time, so instead I write a good first issue.

Usually I also put some pointers on how to get started, like "check such method in such file", or "have a look at that reducer action".

It doesn't take long to do this and it's been working pretty well. It's a very good way for new developers to get something done easily and to get familiar with the code base.

As of now there are 40 such issues, including 28 completed: https://github.com/laurent22/joplin/issues?q=label%3A%22good...

[daffl]

This is interesting because it definitely seems to be different for different types of projects like frontend and end-user applications vs. backend and other libraries.