CTR is completely inappropriate for any Apache project. The current situation where single individuals can ship changes to millions of users is insecure and dangerous. It needs to stop. Projects that can't operate effectively under CTR due to lack of maintainers need to either recruit more maintainers or shut down.
On Mon, Oct 27, 2025 at 11:36 AM Emmanuel Bourg <[email protected]> wrote: > > On 27/10/2025 11:47, Gary Gregory wrote: > > This is a poll to gauge the waters for CTR. > > > > There is way too much Byzantine bureaucracy in this project. > > > > It's constantly throwing spans in the wheels of progress: > > > > A PR for adding one getter method turns into a request for porting a > > code base from IO to NIO, see > > https://lists.apache.org/thread/l23k5n6spfgs05ds06t4hpgmmssqpzvd > > > Apache Commons is already commit then review, which is unfortunate in > some cases, like when unnecessary dependencies were introduced to > commons-compress without prior discussion. And despite the late review > and veto it was never reverted. > > That's not an issue for trivial changes like adding a getter or doing > internal changes, but for things difficult to revert it becomes an issue. > > +1 for CTR on simple, low impact, changes > -1 to non trivial changes without discussion or consensus > > Emmanuel Bourg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Elliotte Rusty Harold [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
