Gentoo Archives: gentoo-dev

From: Tom Wijsman <TomWij@g.o>
To: gentoo-dev@l.g.o
Cc: hasufell@g.o
Subject: Re: [gentoo-dev] The state and future of the OpenRC project
Date: Mon, 09 Jun 2014 22:13:30
Message-Id: 20140610001209.4a9fa8f0@gentoo.org
In Reply to: Re: [gentoo-dev] The state and future of the OpenRC project by hasufell
1 On Mon, 09 Jun 2014 21:45:26 +0000
2 hasufell <hasufell@g.o> wrote:
3
4 > Probably because no one mentored them on how to fix these QA issues.
5 > Otherwise... if that's attitude, then that's just sad and has to be
6 > fixed by those who run that overlay (review, contribution guidelines).
7 >
8 > And I still think that the top 1 reason people run an overlay is
9 > because it's easier than contributing directly.
10 > A lot of overlay maintainers I tried to convince on getting more
11 > involved even said that.
12 >
13 > Even sunrise workflow has proven too slow and cumbersome... look at
14 > the commit history, it's constantly decreasing.
15 >
16 > Sure, reasons may vary, but there is not much positive to say about
17 > current gentoo workflow.
18
19 We are setting up https://github.com/gentoo/proxy-maintainers to deal
20 with some of these problems; if sunrise continues to decrease activity,
21 I suspect this repository has a chance to become its successor.
22
23 Travis integration is used to cover QA issues, see
24 https://travis-ci.org/gentoo/proxy-maintainers which runs repoman on
25 the overlay for each commit; therefore, QA issues don't go unnoticed.
26
27 To improve the workflow further; we use app-portage/overlint to catch
28 differences between that repository and the Portage tree, after which
29 there is room for even much more automation; thus more time reviewing.
30
31 --
32 With kind regards,
33
34 Tom Wijsman (TomWij)
35 Gentoo Developer
36
37 E-mail address : TomWij@g.o
38 GPG Public Key : 6D34E57D
39 GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D

Attachments

File name MIME type
signature.asc application/pgp-signature