1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
All, |
5 |
As some of you may have seen, over the past couple months I've been |
6 |
serving as a proxy-maintainer on a number of packages for a fair few |
7 |
proxy-committeers through what I've been calling C1phers Adopt a Package |
8 |
Program [1]. So far, I would consider it to be a success. A fair few |
9 |
packages have been adopted (over 15 at this point IIRC). There are a |
10 |
couple problems with this existing in the way that it does however. |
11 |
1) I am the sole point of contact for all of these packages. |
12 |
2) It is not really "official". A blog post that some people have seen |
13 |
doesn't really attract a ton of users to get involved. (Though it's done |
14 |
better than I would have guessed). |
15 |
3) As it grows, it becomes a fair bit of work for the one guy involved |
16 |
(me) =P. |
17 |
|
18 |
Now, I know there are a fair few packages in the tree that have other |
19 |
proxy-maintainers. (I'm too lazy to get a real number, so sue me.) So |
20 |
here is what I think would be a good idea to do. |
21 |
|
22 |
Create a formal Gentoo project with its own herd and alias. Whenever a |
23 |
packages has a proxy-maintainer, instead of having 2 maintainer entries |
24 |
(one for the user, one for the dev), have the users contact information, |
25 |
and put the package in the herd associated with the project. (Say |
26 |
proxy-maintained with the alias proxy-maintained@g.o.) From there, users |
27 |
that want to have something committed can use the alias, and any dev |
28 |
that's helping with that project can review it quickly and commit it for |
29 |
them. Or if they so choose, they can add themselves to the metadata in |
30 |
addition to the herd and it will be left to them as long as they get to |
31 |
it in a reasonable amount of time. Otherwise someone else can step in |
32 |
and help out. |
33 |
|
34 |
I think this serves a fair few purposes. First off, I would imagine it |
35 |
will take a pretty decent dent out of our growing count of m-n packages. |
36 |
It makes life easier for the proxy-maintainers and their committers. It |
37 |
allows users who want to proxy-maintain something to find the group of |
38 |
people who will help out rather than having to put a call out on the |
39 |
mailing lists. And, it will mean that users involved in the project can |
40 |
get some recognition on the project page. |
41 |
|
42 |
I do realize there is a small amount of overlap with the already |
43 |
existent Sunrise package, however, given that usually Sunrise serves as |
44 |
a home for m-w packages, I think this can help fill the gap left for the |
45 |
m-n packages. (And help provide a logical transition from Sunrise to |
46 |
Portage). |
47 |
|
48 |
Well, that about covers it. What does everyone think? Good idea? Bad |
49 |
idea? Waste of time? Are you crazy? Let's hear it! |
50 |
|
51 |
Thanks! |
52 |
|
53 |
[1] http://dev.c1pher.net/index.php/2011/03/c1phers-adopt-a-package-program/ |
54 |
|
55 |
- -- |
56 |
Dane Smith (c1pher) |
57 |
Gentoo Linux Developer -- QA / Crypto / Sunrise / x86 |
58 |
RSA Key: http://pgp.mit.edu:11371/pks/lookup?search=0x0C2E1531&op=index |
59 |
-----BEGIN PGP SIGNATURE----- |
60 |
Version: GnuPG v2.0.17 (GNU/Linux) |
61 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
62 |
|
63 |
iQIcBAEBAgAGBQJOAggbAAoJEEsurZwMLhUxLKQP+waNFwYgfWcm1eJDfIk7sY0+ |
64 |
EhZ0yHGVo/aOZ4P/SZMqb1tjf8tgNwaQV8dkPLIGvWFZ4ThExHRJ2FEANakAZgp4 |
65 |
TJCM004xQvX5TQ6QkmQVdTbHqyq0AMZukF3lAsOUWfWfYH776MHR+dKTfpDZg7Gt |
66 |
RvAHjEknHbqvaMZEEqF2rLCV9Gzlg4LxQnz/VaoTt0662o5jlCVltJAqYX094rgi |
67 |
ZAesyeEcy1/1cgKes44/2a6ETbV/isD4UgU0KZHz8Msu8gtE1OWk+ZBoCfE5mYmb |
68 |
D8/xZGx/irdzQMm3aVQviHKZEQMaz70/zpGCfmrmYQSOR232FMJEN4tErMys5Z2D |
69 |
lQ4QfeOTwhHsRFPVFZmg0QD9TMcgAI2Uc+Ck32JOHLIrLOw02tUIh00Danjp4TBK |
70 |
ctNong4g6ayG0BUKByrFP5zrfUV3vQE5L/cul4JlPKbhqGdLl1RpxjqpUG1lCteX |
71 |
FSafKH2aoct2YMTHs1ve0FO3zwsMzo1k7MWWTZWdGmJG9S2GwBQs0yGvtAYwqVQ7 |
72 |
csCkwiROtSUMJzgi4SlBGuZpZ1qemy2CSXIeatYz9ol4W/ixZj6FMw66TbZb+Hjg |
73 |
ZXt5vFX3N2qwqZwl6GHSQCkV/EhaPKSoecN5i4kO052NtOTblRXlsISJiptuLqR9 |
74 |
h1raPYZxIQ8ZoW3elR6z |
75 |
=y21y |
76 |
-----END PGP SIGNATURE----- |