1 |
On Mon, Jul 04, 2022 at 04:19:12PM +0200, Florian Schmaus wrote: |
2 |
> I'd like to propose a new metadata XML element for packages: |
3 |
> |
4 |
> <non-maintainer-commits-welcome/> |
5 |
> |
6 |
> Maintainers can signal to other developers (and of course contributors |
7 |
> in general) that they are happy with others to make changes to the |
8 |
> ebuilds without prior consultation of the maintainer. |
9 |
> |
10 |
> Of course, this is not a free ticket to always make changes to packages |
11 |
> that you do not maintain without prior consultation of the maintainer. I |
12 |
> would expect people to use their common sense to decide if a change may |
13 |
> require maintainer attention or not. In general, it is always a good |
14 |
> idea to communicate changes in every case. |
15 |
> |
16 |
> The absence of the flag does not automatically allow the conclusion that |
17 |
> the maintainer is opposed to non-maintainer commits. It just means that |
18 |
> the maintainer's stance is not known. I do not believe that we need a |
19 |
> <non-maintainer-commits-disallowed/> flag, but if the need arises, we |
20 |
> could always consider adding one. Although, in my experience, people |
21 |
> mostly like to communicate the "non-maintainer commits welcome" policy |
22 |
> with others. |
23 |
> |
24 |
> WDYT? |
25 |
|
26 |
Personally I think something per-maintainer rather than per package |
27 |
would be simpler, and allow to say more as needed. |
28 |
|
29 |
Think like devaway instructions, but something more permanent and |
30 |
not for being away, e.g. |
31 |
"feel free to touch my packages except this big important one, and |
32 |
or do or do not do this to them" |
33 |
|
34 |
> |
35 |
> - Flow |
36 |
> |
37 |
|
38 |
-- |
39 |
ionen |