Toby being the main developer behind vault also spent a significant
time to
decouple the whole ‚frontend‘ & communication part from packagemanager
&
the vault plugin when contributing.
The file slingpackager/cmds/package.js is doing exactly the same as
filevault-package-maven-plugin that lives in Jackrabbit. Following that
argument we would have to split slingpackager into two packages.
Also I would argue that the communication=http part is trivial, it's
really
that package building part that will need some work after the
contribution
(e.g. if we wanted to get it in par with what the Java version can do).
But there is no perfect world and most other people seem to be in favour
to
host it here, so let's go ahead with it then.
-Georg
On 2019-08-27 19:42, Dominik Süß wrote:
Hi all ,
Being a fresh committee to Jackrabbit I certainly can’t speak for the
rest
but historically we seperated out as much as possible concerning the
http
communication.
Toby being the main developer behind vault also spent a significant
time to
decouple the whole ‚frontend‘ & communication part from packagemanager
&
the vault plugin when contributing.
Also the release scheme and cross dependencies wouldn’t be a good fit -
Sling is IMVHO the right home for this and if the contribution comes
with
the commitment to maintain I see no real reasons to reject it.
Contributions in contrib are anyhow rather like in the incubator and
time
will tell if it’s a useful tool with interest beyond the contributor or
not.
Cheers
Dominik
Robert Munteanu <romb...@apache.org> schrieb am Di. 27. Aug. 2019 um
17:00:
Hi Konrad,
On Tue, 2019-08-27 at 14:55 +0200, Konrad Windszus wrote:
> For me the situation looks a bit slightly different: I raised a
> concern in
>
https://lists.apache.org/thread.html/7699b02a090d0397d661721f47a6d70b72fb83ff372fafb7d45e6f5e@%3Cdev.sling.apache.org%3E
> <https://lists.apache.org/thread.html/7699b02a090d0397d661721f47a6d7
> 0b72fb83ff372fafb7d45e6f5e@%3Cdev.sling.apache.org%3E> and Ruben
> answered and I unfortunately never really followed-up on that one.
> Still for me we haven't really reached consensus back then. I was
> rather a bit surprised that Robert started the VOTE without
> commenting on the mailing list thread first.
I did not intend to move this quicker than people expected. I thought
that the discussion settled down and there were no objections.
The way I view this is that we cannot direct a contribution to another
project. The contributors have received feedback that another project
may be better suited, and decided to submit it to Sling nonetheless.
Right now, as a project, we may either accept or reject the
contribution. If we reject it, it is their choice on whether to go to
Jackrabbit or not.
My personal opinion is that there are arguments for both Sling and
Jackrabbit hosting the contribution, but turning it down is not a good
start :-) We have experience in migrating modules cross projects, so
if
it comes to that we should be well equipped for it.
Thanks,
Robert
