> How can we continue moving this forward?
>
> Mick/Jon/TLP folks, is there a path here where we commit the
> Netflix-provided management process, and you augment Reaper to work with it?
> Is there a way we can make a larger umbrella that's modular that can
> support either/both?
There seems a reluctance in any collaboration between Reaper and Netflix atm,
despite efforts from both sides. It worries me that there appears to be this
whole roadmap of design and implementation ready to go, and reference work to
it that we don't get to see. When we (Reaper) do have a real reference work out
in the open. This will ofc make it challenging for the Reaper folk to get
involved, it leaves us with the feeling that we're just having to re-invent the
wheel for someone else, when it would be much quicker for us to evolve Reaper
to the designs proposed.
Such collaboration between us, i reckon needs to happen first ("show, don't
tell"). So I'd throw out the idea that we start the side-car collaboration
project as an external github project. From there if we can put something
together that satisfies people's designs for a new side-car tool, and maintains
the Reaper user base and feature-list, then we've proven that the
community-spirit and trust is in place to bring it into the Cassandra project.
Also, unless we have existing PMC that we know we guardian this project we're
just presuming everyone will know all the ins and outs of ASF processes and
requirements. Maybe it's better to be practicing this stuff first, rather than
presuming it will just happen.
That's just my two cents, and an attempt at a compromise. My first vote would
still be to bring in Reaper and retro-fit it step by step (and i'd be more than
happy to accept and work on someone else's roadmap if we took this approach).
Mick
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
