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.43) id 1E78G2-0000NT-50 for garchives@archives.gentoo.org; Mon, 22 Aug 2005 09:06:18 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7M94nfl031016; Mon, 22 Aug 2005 09:04:49 GMT Received: from palladium.cryos.net (palladium.cryos.net [80.68.90.219]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j7M94mQh026752 for ; Mon, 22 Aug 2005 09:04:48 GMT Received: from localhost (localhost [127.0.0.1]) by palladium.cryos.net (Postfix) with ESMTP id 11AC55CA1C for ; Mon, 22 Aug 2005 10:53:19 +0100 (BST) Received: from palladium.cryos.net ([127.0.0.1]) by localhost (palladium [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 06800-04-4 for ; Mon, 22 Aug 2005 10:53:16 +0100 (BST) Received: from ns0.cryos.net (ns0.cryos.net [217.155.144.221]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by palladium.cryos.net (Postfix) with ESMTP id C1B505C4DF for ; Mon, 22 Aug 2005 10:53:16 +0100 (BST) From: "Marcus D. Hanwell" Organization: Gentoo To: gentoo-science@lists.gentoo.org Subject: Re: [gentoo-science] Re: Scientific herd leadership Date: Mon, 22 Aug 2005 10:05:18 +0100 User-Agent: KMail/1.8.2 References: <20050822074856.77312.qmail@web31707.mail.mud.yahoo.com> In-Reply-To: <20050822074856.77312.qmail@web31707.mail.mud.yahoo.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-science@gentoo.org Reply-to: gentoo-science@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3253236.LmhzXdjEa6"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200508221005.24280.cryos@gentoo.org> X-Virus-Scanned: by amavisd-new at palladium.cryos.net X-Archives-Salt: 45ce8728-35e4-41cd-9adb-8cf8c27c201b X-Archives-Hash: 94cc41cf8890e41b07395e913fb0228c --nextPart3253236.LmhzXdjEa6 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 22 August 2005 08:48, C Y wrote: > Perhaps we could have a "support team" behind someone with official > Gentoo developer status - people could point out significant ebuilds > with most logic in place to the developer, help work out quirks in the > programs/ebuilds, and generally speed things up? Certainly the > developer would bear final responsibility but this way those of us with > five hours every month or so could help out too, particularly for > specialty packages. (BTY, if some genius could figure out brl-cad I > would be grateful - it's going to take me a year at this point :-/.) I was wondering myself if some people in here might be receptive to the ide= a=20 of a support team, much like the arch testers we have for the amd64 porting= =20 team. It often leads on to people becoming devs, but is a great way to help= =20 out when you can. Tony Murray is filling that kind of role unofficially with all the work he= =20 puts into the boinc and setiathome ebuilds, whilst I review, test, improve= =20 and commit them once they are up to standard. I also have good contact with= =20 the quickplot developer who has integrated my patches upstream and helped=20 significantly with the ebuilds for that package. I think these relationships are important, and I personally nurture them as= =20 much as possible. Many scientific packages are very involved and having=20 people help test and work out problems can significantly increase our=20 efficiency as a team. > > There are a fair number of at least partial ebuilds for useful > scientific software stuck in bugzilla - brl-cad and acl2 come > immediately to mind, and I know there are others. Plus a fair number > that don't have ebuilds where it would be useful to have them. Gentoo > is alreay one of the best for scientific software, due to compiling > things being easy and our ebuild pool, but we could definitely do > better. The problem comes down to manpower and a need to recruit some more people t= o=20 the team. Having a support team similar to the arch testers could certainly= =20 help in our case if those people were not ready to become devs/didn't have= =20 the time. Once a package has been committed they would also need to help wi= th=20 version bumps and fixing bugs with the new packages ideally. > > My machine is probably a poor test machine - what gentoo environment > would we need to maintain? Just an up to date Gentoo install is fine. If you are testing some more=20 experimental stuff (I test new baselayout, glibc, gcc and other core stuff= =20 sometimes) then a chroot might also be adviseable. Scientific apps just=20 require an up to date system. Thanks, Marcus =2D-=20 Gentoo Linux Developer Scientific Applications | AMD64 | KDE | net-proxy --nextPart3253236.LmhzXdjEa6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBDCZVUzgRsaX1BF70RAhIhAJwJqABpvaHUlQLC5iS5AeneFUjWzACgn+eY 6Z6v6hw+8M+gXU1p+P2uPwk= =WaI1 -----END PGP SIGNATURE----- --nextPart3253236.LmhzXdjEa6-- -- gentoo-science@gentoo.org mailing list