From: Bart Ribbers <bribbers@disroot.org>
To: ~alpine/devel@lists.alpinelinux.org
Subject: Re: Alpine community governance
Date: Sun, 27 Oct 2019 16:42:36 +0100
Message-ID: <4356713.RsDxjGZlov@frostblade>
In-Reply-To: <5152c7bd5e788aadfb987281a47107a4f3959860.camel@cogitri.dev>
References: <BXZLAL5IFNQW.15ACK4H0U6JGN@homura> <5152c7bd5e788aadfb987281a47107a4f3959860.camel@cogitri.dev>
Mime-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

On Sunday, 27 October 2019 14:42:20 CET Rasmus Thomsen wrote:
> > Moving a discussion from IRC to the ML:
> > 
> > One easy way to improve the core team's bandwidth would be a simple
> > git
> > hook which allowed anyone to push changes to packages for which
> > they're
> > listed as the maintainer.
> 
> Hm, although that does sound like it'd significantly lessen the
> workload on core member I dislike this approach, at least with how we
> currently handle maintainership of packages. About everyone can become
> a maintainer (which is a good thing IMHO since this allows people
> knowing the package well but not Alpine's packaging process to be a
> maintainer) as of now and I feel like it'd be best to have someone look
> over the changes of maintainers which aren't that experienced with
> Alpine's packaging process yet. Maybe just having somewhat strict CI
> rules and only allowing a merge if CI passes would do the trick to
> ensure QA is done though.

Then you have the problem that some packages take more time to compile than 
the CI allows. For example CI time had to be increased for my fork in Gitlab 
as I push KDE and Plasma changes, which almost all the time take more than 1 
hour to complete. I don't think it's feasible to manually increase the set 
time for every person's fork that needs it.
 
> > This reduces the core team's workload to
> > dealing with new packages, new maintainers, etc; but removes the
> > burden
> > of dealing with every change to aports.