On Tue, Dec 1, 2015 at 2:02 AM, Bertrand Delacretaz <bdelacre...@apache.org> wrote:
> Hi Owen, > > On Mon, Nov 30, 2015 at 5:55 PM, Owen O'Malley <omal...@apache.org> wrote: > > ...The > > condensed version is that the original code base (OpenSOC) was created > by a > > company (Cisco) that put it on github as ALv2, but then hasn't been > working > > on it. We posted a message > > < > https://groups.google.com/d/msg/opensoc-support/rFlW2uSSvmU/Sw_cO-T2AAAJ> > > to the OpenSOC support group a month ago proposing a move to Apache and > got > > a single positive response... > > The response I see there ("this is great news - looking forward to > working with you") does not look to me like approval from whoever owns > that code to move it to the ASF. > The point was that the community around OpenSOC is unresponsive. If there was an active community, it would generate more than a single response after a month. Cisco threw the code over the wall, but doesn't seem to be investing in it. > What's needed IMO is approval from whoever owns the code that's at > https://github.com/OpenSOC/opensoc . As usual, although the license of > that code would allow us to fork, we only accept voluntary > contributions. > My point is that Apache's self-imposed rule is not to do hostile forks, because we want to play nicely with other open source projects. That rule keeps us out of a lot of trouble and avoids bad feelings. I've heard it expressed as "Apache doesn't fork communities," which I think ties nicely with "Community over code." To avoid forking communities, you need to either have: * the community wants to move to Apache * the community is dead or inactive There is a pretty compelling evidence that OpenSOC is currently inactive. .. Owen > > -Bertrand > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
