becoming-developer: Rework/update the guide

Update the text for the current recruiting standards. Clearly highlight
the differences between developers with and without commit access.
Include all basic details so that Recruiters don't have to keep a second
guide.

Approved by Recruiters project.

1 files changed, 62 insertions, 18 deletions

diff --git a/get-involved/become-developer/index.md b/get-involved/become-developer/index.md
index a752c9d..7bc243f 100644
--- a/get-involved/become-developer/index.md
+++ b/get-involved/become-developer/index.md
@@ -13,32 +13,76 @@ nav2-weight: 50
   Please do not hesitate to contact them!
 </div>
 
-## How do I get started?
+## Becoming a developer
 
-First of all, you need an **area of Gentoo you want to contribute to**, be it support, package maintenance, artwork, or documentation.
-You can find some pointers to what you could do [on our website](/get-involved/contribute/).
-Projects also publish specific [Staffing Needs](https://wiki.gentoo.org/wiki/Project:Gentoo/Staffing_Needs) for specific tasks that need to be done.
-You are very much free to use these as your kickstart into Gentoo and venture to other areas of the project later on.
+There are two interwoven paths for becoming a Gentoo developer. If you would
+like to focus your work on ebuilds, then you are probably interested in <span
+class="bg-danger">becoming a developer with commit access to ::gentoo</span>. If
+you are interested primarily in other areas of contribution, you may prefer to
+<span class="bg-info">become a developer without commit access</span>.
 
-### Getting a Mentor
+### Step 1. Contribute
 
-If you enjoy working on the distribution and would like to continue, the **next step is to find a mentor.**
-It's very likely a current developer who is working on the same things as you are can be that for you.
-Should there be noone available to be your mentor, do ask the [Gentoo Recruiters](mailto:recruiters@gentoo.org).
+If you would like to help Gentoo, first find yourself something to do. You may
+want to look at our [contribution guide](/get-involved/contribute/), and
+subsequently look through the [Gentoo
+projects](https://wiki.gentoo.org/wiki/Project:Gentoo). <span
+class="bg-danger">For ebuild work, you can try helping out one of the projects
+that focus on maintaining packages, such as the
+[GNOME](https://wiki.gentoo.org/wiki/Project:GNOME) or
+[KDE](https://wiki.gentoo.org/wiki/Project:KDE) projects. Alternatively, you can
+maintain your own packages or co-maintain other Gentoo packages via the [Proxy
+Maintainers](https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers)
+project.</span> <span class="bg-info">For non-ebuild work, you may want to look
+at other projects, such as [Bug
+Wranglers](https://wiki.gentoo.org/wiki/Project:Bug-wranglers) or [Gentoo
+Forums](https://wiki.gentoo.org/wiki/Project:Forums).</span>
 
-### Quiz and Review
+### Step 2. Participate
 
-When you have found your mentor, you will now work together with them on
-**completing [one or two quizzes](https://wiki.gentoo.org/wiki/Project:Recruiters/Quiz)**—depending on your area of contribution.
-These are in place to ensure you are up to speed with the basic structure, policies, and procedures of the project
-and you feel comfortable working with us.
+If you enjoy working on Gentoo and would like to stay longer, you should
+consider starting to participate in the community. You should consider joining
+some of [our IRC channels](/get-involved/irc-channels/), subscribing to some of
+[the mailing lists](/get-involved/mailing-lists/) and/or using [Gentoo
+Forums](https://forums.gentoo.org/). This way you get to know more of the Gentoo
+developers and users, and they get to know you!
 
-Your mentor will **file a ticket** for you on our [bug tracker](https://bugs.gentoo.org) that **officially starts the recruitment process.**
-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.
+### Step 3. Find a mentor
 
-### Jumping the Gap
+The next step towards becoming a Gentoo developer is to find a mentor. A mentor
+is an existing Gentoo developer who will vouch for you and help you in. Most of
+the developers find their mentor among the developers they initially work with.
+If you have any trouble finding a mentor, contact the [Mentors
+project](https://wiki.gentoo.org/wiki/Project:Mentors).
+
+### Step 4. Take quizzes
+
+Before you become an officially recognized Gentoo developer, you are expected to
+learn a few basics on how Gentoo is structured and how it operates. <span
+class="bg-danger">To get commit access, you will also need to know a fair bit
+about ebuilds</span>. To help you get yourself knowledgeable, we have prepared
+<span class="bg-info">one</span> or <span class="bg-danger">two</span> quizzes
+for you to take.
+
+<span class="bg-danger">The prospective developers aiming to obtain commit
+access should take the [ebuild
+quiz](https://projects.gentoo.org/comrel/recruiters/quizzes/ebuild-quiz.txt),
+followed by the [end
+quiz](https://projects.gentoo.org/comrel/recruiters/quizzes/end-quiz.txt).</span>
+<span class="bg-info">For candidates for developers without commit access, we
+have prepared a less technical [developer
+quiz](https://projects.gentoo.org/comrel/recruiters/quizzes/developer-quiz.txt)
+instead.</span>
+
+### Step 5. Get recruited!
+
+Once you and your mentor agree that you're ready, you arrange a review session
+with the [Recruiters](https://wiki.gentoo.org/wiki/Project:Recruiters) at a
+convenient time. During this session(s), Recruiters interview you and ensure
+that you have obtained all the necessary knowledge. Once you pass the review,
+the Recruiters create your developer account and announce you as a new
+developer.
 
-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.
 
 ## What do I get?