1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Kurt Lieber schrieb: |
5 |
| Ignoring the yellow star issue, there are a few implementation |
6 |
| concerns/impossibilities with GLEP 41 in its current form. |
7 |
| |
8 |
| For instance, the way GLEP 41 suggests doing r/o cvs is not going to work. |
9 |
| It suggests using a single account and placing an SSH key for each arch |
10 |
| tester in that account's ~/.ssh/authorized_keys file. |
11 |
| |
12 |
| There are no provisions for key management and I cannot see an easy way to |
13 |
| handle it. It's easy to add new keys, but how do we clean out old |
14 |
keys for |
15 |
| retired arch testers? (including arch testers that "retire" without ever |
16 |
| informing us) SSH doesn't log key ID as near as I can tell, so we have no |
17 |
| way of tracking what keys are used and how often. Also, how do we |
18 |
| definitively correlate an SSH key with an arch tester? |
19 |
Do we have to? Nobody has to track how often an Arch Tester uses RO |
20 |
access to CVS, as you don't need that information. RO CVS access is a |
21 |
service to the ATs. Their work is pretty much outside CVS... |
22 |
|
23 |
| Now, the same question for email -- how do we manage aliases, especially |
24 |
| for inactive, retired and semi-retired arch testers? We could track usage |
25 |
| in logs, but between mailing list subscriptions, bugzilla |
26 |
notifications and |
27 |
| all sorts of other automated emails, that's not an accurate representation |
28 |
| of whether an email alias is actively used or not. |
29 |
Afaik the gentoo.org address is only a forward to their normal adress, |
30 |
so one can hardly speak 'active usage'. You simply can't actively use |
31 |
it! On the other hand, tracking down how active/inactive a AT/HT is |
32 |
falls under the project the AT/HT is associated with, or the AT/HT |
33 |
Project (hparker) as last resort. So if he says 'AT foo is inactive', |
34 |
he's to be removed from email forwarding and CVS RO Access. I really |
35 |
don't see the problem here. |
36 |
|
37 |
Danny |
38 |
- -- |
39 |
Danny van Dyk <kugelfang@g.o> |
40 |
Gentoo/AMD64 Project, Gentoo Scientific Project |
41 |
-----BEGIN PGP SIGNATURE----- |
42 |
Version: GnuPG v1.4.1 (GNU/Linux) |
43 |
|
44 |
iD8DBQFDf2eVaVNL8NrtU6IRAoyTAJ0ey3mRDulIHz2KMtZjCM0zWEOKWwCffHsx |
45 |
pcnKGFfZ9OoXBRV2RhKKAOU= |
46 |
=vTjI |
47 |
-----END PGP SIGNATURE----- |
48 |
-- |
49 |
gentoo-dev@g.o mailing list |