Gentoo Archives: gentoo-commits

From: "Michał Górny" <mgorny@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] sites/www:master commit in: get-involved/become-developer/
Date: Sun, 26 Feb 2017 22:50:13
Message-Id: 1488149387.085fd217c4c1db7c012b6057a89ea3f6fb619476.mgorny@gentoo
1 commit: 085fd217c4c1db7c012b6057a89ea3f6fb619476
2 Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
3 AuthorDate: Sun Feb 26 22:48:06 2017 +0000
4 Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
5 CommitDate: Sun Feb 26 22:49:47 2017 +0000
6 URL: https://gitweb.gentoo.org/sites/www.git/commit/?id=085fd217
7
8 becoming-developer: Rework/update the guide
9
10 Update the text for the current recruiting standards. Clearly highlight
11 the differences between developers with and without commit access.
12 Include all basic details so that Recruiters don't have to keep a second
13 guide.
14
15 Approved by Recruiters project.
16
17 get-involved/become-developer/index.md | 80 ++++++++++++++++++++++++++--------
18 1 file changed, 62 insertions(+), 18 deletions(-)
19
20 diff --git a/get-involved/become-developer/index.md b/get-involved/become-developer/index.md
21 index a752c9d..7bc243f 100644
22 --- a/get-involved/become-developer/index.md
23 +++ b/get-involved/become-developer/index.md
24 @@ -13,32 +13,76 @@ nav2-weight: 50
25 Please do not hesitate to contact them!
26 </div>
27
28 -## How do I get started?
29 +## Becoming a developer
30
31 -First of all, you need an **area of Gentoo you want to contribute to**, be it support, package maintenance, artwork, or documentation.
32 -You can find some pointers to what you could do [on our website](/get-involved/contribute/).
33 -Projects also publish specific [Staffing Needs](https://wiki.gentoo.org/wiki/Project:Gentoo/Staffing_Needs) for specific tasks that need to be done.
34 -You are very much free to use these as your kickstart into Gentoo and venture to other areas of the project later on.
35 +There are two interwoven paths for becoming a Gentoo developer. If you would
36 +like to focus your work on ebuilds, then you are probably interested in <span
37 +class="bg-danger">becoming a developer with commit access to ::gentoo</span>. If
38 +you are interested primarily in other areas of contribution, you may prefer to
39 +<span class="bg-info">become a developer without commit access</span>.
40
41 -### Getting a Mentor
42 +### Step 1. Contribute
43
44 -If you enjoy working on the distribution and would like to continue, the **next step is to find a mentor.**
45 -It's very likely a current developer who is working on the same things as you are can be that for you.
46 -Should there be noone available to be your mentor, do ask the [Gentoo Recruiters](mailto:recruiters@g.o).
47 +If you would like to help Gentoo, first find yourself something to do. You may
48 +want to look at our [contribution guide](/get-involved/contribute/), and
49 +subsequently look through the [Gentoo
50 +projects](https://wiki.gentoo.org/wiki/Project:Gentoo). <span
51 +class="bg-danger">For ebuild work, you can try helping out one of the projects
52 +that focus on maintaining packages, such as the
53 +[GNOME](https://wiki.gentoo.org/wiki/Project:GNOME) or
54 +[KDE](https://wiki.gentoo.org/wiki/Project:KDE) projects. Alternatively, you can
55 +maintain your own packages or co-maintain other Gentoo packages via the [Proxy
56 +Maintainers](https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers)
57 +project.</span> <span class="bg-info">For non-ebuild work, you may want to look
58 +at other projects, such as [Bug
59 +Wranglers](https://wiki.gentoo.org/wiki/Project:Bug-wranglers) or [Gentoo
60 +Forums](https://wiki.gentoo.org/wiki/Project:Forums).</span>
61
62 -### Quiz and Review
63 +### Step 2. Participate
64
65 -When you have found your mentor, you will now work together with them on
66 -**completing [one or two quizzes](https://wiki.gentoo.org/wiki/Project:Recruiters/Quiz)**—depending on your area of contribution.
67 -These are in place to ensure you are up to speed with the basic structure, policies, and procedures of the project
68 -and you feel comfortable working with us.
69 +If you enjoy working on Gentoo and would like to stay longer, you should
70 +consider starting to participate in the community. You should consider joining
71 +some of [our IRC channels](/get-involved/irc-channels/), subscribing to some of
72 +[the mailing lists](/get-involved/mailing-lists/) and/or using [Gentoo
73 +Forums](https://forums.gentoo.org/). This way you get to know more of the Gentoo
74 +developers and users, and they get to know you!
75
76 -Your mentor will **file a ticket** for you on our [bug tracker](https://bugs.gentoo.org) that **officially starts the recruitment process.**
77 -After that, your completed quizzes should be sent to the recruiters and when someone is available, they will sit down (well, figuratively, as it's on IRC) with you to review your quizzes and answer any questions you might have.
78 +### Step 3. Find a mentor
79
80 -### Jumping the Gap
81 +The next step towards becoming a Gentoo developer is to find a mentor. A mentor
82 +is an existing Gentoo developer who will vouch for you and help you in. Most of
83 +the developers find their mentor among the developers they initially work with.
84 +If you have any trouble finding a mentor, contact the [Mentors
85 +project](https://wiki.gentoo.org/wiki/Project:Mentors).
86 +
87 +### Step 4. Take quizzes
88 +
89 +Before you become an officially recognized Gentoo developer, you are expected to
90 +learn a few basics on how Gentoo is structured and how it operates. <span
91 +class="bg-danger">To get commit access, you will also need to know a fair bit
92 +about ebuilds</span>. To help you get yourself knowledgeable, we have prepared
93 +<span class="bg-info">one</span> or <span class="bg-danger">two</span> quizzes
94 +for you to take.
95 +
96 +<span class="bg-danger">The prospective developers aiming to obtain commit
97 +access should take the [ebuild
98 +quiz](https://projects.gentoo.org/comrel/recruiters/quizzes/ebuild-quiz.txt),
99 +followed by the [end
100 +quiz](https://projects.gentoo.org/comrel/recruiters/quizzes/end-quiz.txt).</span>
101 +<span class="bg-info">For candidates for developers without commit access, we
102 +have prepared a less technical [developer
103 +quiz](https://projects.gentoo.org/comrel/recruiters/quizzes/developer-quiz.txt)
104 +instead.</span>
105 +
106 +### Step 5. Get recruited!
107 +
108 +Once you and your mentor agree that you're ready, you arrange a review session
109 +with the [Recruiters](https://wiki.gentoo.org/wiki/Project:Recruiters) at a
110 +convenient time. During this session(s), Recruiters interview you and ensure
111 +that you have obtained all the necessary knowledge. Once you pass the review,
112 +the Recruiters create your developer account and announce you as a new
113 +developer.
114
115 -When recruiters are confident you're ready, they will complete the process by setting you up with access to the various developer services of Gentoo.
116
117 ## What do I get?