| 1 |
On Mon, Jul 04, 2022 at 05:27:03PM +0200, David Seifert wrote: |
| 2 |
> On Mon, 2022-07-04 at 16:19 +0200, Florian Schmaus wrote: |
| 3 |
> > I'd like to propose a new metadata XML element for packages: |
| 4 |
> > |
| 5 |
> > <non-maintainer-commits-welcome/> |
| 6 |
... |
| 7 |
> Ultimately, all these things really matter when only the defaults |
| 8 |
> change. Turn-right-on-red in the US is such a thing, because unless |
| 9 |
> otherwise stated, it's the norm. Knowing our devbase, with roughly 75% |
| 10 |
> mostly AWOL and barely reading the MLs, I don't think this idea will |
| 11 |
> bring about the desired change. Instead, we should really just go for |
| 12 |
> the <non-maintainer-commits-disallowed/> tag, because my feeling is that |
| 13 |
> the default will be that most maintainers don't mind non-maintainer |
| 14 |
> commits, except a select few territorial ones. |
| 15 |
|
| 16 |
I had a rough draft similar proposal to this before that was never |
| 17 |
completed into GLEP. |
| 18 |
|
| 19 |
It had 3 states however: |
| 20 |
a) go ahead and touch it, no additional approvals needed |
| 21 |
b) please get a maintainer to approve it |
| 22 |
c) do not touch it |
| 23 |
|
| 24 |
With b) being the proposed default as status-quo at the time. |
| 25 |
|
| 26 |
That however was years ago, and I'll entirely agree that the devbase |
| 27 |
isn't as watchful anymore. |
| 28 |
|
| 29 |
With that said, I stand behind the intent of making the default a), with |
| 30 |
a migration period. |
| 31 |
|
| 32 |
Something like this for the migration period: |
| 33 |
July 1 to Sep 30: default is still b), to allow developers time to update |
| 34 |
their metadata. |
| 35 |
Oct 1 onwards: default becomes a) |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
Robin Hugh Johnson |
| 40 |
Gentoo Linux: Dev, Infra Lead, Foundation Treasurer |
| 41 |
E-Mail : robbat2@g.o |
| 42 |
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 |
| 43 |
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136 |
Archives