As an observer without a vote, my concern with CTR is security: can it prove via an audit log that every commit was reviewed by an active committer? Without that guarantee, RTC feels like the safer option.
Seems to me the problem is the way review are done, and the lack of clarity and expectation around when a change request needs to go into a review before it’s approved and when it can be a follow up. Thanks Dan B Daniel Burrell Head of Platform Engineering | B2C2 Ltd. Digital asset pioneer building the ecosystem of the future Hedgeweek Global Digital Asset Awards 2024: Market Making Provider of the Year On Mon, 27 Oct 2025 at 17:53, Gary Gregory <[email protected]> wrote: > On Mon, Oct 27, 2025, 13:43 Matt SIcker <[email protected]> wrote: > > > I’m in favor of whatever process makes this project enjoyable to > > contribute to again. In the past, we embraced the Apache Way of a > > “do-ocracy” where people just sort of work on what they want to work on, > > and things work out in the end because this philosophy embraces community > > over code. Projects that demand perfect code end up dead once the > > gatekeeper stops caring about the project (see for example qmail). > > > > Down with the fun! It feels to me like we have process _over_ community, > not community over code. > > Gary > > > > > On Oct 27, 2025, at 6:25 AM, Gary Gregory <[email protected]> > > 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 > > > > > > Gary > > > > > -- *This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you must not disseminate, distribute or copy this e-mail. Please notify us on [email protected] <mailto:[email protected]> immediately if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.*
