1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Hi all, |
5 |
|
6 |
currently I am a maintainer for two packages -- and as a non-gentoo-dev |
7 |
being proxied by guys who are. |
8 |
|
9 |
Now a disadvantage of this position are the restricted rights in |
10 |
bugzilla. In case a bug is filed for one of my maintained packages I |
11 |
have to ask one of my proxies for each step ("could you mark this as a |
12 |
dupe?", "could you mark this as fixed?", etc.). This is quite cumbersome |
13 |
and puts just some load on the devs (which should have been avoided by |
14 |
the proxy-solution in the first place). |
15 |
|
16 |
So I am asking whether there would be a solution to allow people like me |
17 |
to have full bugzilla rights on packages they are in charge for. |
18 |
|
19 |
Two possibilities come to my mind: |
20 |
|
21 |
1) Have an implicit restriction, i.e. give them full rights (where |
22 |
"full" just means: everything they need for handling their bugs), but |
23 |
make a policy, that they are only allowed to use this for their |
24 |
packages. In other words: Enforce the correct usage by "legal" ways |
25 |
instead of teachnically. |
26 |
|
27 |
This approach is probably easier in terms of bureaucracy but might be |
28 |
seen as dangerous. |
29 |
|
30 |
2) Enforce the restriction technically. I do not know how this could be |
31 |
done in bugzilla - perhaps by having "proxy-herds", i.e. one herd for |
32 |
each proxied package and only give the user the full rights, if a bug is |
33 |
assigned to a herd he is a member of. |
34 |
|
35 |
The disadvantage is here, that there is quite some overhead of managing |
36 |
a bunch of "proxy-herds". |
37 |
|
38 |
Some sort of "bugzilla quiz" which needs to be taken by the maintainer |
39 |
might be useful in both cases. |
40 |
|
41 |
I'd be glad to hear some other opinions. |
42 |
|
43 |
- - René |
44 |
-----BEGIN PGP SIGNATURE----- |
45 |
Version: GnuPG v2.0.14 (GNU/Linux) |
46 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
47 |
|
48 |
iEYEARECAAYFAkuxH9sACgkQ4UOg/zhYFuAvogCfflrqjFg6iMq6OGEfp7Z4NHXS |
49 |
ERUAnAonFFHRlGRYuKVSL12Vb2WinSAr |
50 |
=1DOx |
51 |
-----END PGP SIGNATURE----- |