incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roy T. Fielding" <>
Subject Re: Q. Forks without concensus?; A. anytime / depends / never without agreement
Date Sat, 07 Jan 2012 22:10:52 GMT
On Jan 7, 2012, at 1:49 PM, Greg Stein wrote:

> On Jan 7, 2012 4:24 PM, "Roy T. Fielding" <> wrote:
>> ...
>> The original developers are not ambivalent to this fork.
> Untrue. Christian and Remy are, and always have been, supportive. They were
> the ones to suggest the fork, rather than trying to make the changes in
> trunk.

I read the trac-dev mailing list.  To say that they are supportive is a huge
stretch of the imagination.  They are sadly resigned to see a potential
contributor decide to fork the code instead of working with them directly.
And the rest of the community (which is far larger than the core) thinks
the idea stinks.

> What you have is a vocal minority that disagree. Ethan is not even a core
> committer, as far as I can tell.
> Edgewall, the copyright holder, is a defunct shell. That is a primary
> reason WANdisco wanted to move to the ASF: a home with actual backing and
> longevity.

Then we should be able to convince Christian and Remy to join the initial
committers list and bring the rest of the TRAC community with them.
Why has that not been done?

>> ...
> WANdisco has definite problems in how they approach and work with open
> source communities. They discussed this stuff with the Trac principals
> privately, rather than with the broader community. But my read is that the
> Trac leads are supportive of Bloodhound.

They are supportive of people doing work on Trac.  They did not support a
fork at the ASF.  What they told WANdisco was that, rather than come to some
artificial agreement on how they should work together before WANdisco
had contributed anything, that WANdisco should fork the code and start by
making contributions.  That's it.  The only reason that Christian has not
directly opposed Bloodhound is because he believes the BSD license gives
permission to fork the code.

> My interest here is seeing Trac revitalized, improved, and delivered as an
> awesome open source issue tracker. I'm tired of Bugzilla and (non-OSS)
> Jira. I like the Google Code tracker, but I'm biased there :-P

There is no evidence to suggest that cannot be done on trac-dev.


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

View raw message