I have never invited so many people to a calendar event, so I trust your opinion, we should always aim to reduce the pain of whom is organizing this extra stuff. So from my side, I am happy to stick with the dev channel communication and the list extracted from yesterday's meeting.
An additional +1 to make it at a time "more India and East Asia in general friendly". Cheers -------------------------- Alessandro Benedetti Apache Lucene/Solr PMC member and Committer Director, R&D Software Engineer, Search Consultant www.sease.io On Fri, 21 Jan 2022 at 01:22, David Smiley <[email protected]> wrote: > I propose that the next committer meeting be held on Thursday, April > 14th. I'd be happy to host again unless someone wishes to take over. The > time is TBD. > > Continuing from today's meeting: We discussed the meeting invitation > itself a little. To be clear, all committers are officially invited via > the email announcement to the dev list. As a practical matter, I'm > skeptical about adding 89 committers[1] to my Google Calendar. Setting > that up seems like a pain and I wonder if a list that long is allowed. > Instead, I propose I duplicate the previous one, thus carry the list > forward. This is less work for everyone, I think. When someone next takes > over for me as host, we'll try to work this out. > > Perhaps the next meeting should be at a time more friendly to other > timezones like those in India? Just an idea; I feel bad when some of us > can't attend. Even if there are no requests for this, I propose we at > least move the next meeting to one hour earlier than previously to make it > a little nicer for Europe timezones. Pacific can wake up at 8am -- > personally I wake up at 6:40am every day :-) > > [1]: https://projects.apache.org/committee.html?solr > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley >
