Thanks Anshum. I believe this will help everyone who wish to play with
other innovative ideas
On Thu, Jan 14, 2021, 7:08 AM Anshum Gupta wrote:
> Based on the discussion on the committer meeting, I'll put in a request to
> create a solr sandbox repo.
>
> Thank you everyone.
>
> On Tue, Jan 12,
Based on the discussion on the committer meeting, I'll put in a request to
create a solr sandbox repo.
Thank you everyone.
On Tue, Jan 12, 2021 at 8:13 PM Noble Paul wrote:
> I'm +1 for a top level sandbox repo. Anyone should be able create a
> project in that.
>
> Once the project graduates
I'm +1 for a top level sandbox repo. Anyone should be able create a
project in that.
Once the project graduates out of the sandbox we should create a top level
On Wed, Jan 13, 2021, 11:30 AM Anshum Gupta wrote:
> Building this as a branch is an option, but building it outside in a
> personal
On Wed, 13 Jan, 2021, 6:00 am Anshum Gupta, wrote:
> Building this as a branch is an option, but building it outside in a
> personal repo is exactly what's not the Apache Way.
>
Negative. Nothing of that is mentioned in
https://www.apache.org/theapacheway/. Private decision making isn't
Building this as a branch is an option, but building it outside in a
personal repo is exactly what's not the Apache Way.
Code should be designed and built in the Apache world, else it'd be a
grant/donation and not really a PR. Also, you can't create a PR against a
repo that doesn't exist
I feel this is placing the cart before the horse.
We can always build this as a branch or a repo under your own account.
Once we reach a point where the project is reasonably mature, you can
create a repo and contribute it upstream.
On Wed, Jan 13, 2021 at 6:27 AM Anshum Gupta wrote:
>
> I
I understand what you are saying, which is also my reason to not have a
mono-repo. This way it's easier to manage and drop a repository when it's
not needed. It doesn't cause clutter and lives in isolation.
I think we are on the same page in terms of the intention.
On Tue, Jan 12, 2021 at 10:51
Look at the branches that are cluttering up our main repository, many
symbolic of unfinished work. If we start one repo each for everything we
hope to finish, we'll make Solr annoying in a new way.
There is no reason multiple artifacts can't be released independently from
the same repo. Why are
Thank you everyone!
I'll move forward with the cross-dc repo creation then as mentioned in the
original email :)
If we want to change the approach on the repo, we can always change that
before we release anything in the future.
On Mon, Jan 11, 2021 at 10:32 AM Mike Drob wrote:
> I'm seeing
I'm seeing valid reasons to prefer one solr sandbox repo, or prefer
multiple many repos for future plugins or integrations. In this specific
case, I think the relevant deciding points are 1) we don't have multiple
things yet, so deciding between a "mono-repo" and a "multi-repo" is not
very
(palm-to-face) -- LOL okay sorry. I'm getting my threads crossed.
A repo which holds multiple independent modules that can work with Solr
need not release them all at once.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On Sat, Jan 9, 2021 at 4:48
David, this is about the Cross DC work that was supposed to be done :-)
The independent release cadence is primarily the reason why a new repo
makes sense to me in this case.
On Sat, Jan 9, 2021 at 1:24 PM David Smiley wrote:
> While I like the idea of a single (Apache!) repo for multiple
>
While I like the idea of a single (Apache!) repo for multiple
packages/plugins, that does not apply to the Solr Operator, which isn't
even in Java. It's too unique. So I agree with Anshum & others about
creating an Apache repo for the Solr Operator.
I think the ship has sailed on the Solr
The problem with a single repository is that it will/may conflict at times.
Also, I still don't see the problem with having the extra repo as long as
we aren't releasing anything.
The problem with (b) is that you can't create a PR from a random repository
to a repo it isn't a fork of. I also
Not necessarily. Most people contribute to Apache Lucene/Solr using
external repositories (forks) and raise pull requests against Apache owned
repositories. There's no SGA needed on such occasions.
I see two paths forward from here.
a) Lets setup a single repository for all packages/plugins, say
An external repository probably ends up requiring a software grant? I know
there is a material difference between code originating externally and code
originating within the umbrella of the ASF in terms of IP, copyright, or
other legal status.
On Thu, Jan 7, 2021 at 8:11 PM Ishan Chattopadhyaya
If all we need now is a place to commit a PoC for now (and something like
sandbox repo or contribs won't suffice), why can't we have a separate
repository in GitHub outside Apache and merge into an Apache repository
only once the code takes reasonable shape?
On Fri, 8 Jan, 2021, 2:31 am Anshum
Thanks for the feedback, Mike.
I like the idea of the sandbox, but that might be restricting when we want
to work on more than one repos.
I'm not sure if that would happen in the near future, but as we can always
discard the repo and it doesn't really come at a cost, I don't see a
problem with
I'm not sure where I sit on this, going to start typing things and then
hopefully I'll reach a conclusion by the end.
This definitely needs to be outside of the core solr repo so that it can be
versioned and released independently. And I disagree with Ishan about the
consequence of abandoning the
I understand your concern, but this is the placeholder for where the code
would be, not what the code would look like.
Considering we agreed to do this in a repository outside of the core, I
believe this is a good place to start. The idea that the release cadence
for the cross-dc effort should be
-1 on this. Without finalizing on the shape of how the solution will look
like, I don't think we should start a repository: it would be bad if we
have to abandon the repository of our approach changes (say we want to keep
it tightly integrated inside Solr).
On Thu, 7 Jan, 2021, 11:45 pm Anshum
21 matches
Mail list logo
