| 1 |
Hi, everyone. |
| 2 |
|
| 3 |
TL;DR: the Council has approved adding the optional |
| 4 |
proxied="yes|no|proxy" (defaults to 'no') attribute to metadata.xml |
| 5 |
yesterday. Please wait a few more hours before using it. |
| 6 |
|
| 7 |
If you're not dealing with proxy maintenance at all, you can safely |
| 8 |
ignore this message. |
| 9 |
|
| 10 |
|
| 11 |
What's added? |
| 12 |
============= |
| 13 |
The <maintainer/> elements (used for Gentoo maintainers, not these |
| 14 |
in <upstream/>) now accepts an additional proxied="" attribute, that can |
| 15 |
be either: |
| 16 |
|
| 17 |
- proxied="yes" -- indicating that the person in question is a proxied |
| 18 |
maintainer (i.e. does not have direct push access) |
| 19 |
|
| 20 |
- proxied="no" (the default, so don't specify it) -- indicating that |
| 21 |
the person in question is a maintainer with push access |
| 22 |
|
| 23 |
- proxied="proxy" -- indicating that the developer in question only |
| 24 |
proxies (i.e. pushes commits) for somebody else and does not maintain |
| 25 |
the package itself |
| 26 |
|
| 27 |
|
| 28 |
What's needed to support it? |
| 29 |
============================ |
| 30 |
The updates to DTD and XML Schema were pushed yesterday (EU) evening, |
| 31 |
and I've just pushed pkgcore revbumps. I'm still waiting for rsync to |
| 32 |
catch up to upgrade pkgcore on Infra. So rough ETA, you can start using |
| 33 |
it in ~6 hours. |
| 34 |
|
| 35 |
If you see pkgcheck complaining about failing schema validation, upgrade |
| 36 |
it. |
| 37 |
|
| 38 |
|
| 39 |
How to use it? |
| 40 |
============== |
| 41 |
For regular dev-maintainers (with @gentoo.org), don't do anything. |
| 42 |
|
| 43 |
For proxied maintainers (including Gentoo devs without push access), use |
| 44 |
proxied="yes". For their respective proxies, use proxied="proxy". For |
| 45 |
example: |
| 46 |
|
| 47 |
<maintainer type="person" proxied="yes"> |
| 48 |
<email>fnord@×××××××.com</email> |
| 49 |
</maintainer> |
| 50 |
<maintainer type="project" proxied="proxy"> |
| 51 |
<email>proxy-maint@g.o</email> |
| 52 |
</maintainer> |
| 53 |
|
| 54 |
|
| 55 |
What's the gain? |
| 56 |
================ |
| 57 |
This will primarily power pkgcheck checks for stale proxy records. |
| 58 |
Currently they assume that everyone @gentoo.org has push access (which |
| 59 |
isn't correct) and only treats proxy-maint@g.o as proxy. With |
| 60 |
this data, the checks will be enhanced to explicitly recognize devs |
| 61 |
without push access and devs acting as proxies, and therefore report: |
| 62 |
|
| 63 |
a. whenever metadata.xml specifies only proxies, i.e. nobody in there |
| 64 |
has push access, |
| 65 |
|
| 66 |
b. whenever a proxy is left over when all proxied maintainers are |
| 67 |
removed. |
| 68 |
|
| 69 |
|
| 70 |
Questions? |
| 71 |
========== |
| 72 |
<fill here> |
| 73 |
|
| 74 |
-- |
| 75 |
Best regards, |
| 76 |
Michał Górny |
Archives