Hi Alex, This is an attempt to manage the tyranny of timezones with a worldwide community. That time is what gives New Zealand and Australia at least a chance to attend that isn't the middle of the night. The alternative would be to have two meetings for different timezones.
Patrick On Fri, Sep 25, 2020 at 2:07 AM Oleksandr Petrov <oleksandr.pet...@gmail.com> wrote: > Is it possible to find a time slot that is earlier than 12:30PM PST? It's > 9:30PM for most of Europe [1], and this meeting is rather important for > many of us to attend. > > [1] https://savvytime.com/converter/pst-to-sgt-cet-gmt/12-30pm > > On Fri, Sep 25, 2020 at 2:23 AM Patrick McFadin <pmcfa...@gmail.com> > wrote: > > > Hi everyone, > > > > First, I want to acknowledge some of the raw conversations today in the > > cassandra-dev slack channel. It was probably well overdue and if not for > > 2020 and what a wonderful year this has been, we might have gotten there > > earlier. I really appreciate how everyone who participated kept the > > conversation from completely devolving into something that wouldn't get > us > > anywhere as a project. I also want to say that I hope we don't forget to > > pause and give each other a break. People are already tense and on edge > > from months of pandemics, politics, social unrest, disasters, child care > > issues and a lot of other things on a long list. I find it helpful to > > assume that everyone I talk to is stressed out, behind schedule and > > probably has a boss pressuring them to do something. We share a really > > unique common bond by willfully choosing to work on distributed systems. > I > > hope we find more reasons to come together than be apart in the future. > > > > If I can even attempt to sum up the important themes from a very long > > conversation. There is a tension between the frozen codebase leading to > 4.0 > > and the desire to add new features beyond 4.0. One way to eliminate that > > tension is to get 4.0 wrapped up. What is left to get 4.0 done isn't > clear > > to many and there is a desire to get clear on the remaining items. > > > > I would like to contribute some of my energy and time to help this along. > > Standing on the shoulders of giants here, a LOT of work has already gone > > into this topic. Josh, Jordan and Jon (J^3 ?) kept a steady strain on > > updating jiras and status. This Kanban is really helpful: > > > > > https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&quickFilter=1661 > > > > There is an epic that was discussed in slack: > > https://issues.apache.org/jira/browse/CASSANDRA-15536 > > > > There are 17 separate jiras as dependencies, of which only 2 are marked > as > > completed. 3 have no assigned owner. I have put a Zoom call on the > > contributor meeting calendar to discuss those three first. I had to weave > > it between ApacheCon sessions but hopefully this will help in velocity. > > Agenda > > posted, feel free to alter as you see fit. September 29, 1230PM PST: > > > > > https://cwiki.apache.org/confluence/display/CASSANDRA/2020-09-29+Apache+Cassandra+Contributor+Meeting+-+4.0+push+edition > > > > I mentioned this is Slack. We are so close. Beta 2 is out there, Harry > just > > dropped and Jiras have been closing. I get excited when I think of the > > impact this will have. My entire life has now somehow become dependent on > > Cassandra working. When I take a pic with my iPhone. Play games on my > > PlayStation. Use curb-side pickup at Target. Order food on GrubHub. > > Everybody here helped make that happen and there are a lot of great > > engineers that will be deploying 4.0 and loving it. Most importantly, I > > reliably get food when I'm playing Ghost of Tsushima and take a selfie > for > > my finsta. #priorities I would love to stick it to 2020 and make > "Shipping > > 4.0" a positive event as we leave this stinking year behind. > > > > Patrick > > > > > -- > alex p >
