I run the local Cassandra User Group and I would love to help get the community more involved. I would propose holding a night to add patches to Cassandra some will be simple things like making sure some asserts have proper messages with them etc, but some may be slightly larger. The goal being to just get people used to the process, to help make this a success it would be great if we could have support on getting the patches we submit at least looked at briefly in 1 month. That timeframe allows us to talk about it at the next meetup and show people their contributions even small ones are valued.
Before we did this night I would probably dig through some tickets and get an example list going and any feedback notes on making the process easier would be great. Generally if there is anything you need from the meetups ask I know I will do my best to get the local group to support things. Jeff On Fri, Nov 4, 2016 at 6:08 PM Aleksey Yeschenko <alek...@apache.org> wrote: Dunno. A sneaky correctness or data corruption bug. A performance regression. Or something that can take a node/cluster down. Of course no process is bullet-proof. The purpose of review is to minimise the odds of such a thing happening. I’m sure users running Cassandra in production would prefer actual proper reviews to non-review +1s. -- AY On 4 November 2016 at 23:03:23, Edward Capriolo (edlinuxg...@gmail.com) wrote: I feel that is really standing up on a soap box. What would be the worst thing that happens here
