1 |
Hi folks, |
2 |
|
3 |
|
4 |
in light of some recent discussions where overlay maintainers found |
5 |
that bug reports had been assigned "incorrectly" and thought it was apt |
6 |
to inform the miscellaneous bug wranglers of the correct assignees, I |
7 |
thought it would be a good idea to introduce a new list, akin to |
8 |
metadata.xml and herds.xml, to resolve this issue once and for all. As |
9 |
with herds and metadata, this overlays.xml should list a repository's |
10 |
name, HOMEPAGE and the e-mail address(es) of its maintainers. |
11 |
|
12 |
In the absence of such information, a bug wrangler may assign the bug |
13 |
report to someone who has contributed to the overlay in question, or to |
14 |
anyone who might reasonably know whom to properly assign the bug report |
15 |
to. |
16 |
|
17 |
In case assignment goes awry, and when the assignee is part of the team |
18 |
of proper assignees, then the team or assignee should make sure |
19 |
overlays.xml is updated to reflect the current maintainance status and |
20 |
should add the remainder of the assignees themselves. Nothing else |
21 |
needs to be done in this case - the next time a different bug wrangler |
22 |
might be handling a bug report about that overlay, so CC'ing or pinging |
23 |
(on IRC) doesn't make sense - updating overlays.xml would. If the |
24 |
assignee is not part of the maintainer team of the overlay in question, |
25 |
then the bug may be bounced back to bug-wranglers@g.o. |
26 |
|
27 |
Please discuss. |
28 |
|
29 |
|
30 |
Kind regards, |
31 |
jer |