On 4 November 2012 05:15, Markos Chandras <hwoar...@gentoo.org> wrote: > On Wed, Oct 31, 2012 at 12:39 PM, Michael Palimaka > <kensing...@gentoo.org> wrote: >> Hi all, >> >> In bug #304435[1], hwoarang suggested merging the devrel handbook[2] into >> the devmanual[3]. >> >> As the project has grown, so has the amount - and dispersion - of >> development information. I believe consolidation of this information into a >> single point will make everyone's (especially new developers) lives easier. >> >> What do you think? >> >> Best regards, >> Michael >> >> [1]: https://bugs.gentoo.org/show_bug.cgi?id=304435 >> [2]: http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml >> [3]: http://devmanual.gentoo.org/ >> > > fyi > > http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=shortlog;h=refs/heads/devrel-handbook >
That's a good start. I would like to see our devmanual become the one-stop-shop solution for anything regarding development policies that a Gentoo dev (or overlay maintainer) needs to know. That would mean a recruit would find everything he needs in the devmanual — or at least he would find references to other important documents (e.g. GLEPs, PMS, eclass manpages) in case not all relevant information is contained in the devmanual. That way everything an aspiring Gentoo dev needs to know can be found in one place, instead of having to go hunting through many dispersed sources. This also means we should document all QA policies, project/herd/arch specific policies, development-related council decisions, and (possibly unwritten) best practices in our devmanual. I think that would make things much easier for all of us. Obviously I am willing to do my part to make this happen. -- Cheers, Ben | yngwin Gentoo developer Gentoo Qt project lead, Gentoo Wiki admin
