It would be great to have a calendar of these events if we're scheduling them on a regular cadence. We could use a shared Google Calendar or $tool to publish it.
Dinesh > On Aug 19, 2019, at 1:32 PM, sankalp kohli <kohlisank...@gmail.com> wrote: > > Thank you all for the feedback. It has been a week since last last feedback > so we will move forward with these meeting. We plan to start them post > NGCC. If anyone feedback is not addressed, please let me know. > > Also feedback on this will always be welcomed even when meetings are > ongoing as I am assuming shape of this meeting will keeping changing over > time based on feedback. > > On Mon, Aug 12, 2019 at 4:33 PM sankalp kohli <kohlisank...@gmail.com> > wrote: > >> Thanks Patrick for helping with logistics. We can certainly use your >> resources unless someone objects >> >> On Mon, Aug 12, 2019 at 10:42 AM Patrick McFadin <pmcfa...@gmail.com> >> wrote: >> >>> If it works for everyone, DataStax has some resources we could put to this >>> effort. We do large scale conferences like this all the time and have the >>> tools to pull it off. It would be a small group of people with full duplex >>> audio and video with the ability for 100s of people to watch in streaming. >>> As Scott mentioned, a recording could be made available after the fact for >>> anyone that wanted to review and historical purposes. >>> >>> If we go this route, I would suggest using the ASF Cassandra slack for >>> people posting questions. 1) It gets more people on slack 2) It's more or >>> less a permanent, searchable record. >>> >>> Patrick >>> >>> On Sun, Aug 11, 2019 at 10:18 AM Rahul Xavier Singh < >>> rahul.xavier.si...@gmail.com> wrote: >>> >>>> I think these meetings would be great.. if there is a specific >>> structure. >>>> We use a simple format that could help e.g. >>>> >>>> 1. Review long term vision/ roadmap. >>>> 2. Review next release / features that are in progress. >>>> 3. Discuss issues in general and make a game plan for the next quarter. >>>> >>>> Nothing too complicated, but at least some structure so that we are >>>> timeboxed on what we are doing. >>>> >>>> >>>> >>>> On Wed, Aug 7, 2019 at 7:42 AM Joshua McKenzie <jmcken...@apache.org> >>>> wrote: >>>> >>>>> The one thing we need to keep in mind is the "If it didn't happen on a >>>>> mailing list, it didn't happen <http://theapacheway.com/on-list/>" >>>>> philosophy of apache projects. Shouldn't constrain us too much as the >>>>> nuance is: >>>>> >>>>> *"Discussions and plan proposals often happen at events, in chats >>> (Slack, >>>>> IRC, IM, etc.) or other synchronous places. But all final decisions >>> about >>>>> executing on the plan, checking in the new code, or launching the >>> website >>>>> must be made by the community asyncrhonously on the mailing list."* >>>>> >>>>> So long as we keep that in mind (and maybe push it back to 8am PST >>> since >>>>> 9am can get pretty ugly for some of the more eastern european / asian >>>>> countries), makes sense to me. >>>>> >>>>> On Tue, Aug 6, 2019 at 6:07 PM Dinesh Joshi <djo...@apache.org> >>> wrote: >>>>> >>>>>> Thanks for initiating this conversation Sankalp. On the ASF front, I >>>>> think >>>>>> we need to ensure that non-Pacific time participants can also >>>> participate >>>>>> in the discussions. So posting the notes and opening up discussions >>>> after >>>>>> the meet up to dev@ would be a great way of making sure everyone >>> can >>>>>> participate and gets visibility. Additionally, we should consider >>>>>> scheduling this meetup in different timezones as far as logistics >>> allow >>>>> it. >>>>>> >>>>>> Dinesh >>>>>> >>>>>>> On Aug 6, 2019, at 2:58 PM, sankalp kohli <kohlisank...@gmail.com >>>> >>>>>> wrote: >>>>>>> >>>>>>> Hi All, >>>>>>> There are projects (like k8s[1]) which do regular meetings >>>>> using >>>>>>> video conferencing tools. We want to propose such a meeting for >>>> Apache >>>>>>> Cassandra once a quarter. Here are some of the initial details. >>>>>>> >>>>>>> 1. A two hour meeting once a quarter starting at 9am Pacific. We >>> can >>>>>> later >>>>>>> move this to other times to make it easier for other timezones. >>>>>>> 2. Agenda of the meeting will be due 2 days prior to the meeting. >>> A >>>>>> sample >>>>>>> agenda for next one could cover updates on 4.0 testing, any major >>>> bugs >>>>>>> found and/or fixed, next steps for 4.0, etc. >>>>>>> 3. Each agenda item will have a time duration and list of people >>> to >>>>> drive >>>>>>> that item. >>>>>>> 4. We will have a moderator for each meeting which will rotate >>> around >>>>> the >>>>>>> community members. >>>>>>> 5. We need to figure out which video conferencing tool to use for >>>> this. >>>>>>> Suggestions and donation of tools are welcome. >>>>>>> 6. We will have meeting notes for each item discussed in the >>> meeting. >>>>>>> >>>>>>> Motivation for such a meeting >>>>>>> 1. We currently have Slack, JIRA and emails however an agenda >>> driven >>>>>> video >>>>>>> meeting can help facilitate alignment within the community. >>>>>>> 2. This will give an opportunity to the community to summarize >>> past >>>>>>> progress and talk about future tasks. >>>>>>> 3. Agenda notes can serve as newsletters for the community. >>>>>>> >>>>>>> Notes: >>>>>>> 1. Does this violate any Apache rules? I could not find any rules >>> but >>>>>>> someone can double check >>>>>>> 2. Are there any other Apache projects which do something similar? >>>>>>> >>>>>>> This is a proposal at this time and your feedback is greatly >>>>> appreciated. >>>>>>> If anyone thinks this will not help then please provide a reason. >>>>>>> >>>>>>> Thanks, >>>>>>> Sankalp >>>>>>> [1] >>> https://github.com/kubernetes/community/tree/master/sig-storage >>>>>> >>>>>> >>>>>> >>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org >>>>>> For additional commands, e-mail: dev-h...@cassandra.apache.org >>>>>> >>>>>> >>>>> >>>> >>> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
