So….    I went to check on this, and I guess it was yesterday?

How about making the next one three months from yesterday and be July 12 at 
noon EST?

Eric


> On Apr 7, 2022, at 11:41 AM, Houston Putman <[email protected]> wrote:
> 
> Tuesday April 12 is relatively safe, though it's a bit short notice?
> 
> Wish that site went further than 7 days...
> 
> On Thu, Apr 7, 2022 at 4:36 AM Jan Høydahl <[email protected] 
> <mailto:[email protected]>> wrote:
> April 14th is a public holiday in Norway as well as a huge number of other 
> countries https://www.timeanddate.com/holidays/ 
> <https://www.timeanddate.com/holidays/>
> Probably wise to find another date.
> 
> Jan
> 
>> 7. apr. 2022 kl. 07:14 skrev David Smiley <[email protected] 
>> <mailto:[email protected]>>:
>> 
>> So the next quarterly committer meeting was tentatively set by me for April 
>> 14th -- a week away now.  I've been in denial of this as I've been putting 
>> off the prospect of coordinating yet another time slot that appeals to many 
>> people around the globe.  One crude way to handle this is inertia -- it's 
>> the same time (noon US eastern) unless someone volunteers to host it at a 
>> time convenient to them?  At least this way it's not a recurring onerous 
>> issue / hurdle.  And I personally don't have an agenda but that's what 
>> crowd-sourcing is for ;-).  
>> 
>> https://cwiki.apache.org/confluence/display/SOLR/2022-04+Meeting+notes 
>> <https://cwiki.apache.org/confluence/display/SOLR/2022-04+Meeting+notes>
>> 
>> The meeting can be a good sounding board for socializing new things you are 
>> working on or for discussing pain points.  And of course just to say "hello" 
>> :-)
>> 
>> ~ David Smiley
>> Apache Lucene/Solr Search Developer
>> http://www.linkedin.com/in/davidwsmiley 
>> <http://www.linkedin.com/in/davidwsmiley>
>> 
>> On Thu, Jan 20, 2022 at 8:21 PM David Smiley <[email protected] 
>> <mailto:[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 
>> <https://projects.apache.org/committee.html?solr>
>> 
>> ~ David Smiley
>> Apache Lucene/Solr Search Developer
>> http://www.linkedin.com/in/davidwsmiley 
>> <http://www.linkedin.com/in/davidwsmiley>

_______________________
Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
http://www.opensourceconnections.com <http://www.opensourceconnections.com/> | 
My Free/Busy <http://tinyurl.com/eric-cal>  
Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 
<https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw>
    
This e-mail and all contents, including attachments, is considered to be 
Company Confidential unless explicitly stated otherwise, regardless of whether 
attachments are marked as such.

Reply via email to