On Sat, Oct 10, 2015 at 10:09:11AM +0200, Michał Górny wrote:
> I have the pleasure to announce that we have formed a new Reviewers
> team [1] for Gentoo. The team is going to assemble developers willing
> to perform ebuild reviews and help contributors improve their ebuild
> skills.
>
> The main goal of the team is to handle GitHub pull requests. We are
> going to review incoming PRs, communicate with maintainers and merge
> them as appropriate. In particular, we're going to help willing
> contributors get high-quality, PGP-signed commits into Gentoo,
> therefore helping them prepare to become Gentoo developers.
>
> The side goal is to review current Gentoo commits for major QA
> violations and other issues, aiming at improving the quality of ebuilds
> in Gentoo and helping other developers using bash, ebuilds and git
> effectively.
>
> [1]:https://wiki.gentoo.org/wiki/Project:Reviewers
This is good news. There are quite a few developers that manage a small
subset of packages while doing tremendous work for Gentoo within that
community. For instance, they focus on particular deliverables in
repositories which eventually get packaged, or on integration of certain
components which have a strong, broader community coverage.
These developers will certainly welcome any helping hand (even post-commit)
in keeping packages of high quality.
I hope you will also focus on the documentation side. Certain processes that
we follow within Gentoo (for commits, for instance the Git workflow) would
benefit from a good document *set* (yes, set, as you'll definitely want such
processes to have both a single-screen version as well as an elaborate
version).
I've also found myself often looking for similar ebuilds in which a certain
problem would already have been implemented. For instance, ebuilds with an
optional python part using the python-r1 eclass. Do you think it is
worthwhile to have a number of packages assigned as good examples?
Wkr,
Sven Vermeulen
