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.50) id 1EdWxt-0002Fr-Ka for garchives@archives.gentoo.org; Sat, 19 Nov 2005 17:57:30 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jAJHtwVN025913; Sat, 19 Nov 2005 17:55:58 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jAJHpq0d032534 for ; Sat, 19 Nov 2005 17:51:52 GMT Received: from p83.129.26.248.tisdip.tiscali.de ([83.129.26.248] helo=[192.168.101.99]) by smtp.gentoo.org with esmtpa (Exim 4.43) id 1EdWsR-0006V2-If for gentoo-dev@lists.gentoo.org; Sat, 19 Nov 2005 17:51:52 +0000 Message-ID: <437F6795.7000307@gentoo.org> Date: Sat, 19 Nov 2005 18:57:41 +0100 From: Danny van Dyk User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050901) X-Accept-Language: de-DE, de, en-us, en 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] implementation details for GLEP 41 References: <20051119170615.GW12982@mail.lieber.org> In-Reply-To: <20051119170615.GW12982@mail.lieber.org> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: ac2c23a8-9841-41e0-9b75-1fae5860a1fe X-Archives-Hash: 4ea1ab3b9c2259e593c4dfcd3c82c1df -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kurt Lieber schrieb: | Ignoring the yellow star issue, there are a few implementation | concerns/impossibilities with GLEP 41 in its current form. | | For instance, the way GLEP 41 suggests doing r/o cvs is not going to work. | It suggests using a single account and placing an SSH key for each arch | tester in that account's ~/.ssh/authorized_keys file. | | There are no provisions for key management and I cannot see an easy way to | handle it. It's easy to add new keys, but how do we clean out old keys for | retired arch testers? (including arch testers that "retire" without ever | informing us) SSH doesn't log key ID as near as I can tell, so we have no | way of tracking what keys are used and how often. Also, how do we | definitively correlate an SSH key with an arch tester? Do we have to? Nobody has to track how often an Arch Tester uses RO access to CVS, as you don't need that information. RO CVS access is a service to the ATs. Their work is pretty much outside CVS... | Now, the same question for email -- how do we manage aliases, especially | for inactive, retired and semi-retired arch testers? We could track usage | in logs, but between mailing list subscriptions, bugzilla notifications and | all sorts of other automated emails, that's not an accurate representation | of whether an email alias is actively used or not. Afaik the gentoo.org address is only a forward to their normal adress, so one can hardly speak 'active usage'. You simply can't actively use it! On the other hand, tracking down how active/inactive a AT/HT is falls under the project the AT/HT is associated with, or the AT/HT Project (hparker) as last resort. So if he says 'AT foo is inactive', he's to be removed from email forwarding and CVS RO Access. I really don't see the problem here. Danny - -- Danny van Dyk Gentoo/AMD64 Project, Gentoo Scientific Project -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDf2eVaVNL8NrtU6IRAoyTAJ0ey3mRDulIHz2KMtZjCM0zWEOKWwCffHsx pcnKGFfZ9OoXBRV2RhKKAOU= =vTjI -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list