1 |
On 04/12/2015 05:17 AM, Yanestra wrote: |
2 |
> Hi, |
3 |
> |
4 |
> I am long time user of Gentoo and I tinker with the idea of becoming |
5 |
> Gentoo developer. |
6 |
> |
7 |
> I am a software developer by profession, but I am not quite sure if I |
8 |
> should involve with Gentoo ebuild development. |
9 |
> |
10 |
> To be honest, I have not the slightest imagination what becoming a |
11 |
> Gentoo developer might mean. Things seem to be abhorringly complicated. |
12 |
> |
13 |
> As far as I understand, there are developers, proxy developers, then |
14 |
> there is something like Project Sunrise which I don't understand. |
15 |
> |
16 |
> There are apparently several different portage source repositories, |
17 |
> basing on different software, and furthermore, there is layman. As far |
18 |
> as I remember, portage is stored in cvs, where there is also git, and |
19 |
> somewhere subversion seems to linger. |
20 |
> |
21 |
> And there is lots of documentation that appears to be outdated or |
22 |
> strangely unattached to questions concerning organisation and overall |
23 |
> structure. |
24 |
> |
25 |
> Can someone please tell me where to start becoming a developer? Do there |
26 |
> exist something like quality guidelines for ebuilds? |
27 |
> |
28 |
> Why is there such a chaos? |
29 |
> |
30 |
> Thanks! |
31 |
> |
32 |
|
33 |
As someone who is undergoing their IRC interview soon, I think I can |
34 |
answer some of these questions: |
35 |
|
36 |
* There are developers, proxy-maintainers, and the Sunrise project. |
37 |
Developers have access to the main Gentoo repository of ebuilds and do |
38 |
their best to maintain a quality tree. Proxy-maintainers are regular |
39 |
Gentoo users who "adopt" packages and pledge to help Gentoo developers |
40 |
in maintaining them until either they become a developer themselves or |
41 |
until another developer adopts the package officially. The Sunrise |
42 |
project is a separate tree where developers and users collaborate in |
43 |
getting new or specialized packages into a semi-official repository. |
44 |
Developers assist users in getting ebuilds up to snuff and help them |
45 |
build practical skills in contributing to Gentoo in a more structured |
46 |
manner. |
47 |
|
48 |
* Documentation, like the rest of Gentoo, is powered by volunteers. If |
49 |
you find any missing, erroneous, or outdated information, please file a |
50 |
bug or, if you have permissions on the Wiki, edit it yourself! |
51 |
|
52 |
* The general structure of Gentoo as an organization is somewhat simple. |
53 |
The Council makes all the big and important decisions, while developers |
54 |
have their own "herds" for specific goals (say, the perl, lisp, java, |
55 |
and games herds), which also correspond to projects with the same goals. |
56 |
The Foundation exists to give Gentoo adequate monetary and legal support |
57 |
in carrying out its goals as a distribution. Everything else is pretty |
58 |
much just a bunch of developers working together. |
59 |
|
60 |
* Gentoo's official tree is in CVS for now, but there is a git migration |
61 |
planned. I don't know the timing or exact plans for the immediate |
62 |
future, but my guess is things will be switching to git over the long |
63 |
term once logistic problems are solved. SVN repositories are available |
64 |
over layman only, as far as I'm aware. |
65 |
|
66 |
* Layman itself is a way to activate other repositories. That method is |
67 |
partially deprecated in favor of /etc/repos.conf/ files, which allow for |
68 |
greater, clearer control over repositories. Current releases of layman |
69 |
will interface with the new way of managing, and there are tools in |
70 |
place to make migration (mostly) painless. |
71 |
|
72 |
* The way to begin your journey to become a developer lies mostly in |
73 |
just helping out Gentoo, studying the Devmanual [0], and contacting |
74 |
recruiters to see if there is a mentor available for you. |
75 |
|
76 |
If you're interested in becoming an ebuild developer, you should try out |
77 |
the ebuild quiz [1]. For the most part it just takes a cautious and |
78 |
attentive eye, some adequate knowledge of bash, and familiarity with |
79 |
common building and admin tools. Since you're a developer by trade, I'm |
80 |
sure it wouldn't be a big problem for you to reach developer status. It |
81 |
takes time and effort, but in my personal opinion it's been worth every |
82 |
moment. |
83 |
|
84 |
I hope this helps! |
85 |
|
86 |
~Daniel |
87 |
|
88 |
[0] https://devmanual.gentoo.org |
89 |
[1] https://wwwold.gentoo.org/proj/en/devrel/quiz/ebuild-quiz.txt |