Gentoo Archives: gentoo-dev

From: Markos Chandras <hwoarang@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Merging the devrel handbook into the devmanual
Date: Wed, 07 Nov 2012 10:30:27
Message-Id: CAG2jQ8ikR26JyrftdUTb80PMR5f-x5qzOCT7rySTHMVL_kU=Aw@mail.gmail.com
In Reply to: Re: [gentoo-dev] Merging the devrel handbook into the devmanual by Ben de Groot
1 On Sun, Nov 4, 2012 at 4:47 AM, Ben de Groot <yngwin@g.o> wrote:
2 > On 4 November 2012 05:15, Markos Chandras <hwoarang@g.o> wrote:
3 >> On Wed, Oct 31, 2012 at 12:39 PM, Michael Palimaka
4 >> <kensington@g.o> wrote:
5 >>> Hi all,
6 >>>
7 >>> In bug #304435[1], hwoarang suggested merging the devrel handbook[2] into
8 >>> the devmanual[3].
9 >>>
10 >>> As the project has grown, so has the amount - and dispersion - of
11 >>> development information. I believe consolidation of this information into a
12 >>> single point will make everyone's (especially new developers) lives easier.
13 >>>
14 >>> What do you think?
15 >>>
16 >>> Best regards,
17 >>> Michael
18 >>>
19 >>> [1]: https://bugs.gentoo.org/show_bug.cgi?id=304435
20 >>> [2]: http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml
21 >>> [3]: http://devmanual.gentoo.org/
22 >>>
23 >>
24 >> fyi
25 >>
26 >> http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=shortlog;h=refs/heads/devrel-handbook
27 >>
28 >
29 > That's a good start. I would like to see our devmanual become the
30 > one-stop-shop solution for anything regarding development policies
31 > that a Gentoo dev (or overlay maintainer) needs to know. That would
32 > mean a recruit would find everything he needs in the devmanual — or at
33 > least he would find references to other important documents (e.g.
34 > GLEPs, PMS, eclass manpages) in case not all relevant information is
35 > contained in the devmanual. That way everything an aspiring Gentoo dev
36 > needs to know can be found in one place, instead of having to go
37 > hunting through many dispersed sources.
38 >
39 > This also means we should document all QA policies, project/herd/arch
40 > specific policies, development-related council decisions, and
41 > (possibly unwritten) best practices in our devmanual. I think that
42 > would make things much easier for all of us.
43 >
44 > Obviously I am willing to do my part to make this happen.
45 > --
46 > Cheers,
47 >
48 > Ben | yngwin
49 > Gentoo developer
50 > Gentoo Qt project lead, Gentoo Wiki admin
51 >
52
53 The ETA for the merge is this weekend. If you have a guide/document
54 that links to the devrel ebuild HOWTO[1] please fix your links as the
55 devrel handbook (the ebuild stuff for now) is completely going away
56 and not marked as deprecated.
57
58 [1] http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1
59
60 --
61 Regards,
62 Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2