incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kalle Korhonen <>
Subject Re: Q. Forks without concensus?; A. anytime / depends / never without agreement
Date Tue, 03 Jan 2012 20:59:33 GMT
On Tue, Jan 3, 2012 at 10:33 AM, Greg Stein <> wrote:
> On Jan 3, 2012 1:28 PM, "Kalle Korhonen" <> wrote:
>> On Tue, Jan 3, 2012 at 9:57 AM, Leo Simons <> wrote:
>> > So the generic policy is there is no generic policy, and instead there
>> > is appropriate application of judgement to specific cases.
>> Generic policy doesn't mean you couldn't use judgement or make
>> exceptions. In principle, if the ASF's mission is to build communities
>> around source code, we should not accept forks of open source projects
>> if that's not the (consensus) will of the original community.
> And what happens when the arriving community has a different vision than
> the original community? Do you tell them to go pound sand? Tell them the
> two communities are not allowed to diverge or separate?

You tell the arriving community that you need to work with the
original community and that forking an existing open source project
with an existing community is your last option, not your first one. I
think it's just plain common sense that you have to be respectful of
others, just like in the real world. Specifically regarding
Bloodhound, much of the issues would likely have been avoided if the
proposal hadn't dismissed the original community and hadn't stated as
its primary intention to fork the existing Trac project (see quotes
below). If the stated goal had been to provide a packager and
installers and work closely with the existing community, I bet the
tone of all stakeholders would have been very different.


>From the proposal:

"By it's own recognition, however, the development community
surrounding Trac has largely dissipated."

"As discussed earlier, the current Trac development community is small
and reluctant to accept outside contributions."

"Given the Foundation’s
reputation for building and maintaining communities, we feel a new
project, based on Trac but incubated under the Apache umbrella, would
help re-build the developer community, jump started by developer time
donated by WANdisco."

"The initial goals for Bloodhound primarily revolve around migrating
the existing code base and integrating external features to make the
project easy to deploy."

"Some of the initial goals include:
 * Migrate the existing BSD-licensed Trac code base to the ASF."

> Cheers,
> -g

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message