Re: [gentoo-project] GURU[-rise]: looking for volunteers

[Alice Ferrazzi]

On April 6, 2019 12:37:36 AM GMT+09:00, "Michał Górny" <mgorny@g.o> wrote:
>Hi, everyone.
>
>Some of you have read about my GURU idea already.  For those who
>haven't, a short description is included below.  I'd like to start
>a simpler demo for it, and I'm looking for people interested
>in contributing.
>
>
>GURU is meant to be something between Arch Linux's AUR and the past
>Sunrise project -- an officially recognized repository made entirely
>by users, with minimal supervision from Gentoo developers.


Why making a new name? Betagarden or sunrise was not good enough?

>
>GURU would use two branches: a development branch where all interested
>contributors will be allowed to commit freely, and a reviewed branch
>where established members will push reviewed commits from
>the development branch.  This is very similar to Sunrise, except that
>reviewing will not be limited to Gentoo developers.
>
>GURU would be only for new packages, or packages that are clearly
>abandoned in ::gentoo.  While the packages wouldn't land in ::gentoo,
>having a single officially recognized place for them will help both
>users and developers to find them, and to maintain a single version,
>hopefully better than packages scattered all over private repositories.

I'm worried that guru will delay inclusion of new packages in the Gentoo repository also in the case where just a pull request review would be enough for keeping a good quality overall.

>
>GURU would use three user classes:
>
>1. Contributors -- allowed to commit to development branch, directly
>responsible for their own actions but advised to take care of whole dev
>branch.
>
>2. Trusted contributors -- allowed to merge to master branch and to
>accept new contributors.  Responsible for quality of the master branch,
>and for monitoring new contributors.
>
>3. Gentoo Developers -- allowed to appoint trusted contributors and
>with
>superpowers.  Responsible for taking emergency actions.
>
>The basic idea is whenever a new user requests joining, one of
>the trusted contributors (or developers) accepts him and starts
>monitoring his activity (mostly to quickly detect malicious users).
>When the user makes some recognizable good work, he becomes trusted
>contributor (as approved by a Gentoo developer) and starts reviewing
>stuff from dev branch and merging it to master branch.
>
>This is somewhat similar to Sunrise, except that instead of developers
>reviewing stuff (which IMHO caused Sunrise's downfall), we let users do
>that.  Also, a major difference is that we allow inferior quality
>ebuilds, and assume other contributors are free (and encouraged!)
>to improve them.
>
>
>I'm looking for all people interested in participating in all three
>classes.  That is:
>
>a. users interested in submitting their ebuilds to this repository,
>
>b. users interested in becoming trusted contributors and reviewing
>stuff,
>
>c. developers interested in taking part of overseeing this.
>
>I'm willing to accept some of the recognized proxy-maint contributors
>straight to category b.  Though I should note that according to my
>idea,
>this is the category expected to have most work here.
>
>Gentoo Developers may expect some work especially at the beginning,
>in order to bootstrap this.  However, once we have strong trusted
>contributor group the amount of work should decrease.
>
>Please note that the technical details haven't been decided yet.
>The GURU repository will probably be hosted on Gentoo Infra (due to
>need
>for git hooks).  I'm going to try pushing a bit more for our own GitLab
>instance but if that fails, gitolite would probably have to be good
>enough.  In that case, I will be taking care of adding people on behalf
>of others.

Gitlab instance? We have a Gentoo official Gitlab instance?

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.