I'm fine with that. Sounds like a good idea! It'd just be great if someone else could drive that. I don't have much time the next few weeks.
The lazy consensus thing we already do have, no? If I remember correctly we have this provision where - after waiting for a day or so - you can just commit yourself if no one gets to it. Is that what you were looking for? Christofer Dutz <[email protected]> schrieb am Mo., 30. Sep. 2019, 07:39: > Hi Lars, > > I think perhaps a more relaxed approach would be ok: > - CTR for content modules as this simplifies new contributions > - RTC for core modules such as the presentation framework, themes and > stuff used by presentations. > > I would also suggest to sort of have a lazy consensus on the reviews for > the RTC cause this might prevent decisions being postponed too long. > > Chris > > Am 30.09.19, 15:25 schrieb "Lars Francke" <[email protected]>: > > Hi everyone, > > it was great meeting some of you at ApacheCon NA and I look forward to > meeting a few more in Berlin. > > I've been approached again with the complaint that contributions to the > Training project are too hard due to the review requirements. How > about we > change that then? > I don't feel as strongly about this anymore as I initially did and I > don't > want to cause any harm or make anyone feel unwelcome. > > I'm still a fan of RTC instead of CTR because I've seen the Review not > happen too often in the latter model but this is something we can > always > change again if we feel the need for it. > > If anyone wants to start a vote on this I'd be happy to +1 it. I've > been > very absent these last two months but starting in mid-October I hope to > have more time again. > > Cheers, > Lars > > >
