On 23. 6. 25 17:50, Greg Stein wrote:
The concept of "72 hours" is normal for Apache communities to reach
decisions. It provides everybody a chance to see the concern/issue/question
and respond to it. 72 hours spans weekends, so those in the community that
only contribute weekdays can also participate.
The 72 hour rule is a core feature of Apache governance. It is not a "rush"
to ask for 72 hours to ask for consensus, but is actually a *provision* of
time against taking unilateral immediate action.
The 72 hour span has existed at Apache for over 25 years. I am surprised
people find it concerning. It is completely normal.
Greg, this is not a release vote, or any kind of vote, nor even any kind
of situation where it would be appropriate to invoke the lazy consensus
rule. It's a discussion about a feature in the code and how to implement
it. These have been known to last for months if necessary. Nathan has
already said that he needs more time to research. I'd be surprised if
others were not in the same situation.
Why the rush? It's not as if there's a critical remote root access
exploit fix waiting to be released and we have (checks watch) 58:27 on
the timer before it all goes kaboom. This way, it just feels like you're
trying to pressure people into making hasty decisions.
Yes, we all know what those 72 hours are. A guideline.
-- Brane
