That makes sense to me I think. Each month anyone can volunteer to run things, and they can pick a time that works for their local TZ. If no one in particular has volunteered, I'm happy to host-by-default.
I'll host the first one to get things started. I'm traveling next week, but how about the following Monday (February 6th) at, say, noon ET? Jason On Thu, Jan 26, 2023 at 3:39 PM Houston Putman <[email protected]> wrote: > > This is a great idea Jason! > > As per Jan's suggestion, I think it would be great for the host to pick a > time in their time zone, so that no one feels pressured. There's enough > community members around the globe to not stick to the US > timezones religiously. > > - Houston > > On Thu, Jan 26, 2023 at 6:12 AM Eric Pugh <[email protected]> > wrote: > > > +1 Let’s do it. > > > > > On Jan 24, 2023, at 11:24 AM, David Smiley <[email protected]> wrote: > > > > > > We already have a precedent of using Confluence for meeting notes. > > Here's > > > the last one: > > > > > https://cwiki.apache.org/confluence/display/SOLR/2022-05-10+Meeting+notes > > > > > > An email that occurs per meeting would be good to remind folks that > > there's > > > about to be another meeting within a day or two, say. It should include > > a > > > link to this Confluence doc. I don't think a post-meeting email is > > > necessary, unlike the previous meetings I've done. Ideally the host > > > updates the doc to mention some topics discussed and some attendees but I > > > could understand if the new low-formality approach means this may not > > > happen. > > > > > > ~ David Smiley > > > Apache Lucene/Solr Search Developer > > > http://www.linkedin.com/in/davidwsmiley > > > > > > > > > On Tue, Jan 24, 2023 at 11:13 AM Jason Gerlowski <[email protected]> > > > wrote: > > > > > >> Awesome - sounds there's definitely some general interest. (Though the > > >> details need some hashing out.) > > >> > > >>> I'm wondering if bi-weekly is a bit ambitious? > > >> > > >> It might be. Maybe monthly is a better starting point. My hope was > > >> that making the meetings reasonably frequent would cut down on the > > >> pressure folks might feel to show up to any particular meeting. But > > >> maybe bi-weekly is ambitious to start. Let's say "monthly" then. > > >> > > >>> Who will host them all? > > >> > > >> I'm happy to volunteer, since I brought it up. In my mind that'd > > >> mostly involve (1) setting up a Zoom or Google Hangouts meeting, (2) > > >> sending a reminder email here a few days in advance with a video > > >> conferencing link, and then (3) opening up the meeting when the time > > >> comes. > > >> > > >>> Do you have experience with "no-agenda" meetings elsewhere? > > >> > > >> I guess? I've worked at a few places now where the search team holds > > >> some form of "office hours" where folks might come with some PR > > >> needing review or some question to discuss, or they might show up > > >> "empty handed" just to hang out and learn from the discussions that > > >> others are having. And, even less formally, I'd point to the sort of > > >> informal hallway conversations that we all have when we have with our > > >> coworkers at work, or others in the community at conferences. Those > > >> were the two models that I guess I had in mind. > > >> > > >> That said - I appreciate how not having an agenda to advertise in > > >> advance makes it harder for folks deciding how to use their time. If > > >> folks prefer having a loose list of topics, let's do that. If the > > >> host sends out a reminder email a few days in advance, people planning > > >> to attend could advertise their suggested topic on that thread? Or a > > >> Google sheet or Confluence or anything else would work too. No real > > >> opinion on that. > > >> > > >> Best, > > >> > > >> Jason > > >> > > >> > > >> On Tue, Jan 24, 2023 at 6:01 AM Noble Paul <[email protected]> > > wrote: > > >>> > > >>> Even if we can get together once a month, that should be great. > > >>> > > >>> Let's keep a google sheets to fill up items that we need to discuss . > > We > > >>> can just pick up the top items to discuss? > > >>> > > >>> On Tue, Jan 24, 2023 at 9:17 PM Jan Høydahl <[email protected]> > > >> wrote: > > >>> > > >>>> Kudos for the initiative. Light-weight is always good, and high > > >> frequency > > >>>> makes it more light weight.. > > >>>> > > >>>> I'm wondering if bi-weekly is a bit ambitious? Who will host them all? > > >>>> While no agenda is low-maintenance, it also makes it hard for > > community > > >>>> members to choose which meetings they want to attend if they need to > > >> pick > > >>>> just a few? Do you have experience with "no-agenda" meetings > > elsewhere? > > >>>> > > >>>> Being a large distributed community, it would also be nice to spread > > >> the > > >>>> meetings across differnet week-days and time zones. One natural way to > > >> do > > >>>> that would be to assign a host for each meeting ahead of time, and let > > >> the > > >>>> host choose a suitable time in his/her own TZ without feeling they > > >> need to > > >>>> stay up at night to be "inclusive". Or is the number of U.S. community > > >>>> members simply so large that every meeting should at least be within > > >> the > > >>>> daytime hours of both west- and east coast? > > >>>> > > >>>> Jan > > >>>> > > >>>>> 23. jan. 2023 kl. 20:29 skrev Jason Gerlowski <[email protected] > > >>> : > > >>>>> > > >>>>> What would everyone here think about having some sort of semi-regular > > >>>>> virtual "meetup" for committers/community-members? > > >>>>> > > >>>>> We've done something similar to this with the "committers meetings" > > >>>>> that've been held in the past. Those work great, but I know David > > >> has > > >>>>> said they're a lot of work to put together. I've been wondering > > >>>>> whether a more impromptu, less-organized format might support > > >>>>> interested folks meeting up more often. > > >>>>> > > >>>>> Here's a strawman suggestion to build from: let's set up a standing > > >>>>> time when folks could hop on a Google Hangout (Zoom?) every two > > >> weeks. > > >>>>> There'd be no agenda in-advance - folks could come with a question or > > >>>>> a topic in mind, or just to chat with folks they haven't seen in > > >>>>> awhile or to hear what others are working on. If the group is large > > >>>>> enough we could do breakout rooms (or something similar). > > >>>>> > > >>>>> If there's interest I'd be willing to set up a trial-run with a few > > >>>>> folks later this week, say, Thursday at 3 (ET). Or, alternately, we > > >>>>> could refine the idea for a bit and do a trial run in a few weeks. > > >>>>> Curious what folks think! > > >>>>> > > >>>>> Best, > > >>>>> > > >>>>> Jason > > >>>>> > > >>>>> --------------------------------------------------------------------- > > >>>>> To unsubscribe, e-mail: [email protected] > > >>>>> For additional commands, e-mail: [email protected] > > >>>>> > > >>>> > > >>>> > > >>>> --------------------------------------------------------------------- > > >>>> To unsubscribe, e-mail: [email protected] > > >>>> For additional commands, e-mail: [email protected] > > >>>> > > >>>> > > >>> > > >>> -- > > >>> ----------------------------------------------------- > > >>> Noble Paul > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: [email protected] > > >> For additional commands, e-mail: [email protected] > > >> > > >> > > > > _______________________ > > 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. > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
