1 |
On 9/17/15 6:32 AM, Michał Górny wrote: |
2 |
> |
3 |
> Dnia 17 września 2015 11:07:43 CEST, "Anthony G. Basile" <blueness@g.o> napisał(a): |
4 |
>> On 9/17/15 4:35 AM, Justin (jlec) wrote: |
5 |
>>> On 16/09/15 23:43, Matthew Thode wrote: |
6 |
>>>> On 09/16/2015 04:25 PM, Michał Górny wrote: |
7 |
>>>>> So, what are your thoughts for unmessing this? |
8 |
>>>>> |
9 |
>>>> Herds are groups of developers that can then be mapped to a package. |
10 |
>>>> |
11 |
>>> Herds are a group of packages, which are maintained my one or more |
12 |
>> developers or |
13 |
>>> a project team consisting of one or more developers. |
14 |
>>> |
15 |
>>> |
16 |
>>> |
17 |
>> Let's begin by eliminating herds. We can do that by absorbing herds |
18 |
>> into projects where that makes sense (eg base-system), or expanding the |
19 |
>> |
20 |
>> herd into the respective maintainers where a clear association between |
21 |
>> herd and project does not make sense. An ebuild can then have a |
22 |
>> <project> tag in which case it is maintained by all members of a |
23 |
>> project |
24 |
>> or a maintainer list, or a combination of both. It can also have an |
25 |
>> observer tag for devs that want to track that pkg's maintenance while |
26 |
>> not being a maintainer. |
27 |
> This is not semantically correct for XML. Type of maintainer should be indicated by subelement or attribute, not three identical elements. |
28 |
|
29 |
Are you saying you can't come up with semantic for XML to do this? C'mon |
30 |
what I have below isn't the best, but we can come up with something here. |
31 |
|
32 |
> |
33 |
>> Aliases can be associated with projects in the same way that ebuilds |
34 |
>> are. An alias can either belong to a project, in which case it expands |
35 |
>> |
36 |
>> to all the project members plus other added emails, or just a free |
37 |
>> standing alias with just members. |
38 |
>> |
39 |
>> Eg1. I'm not on base system, so an pkg with |
40 |
>> |
41 |
>> <project> |
42 |
>> <name>base-system</name> |
43 |
>> <email>base-system@g.o</email> |
44 |
> People aren't going to be happy about this. Their VAX-11s may not be able to handle typing the extra bytes when they do their daily routine of writing 200 metadata.xml files. |
45 |
|
46 |
I'm not sure what you mean here, but the initial migration would be |
47 |
automated. I don't see why maintenance after that would be difficult. |
48 |
|
49 |
> |
50 |
>> </project> |
51 |
>> <maintainer> |
52 |
>> <name>Anthony G. Basile</name> |
53 |
>> <email>blueness@g.o</email> |
54 |
>> </maintainer> |
55 |
>> <observer> |
56 |
>> <name>Devan Franchini</name> |
57 |
>> <email>twitch153@gentoo</email> |
58 |
>> <observer> |
59 |
> This looks like a serious overkill. Both in the terms of commits and effort required. |
60 |
|
61 |
What's the overkill part? The <observer> tag was just to coalesce the |
62 |
construction of an alias with the metadata.xml. |
63 |
|
64 |
> |
65 |
>> would be maintained by all of base system with alias |
66 |
>> base-system@g.o and me. twitch153 is listed as just an observer |
67 |
>> |
68 |
>> of the pkg and would receive emails but not technically be allowed to |
69 |
>> maintain the package. The email alias for this pkg is automatically |
70 |
>> generated from the metadata.xml. |
71 |
> This sounds like a lot of alias changes. What about package removals? Do aliases get removed too? |
72 |
|
73 |
Totally rethink the idea of emails aliases as something that is created |
74 |
on the fly. We just need to know who should get emails for a package |
75 |
when it comes to bug reports. Why can't that be calculated on the fly |
76 |
from the metadata.xml? |
77 |
|
78 |
> What about synchronization delays? What about all the extra bugzie accounts? |
79 |
Again, I think we can come up with something here. Let's design |
80 |
something that'll be easy to work with and then figure out how to |
81 |
implement it. |
82 |
|
83 |
> |
84 |
>> |
85 |
>> Eg2. A "free standing" ebuild could have |
86 |
>> |
87 |
>> <maintainer> |
88 |
>> <name>Anthony G. Basile</name> |
89 |
>> <email>blueness@g.o</email> |
90 |
>> <proxy/> |
91 |
>> </maintainer> |
92 |
>> <maintainer> |
93 |
>> <email>bugs@××××××××××.nu</email> |
94 |
>> <name>Johan Bergström</name> |
95 |
>> </maintainer> |
96 |
>> |
97 |
>> Again the alias for this pkg is automatically generated from the |
98 |
>> metadata.xml |
99 |
>> |
100 |
>> Thoughs? |
101 |
|
102 |
|
103 |
-- |
104 |
Anthony G. Basile, Ph.D. |
105 |
Gentoo Linux Developer [Hardened] |
106 |
E-Mail : blueness@g.o |
107 |
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA |
108 |
GnuPG ID : F52D4BBA |