1 |
Dnia 2014-09-10, o godz. 07:53:31 |
2 |
Rich Freeman <rich0@g.o> napisał(a): |
3 |
|
4 |
> On Wed, Sep 10, 2014 at 7:33 AM, Pacho Ramos <pacho@g.o> wrote: |
5 |
> > |
6 |
> > Personally I would vote for simply have a <maintainer> tag pointing to |
7 |
> > the alias but we would still need to keep a list of real maintainers for |
8 |
> > that alias as usually not all people listed in the alias are willing to |
9 |
> > maintain the packages. |
10 |
> > |
11 |
> |
12 |
> I think the solution to this is that maintainers can be either: |
13 |
> 1. Devs - identified by their email address. (simple enough) |
14 |
> or |
15 |
> 2. Projects - identified by their email alias. |
16 |
> or |
17 |
> 3. A proxy maintainer identified by email address (in which case |
18 |
> either a dev or project must also be listed, potentially including the |
19 |
> proxy maintainer project). |
20 |
|
21 |
4. A mail alias that is not project :). For example, we have clang@ for |
22 |
easily aggregating all clang-related build failures and other bugs but |
23 |
it isn't a formal team. |
24 |
|
25 |
It's hard if such a thing has proper member list. But in any case, is |
26 |
there a reason for needing to have definitive member list? |
27 |
|
28 |
-- |
29 |
Best regards, |
30 |
Michał Górny |