Hi Sönke, thanks for bringing this up ... Yes ... don't know if you were referring to me, but I did really stop contributing, because I thought the process was getting in the way of getting stuff done.
I would suggest to definitely go to "commit then review" for content. We could consider staying at "review then commit" for the tooling and main theme stuff, as this would affect others more than content does. But I would also opt for going to the simper process in general and perhaps change things if things go south. I think my unreviewed PR that lay dormant for months is a great demonstration of the "review then commit" not working. Chris Am 24.01.20, 12:09 schrieb "Sönke Liebau" <[email protected]>: Hi everybody, as mentioned in our current board report I feel like we should revisit the commit and review guidelines [1] that we currently have in place. I have heard that in at least one instance individuals decided to stop contributing to this project because doing so was overly complicated and regulated - which personally I take as a serious red flag. What do people think, should we move to a commit then review model, for everything, just for content contributions, treat code separately, ... Personally I'd like to at least see some sort of check in place that only content that was actually reviewed makes it into a release. Personally, I feel that commit then review will lead to a large amount of unreviewed content, but if I am the only one that thinks so I am willing to adapt and try something else :) Best regards, Sönke [1] https://training.apache.org/developers/contributing.html#_toc_review_process1
