It would be useful to have an ability for potential contributors to
search for entry-level bugs. That way, people who are interested to
contribute, but are not yet familiar with code base, may easily find how
to help.

I suggest allowing tagging bug reports as "easy" and/or "no code
needed". Then, a dedicated tab in woof overview page could show only the
easy bugs.

WDYT?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Ihor Radchenko <yantar92@posteo.net> writes:

> It would be useful to have an ability for potential contributors to
> search for entry-level bugs. That way, people who are interested to
> contribute, but are not yet familiar with code base, may easily find how
> to help.
>
> I suggest allowing tagging bug reports as "easy" and/or "no code
> needed". Then, a dedicated tab in woof overview page could show only the
> easy bugs.
>
> WDYT?

I've discussed with many FLOSS maintainers using the goodfirstissue
convention for naming issues in GitHub.  In general, this is not very
effective: these issues are generally seen as boring or trivial, and
get quickly fixed by experienced contributors, not beginners.

I would rather recommend writing a contributor guide for beginners so
that they learn how to tackle issues (easy or difficult ones) faster.

-- 
 Bastien Guerry