Hi Christopher,
> I am just curious if anybody has thought about, or perhaps discussed,
> the idea that the projects in the zookeeper-contrib folder should be
> in their own separate git repos?
We were discussing this a few days ago:
https://github.com/apache/zookeeper/pull/1068#issuecomment-607160440
My (only) concern was that I wouldn't want to see contribs *even more*
abandoned than they are now:
>> While I wouldn't be opposed to moving "unpopular" bindings to their
>> own repository, it would probably only make sense to do so if merge
>> rules are somewhat relaxed—as I suspect it would otherwise be even
>> more difficult to meet the "two PMC approvals" threshold.
But whatever the outcome is:
>> In any case: I am willing to be automatically marked as a reviewer
>> for (at least) the zkperl and zkpython "contribs." Do we have such a
>> mechanism? I see that GitHub implements some such mechanisms (1, 2),
>> but I'm not sure how applicable they are to our case. Never hesitate
>> to ping me manually!
> I'm asking because I've been looking a lot at the build, trying to
> find ways to improve it, and I think this might be a nice improvement
> to streamline the core ZooKeeper build. This can help side-projects
> succeed or fail on their own merits, rather than be bound to the core
> project so tightly, and it could make it easier for contributors to
> know where to contribute, by making each independent component smaller
> and easier to navigate through the code.
Mostly agree—except that I would subsitute "popularity" for "merits."
(Which may or may not change the conclusion.)
Cheers, -D
