List Archive: gentoo-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
Is introduction of such a high level of bureaucracy really a good idea?
In my eyes it could backfire and make matters worse as people either
- start ignoring it due to high noise
- reduce people's activity below set permissions
To summarize presented proposal has a few points that may not work well
with humans. To my understanding we have the assumption in Gentoo that
a Gentoo dev is at least willing to use his brain most of the time. To
me such a machine only makes sense when assuming the opposite(!)
So I would like to propose a much more loose and simple approach: A
- between major and minor changes
- need for prior interaction or not
A sensible default may differ from developer to developer. I propose
collecting these defaults somewhere and make it overridable per
maintainer per package in metadata.xml (just as robbat2 did).
One question to decide would be if access is allowed iff
- no one is objecting or
- everyone is acknowledging
Once all defaults are collected the options are equal, before they are not.
How to best handle herds is not clear to me in detail, yet.
Anyone seing potential in this minimalistic with a natural extension on
herds in mind?