From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1EubDy-0004Uh-5Z for garchives@archives.gentoo.org; Thu, 05 Jan 2006 19:56:38 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k05JtOUv004335; Thu, 5 Jan 2006 19:55:24 GMT Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.202]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k05JqjIf025326 for ; Thu, 5 Jan 2006 19:52:46 GMT Received: by zproxy.gmail.com with SMTP id i28so3535485nzi for ; Thu, 05 Jan 2006 11:52:45 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=IgMv1D2a4ysC/cETcuHr6CRFeekvrrxkyklND6ILh8zCq1SfvwyOQrtIOFVzsufzQFtRSkjB+On7L2f9Oo7TJ2Kj0efoJZTVnw7rLFACITIis5tCgwi2sh4UcJTFuWLNTStig/D6yDBx2DNwitAUp2MQqoWoR3ryTOCS8xlKa7A= Received: by 10.65.95.5 with SMTP id x5mr1553213qbl; Thu, 05 Jan 2006 11:52:45 -0800 (PST) Received: from ?176.16.10.30? ( [68.144.157.61]) by mx.gmail.com with ESMTP id q19sm5928218qbq.2006.01.05.11.52.44; Thu, 05 Jan 2006 11:52:45 -0800 (PST) Subject: Re: [gentoo-dev] RFC: regular project updates From: Lares Moreau To: gentoo-dev@lists.gentoo.org In-Reply-To: <1136476815.20002.45.camel@localhost> References: <1136476815.20002.45.camel@localhost> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-g6GqTALYl//xUeay1U2r" Date: Thu, 05 Jan 2006 12:52:42 -0700 Message-Id: <1136490762.8691.52.camel@localhost> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 X-Archives-Salt: 5b666f85-9583-495c-8e10-b10bf674202c X-Archives-Hash: bca8f932504228bd52c0f5f3688287b1 --=-g6GqTALYl//xUeay1U2r Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2006-01-05 at 17:00 +0100, Patrick Lauer wrote: > Hi all, >=20 > as the debate about the future direction of Gentoo continues it's > getting more and more obvious to me that there's a lack of information > skewing the debate. It seems that while most devs (and users) have a > good idea what's happening in "their" projects it's quite difficult to > see what is happening in other projects. >=20 > So - as GWN monkey - I'm offering my services as aggregator for project > updates. Maybe someone from the doc project wants to help to get this > information put on the website so that it's visible? >=20 > I suggest project updates every 6 months (which roughly is the same > timeframe as releases) > Maybe this helps people get a "global vision" of where Gentoo is and > where it's going. >=20 > Any feedback appreciated :-) Perhaps we could kill more then one bird with on stone. Once every X months, have all herds commit an ebuildish file containing the following to CVS, which would then be parsed and posted on g.o. --- begin --- Herd name: What we do: General vision of our herd Working on: what we are specificaly working on Lead(s): current lead(s) Dev list: list of active devs AT/HT list: list of active AT/HTs Herd Deps: Other Herds we _need_ in order to work properly simple example - x86 Herd (as it is currently called) depends on linux, complex - webapps depend on PHP, Perl, python, Ruby etc; apache; ?mysql Herd associates: People we work in parallel with. ie - all work in parallel - KDE and Gnome work in parallel=20 Herd homepage: either a homepage or a wiki --- end --- all herds depend implicitly on the gentoo infrastructure. Now, If this file isn't commited to CVS on the interval, the herd becomes stale, and is marked as such. If the the herd is stale for interval*2, the herd would be considered dead. Issues this may address - inactive devs/testers - clearly defined scopes for all herds - some communication grevences (easily find a herds direction and projects) - easy to 'find' related herds After parsing, this info could be posted to g.o and easily browsed. An org-chart could be generated for easy reference by all. Have all groups in gentoo be considered a herd. Including council, gentoo-infra, portage, ReleaseEng and others I can't think of. With the dependency structure developed 'from the bottom up', the issue of where we are going is mitigated. Also this allows for any group to have their own objective and not conflict with each other. Anyone can release a livecd under the gentoo name, just add the herdname in the title. ie. gentoo-2006_hardened.0, or gentoo-2006_bin.0 or gentoo-2006_server.0. There would still be an 'official' gentoo release, but I would wrather see a 'default recommended' release. Because in all reality, there is a different release for each arch. This is by no means complete, just some thoughts that might work. cat flames > /dev/null; I'd wrather hear nothing. --=20 Lares Moreau | LRU: 400755 http://counter.li.org lares/irc.freenode.net | Gentoo x86 Arch Tester | ::0 Alberta, Canada Public Key: 0D46BB6E @ subkeys.pgp.net | Encrypted Mail Preferred Key fingerprint =3D 0CA3 E40D F897 7709 3628 C5D4 7D94 483E 0D46 BB6E --=-g6GqTALYl//xUeay1U2r Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBDvXkJfZRIPg1Gu24RAtnGAJ9OOKSSJcZVAPA+kIhOl02xmIslQQCeMEYQ /6GcPWQ2f2JGgAol47DHs+Q= =twLL -----END PGP SIGNATURE----- --=-g6GqTALYl//xUeay1U2r-- -- gentoo-dev@gentoo.org mailing list