Jan, Maybe you missed this thread but I noticed you just added /solr/monitoring. Please move that to the top level.
On Mon, Aug 24, 2026 at 10:58 AM Jason Gerlowski <[email protected]> wrote: > > A belated +1 from me. There's always a bit of friction with these > sort of changes (like the PR conflicts that Christos mentions), but I > think it'll ultimately be worth the trouble. > > Jason > > On Sat, Aug 1, 2026 at 3:33 AM Christos Malliaridis > <[email protected]> wrote: > > > > +1 for restructuring things, I believe it makes sense to structure > > components llogically and replace any legacy structure. > > > > The only concern I have is that moving things around can make updating PRs > > a bit difficult. But that's acceptable in my opinion. Perhaps its worth > > notifying PR authors at PR level when they are affected? > > > > Best, > > Christos > > > > On Thu, Jul 30, 2026, 01:31 David Smiley <[email protected]> wrote: > > > > > Our source repo has been only for Solr for some time now -- Lucene has > > > left. Naturally, all of our sub-projects are underneath /solr because > > > with > > > Lucene around, doing anything else wouldn't have made any sense. But I > > > don't think that makes sense anymore. I think moving some things to the > > > top level would be useful to differentiate things... like what things do > > > *not* go inside a running Solr server. For example cross-dc-manager and > > > the Solr ref guide are rather different things that both don't run in a > > > Solr server. They might ship with a Solr distribution but what we choose > > > to bundle and not is rather arbitrary. The new UI module is a gray area > > > but I'd vote outside. Packaging & distribution are both rather meta... > > > maybe outside makes more sense. > > > > > > Do others have thoughts on this? > > > > > > ~ David Smiley > > > Apache Lucene/Solr Search Developer > > > http://www.linkedin.com/in/davidwsmiley > > > > > --------------------------------------------------------------------- > 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]
