Yes, it's CTR vs RTC with variations on the seriousness of the review. A small impact change needs a single review from another committer while a big change needs a binding vote majority.
It's also unclear to me how "product management" and "user experience design" would work under Apache. Because here we could decide to reject a contribution on UX/product considerations alone. Not sure how voting would help/work here. --emi Pe 20 iun. 2017, la 12:17, Bertrand Delacretaz <[email protected]> a scris: > Hi, > >> On Tue, Jun 20, 2017 at 10:38 AM, Emilian Bold <[email protected]> >> wrote: >> ...high impacting API / SPI changes must have proper voting.... > > I think what you're describing is CTR vs. RTC > (https://www.apache.org/foundation/glossary.html) > > Many projects have some areas of their codebase under RTC, typically > based on module names or attributes like "it's an API", based on a > documented list of where CTR applies. > > OTOH if all changes are consistently and relatively quickly reviewed, > source code control is your friend and nothing bad can happen. > > -Bertrand
