Lucene devs are always welcome, and some of the people attending work on Lucene as well. This is mostly a Solr issue though. There are two outcomes that directly affect Lucene I can think of offhand:
1> moving to the Gradle build, which irrelevant if the consensus is to treat that effort separately 2> if the consensus results in a significant delay for any 9.0 release it also directly impacts Lucene. There’s no reason additional 8x releases couldn’t be done though. So feel free to attend, I’m not sure how valuable it will be though. Maybe Lucene folks can catch up on e-mails ;) > On Nov 17, 2019, at 10:18 AM, Atri Sharma <a...@apache.org> wrote: > > Does it make sense for Lucene committers to attend? > > On Sun, 17 Nov 2019 at 20:20, Erick Erickson <erickerick...@gmail.com> wrote: > David: > > I may be able to attend, but perhaps only via keyboard. It depends on when I > get back from an appointment in time. If I don’t make it back in time, here’s > some grist for the mill. > > Can we add an item for the Gradle build effort? I’m curious what people think > about that effort and whether it’s worth pursuing and if so, how/when. Should > we make it a goal to make it the only build system for 9.0? Try to backport > for 8x? etc. So far, it’s not a big deal to keep the Gradle branch current > with master, there are _very_ few necessary code changes, it’s almost all new > code. Dawid noticed some issues where the gradle_8 branch doesn’t match > master, I’m not sure what’s going on with that. > > If some variant of my straw-man proposal below is adopted, my vote would be > to make the Gradle build 9x only assuming we go forward with it. > > ************* > > My straw-man proposal: > > If we’re going to make many of the changes the agenda outlines, we’re going > to be tearing up a lot of code. And, I very much assume, going through quite > a period of (more) instability. So I expect making changes unrelated to this > effort on both master and 8x will become increasingly difficult. Should we be > prepared to “soft freeze" 8x and bend efforts to releasing 9.0 at some point > (TBD)? I don’t think of this is a “hard freeze”, more like pretending we just > made a 9.0 release and getting increasingly selective about what we attempt > to backport. > > And thanks for organizing this! > Erick > > > On Nov 17, 2019, at 9:13 AM, David Smiley <david.w.smi...@gmail.com> wrote: > > > > The meeting will be held on Wednesday at 11am PST (2pm EST). I'll send a > > calendar invite tomorrow to those that used the Doodle poll. > > The agenda is here: > > https://cwiki.apache.org/confluence/display/SOLR/2019-11+Meeting+on+SolrCloud+and+project+health > > Edit it if you wish. If you can't (e.g. you are not a committer), then > > maybe reply here to offer a suggestion. > > > > ~ David Smiley > > Apache Lucene/Solr Search Developer > > http://www.linkedin.com/in/davidwsmiley > > > > > > On Wed, Nov 13, 2019 at 1:56 PM David Smiley <david.w.smi...@gmail.com> > > wrote: > > I am proposing a virtual "Solr committer meeting" next week to discuss the > > concerns and ideas Mark Miller has raised recently. The scope of > > conversation of this one is not the other wonderful things people are > > working on (e.g. new plugins architecture), though I would *love* to have > > future virtual committer meetings that are open-ended to discuss all manner > > of things on our minds. > > > > Why? (A) I felt the committer meeting at Activate this year was > > fantastically productive (B) I love opportunities to see/hear from my > > awesome virtual colleagues (C) Mark raised issues of grave concern to our > > community > > > > When exactly is this?: I'm using a "Doodle poll" to determine an optimal > > time slot. For the link to the poll, go to the ASF Slack, #solr-dev > > channel, and you will see it. You could also email me directly for it. > > > > For this virtual committer meeting and future ones: > > * This is in the spirit of committer meetings co-located with conferences. > > I recall that ASF policy says that no "decisions" can be made in such a > > venue. We make decisions on this dev list and indirectly via JIRA out in > > the open and with the opportunity for anyone to comment. > > * Who: Committer-only or by invitation > > * Video chat with option of audio dial-in. This time I will use Google > > Hangout. > > * Recorded for those invited only. I'll dispose of the recording a week > > after. The intention is for those who cannot be there due to a scheduling > > conflict to see/hear what was said. I have the ability to do this > > recording via Salesforce's G-Suite subscription. > > * Published notes: I (or someone) will take written meeting notes that are > > ultimately published for anyone to see (not restricted to those invited). > > They will be transmitted to the dev list. > > > > Thanks everyone. I hope we do more of these! And I hope non-committers > > don't feel slighted; the published notes is a great time to make your voice > > heard here! I'm open to suggestions. > > > > ~ David Smiley > > Apache Lucene/Solr Search Developer > > http://www.linkedin.com/in/davidwsmiley > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > > -- > Regards, > > Atri > Apache Concerted --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
