Gentoo Archives: gentoo-dev

From: hasufell <hasufell@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] The state and future of the OpenRC project
Date: Sun, 08 Jun 2014 14:41:21
Message-Id: 53947600.50506@gentoo.org
In Reply to: Re: [gentoo-dev] The state and future of the OpenRC project by Jeroen Roovers
1 Jeroen Roovers:
2 > On Sun, 08 Jun 2014 03:05:28 +0200
3 > Alexander Berntsen <bernalex@g.o> wrote:
4 >
5 >> On 07/06/14 23:08, Jeroen Roovers wrote:
6 >>> You can start fixing bugs immediately. You can check out the
7 >>> sources, write patches and attach the patches to the bug reports.
8 >>> Then all it takes is someone else to review/commit the patches.
9 >
10 >> Hacking an init system is different to hacking e.g. desktop or Web
11 >> programs.
12 >
13 > Exactly nobody suggested that.
14 >
15 > That said, starting with OpenRC probably doesn't give you the easiest
16 > learning curve for getting "into" Gentoo.
17 >
18 >> Unless Daniel happens to be a seasoned veteran init system
19 >> hacker, having a mentor will be a significant boost.
20 >
21 > Lots of people post patches all the time. Whether they're good patches
22 > is up for review, and the lack of mentoring doesn't stop thousands of
23 > others from proposing patches on bugzilla on a very regular basis.
24 >
25 >
26
27 The amount of contributors (with real patches and real ebuilds) is
28 constantly decreasing, because our workflow is horrible. I hope you
29 don't actually think that bugzilla is an appropriate review platform.
30
31 The situation with lack of mentors is more than a small problem. It's a
32 problem for a lot of gentoo internal projects as well where people start
33 at positions they don't understand, because there is no one who did
34 mentor them in that specific area.

Replies