Re: [Trac] sell Guido on Trac

2006-03-28 Thread alexander . buccino
First off, let me say that I love Trac.  It's been a huge help to my 
development group.  However, I'm not sure I would want to make the 
argument of Trac over Roundup.  I've been a big fan of Roundup since way 
back, and I would love to see it get the kind of momentum that you mention 
Trac having.  Roundup has always had some great ideas and I think it has 
some powerful features that would be really useful for OSS development.

I think Roundup's strongest points are:
--email notification, especially the nosy list
  I find that Trac's email notification never works quite the way I want 
it to.  Either I turn on the always_notify_x switches and get too many 
emails or I turn it off and get too few.  Roundup's nosy list concept is 
simple, intuitive, and very powerful.  I'd love to see it implemented in 
Trac.
--generic object model
  Roundup's flexibility in creating new object types with states and 
interlinking is very nice.  I've seen the Trac Object Model Proposal and 
it looks like an attempt to implement a similar idea for Trac, which would 
be great. http://projects.edgewall.com/trac/wiki/TracObjectModelProposal
--Easy setup
  While this wouldn't be an issue in this instance, Roundup is no problem 
to install and get running while Trac can be an absolute nightmare with 
all of its dependencies.

Trac's strongest points in comparison to Roundup are:
--Much more polished look-and-feel
  It looks and works great out of the box (assuming you can actually get 
all its dependencies installed).
--Tight integration (subversion, wiki, ticketing)
--Clean plugin model for extension

I think that both are very well designed, but I'd love to see Roundup get 
the kind of attention that Trac has gotten and see where Roundup goes.

Alex Buccino






Chris Ryland [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
03/28/2006 12:43 PM
Please respond to trac
 
To: trac@lists.edgewall.com
cc: 
Subject:[Trac] sell Guido on Trac


I'm (privately, via email) trying to sell Guido (Python BDFL) on the 
use of Trac vs. Roundup for future Python development (e.g., Python 
3000).

How would I make the case to him?

The main advantage I would see in Trac is it's excellent Subversion 
integration, which is not really built-in to RoundUp, plus Trac's 
much greater momentum in the OSS worlds.

Cheers!
--Chris Ryland / Em Software, Inc. / www.emsoftware.com


___
Trac mailing list
Trac@lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac



___
Trac mailing list
Trac@lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac


Re: [Trac] sell Guido on Trac

2006-03-28 Thread Chris Ryland

Excellent response!

Yes, I'd love to see RoundUp's 'nosy' feature make it into Trac as well.

On Mar 28, 2006, at 1:08 PM, [EMAIL PROTECTED] wrote:


First off, let me say that I love Trac.  It's been a huge help to my
development group.  However, I'm not sure I would want to make the
argument of Trac over Roundup.  I've been a big fan of Roundup  
since way
back, and I would love to see it get the kind of momentum that you  
mention
Trac having.  Roundup has always had some great ideas and I think  
it has
some powerful features that would be really useful for OSS  
development.


I think Roundup's strongest points are:
--email notification, especially the nosy list
  I find that Trac's email notification never works quite the way I  
want
it to.  Either I turn on the always_notify_x switches and get too  
many
emails or I turn it off and get too few.  Roundup's nosy list  
concept is
simple, intuitive, and very powerful.  I'd love to see it  
implemented in

Trac.
--generic object model
  Roundup's flexibility in creating new object types with states and
interlinking is very nice.  I've seen the Trac Object Model  
Proposal and
it looks like an attempt to implement a similar idea for Trac,  
which would
be great. http://projects.edgewall.com/trac/wiki/ 
TracObjectModelProposal

--Easy setup
  While this wouldn't be an issue in this instance, Roundup is no  
problem
to install and get running while Trac can be an absolute nightmare  
with

all of its dependencies.

Trac's strongest points in comparison to Roundup are:
--Much more polished look-and-feel
  It looks and works great out of the box (assuming you can  
actually get

all its dependencies installed).
--Tight integration (subversion, wiki, ticketing)
--Clean plugin model for extension

I think that both are very well designed, but I'd love to see  
Roundup get

the kind of attention that Trac has gotten and see where Roundup goes.

Alex Buccino






Chris Ryland [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
03/28/2006 12:43 PM
Please respond to trac

To: trac@lists.edgewall.com
cc:
Subject:[Trac] sell Guido on Trac


I'm (privately, via email) trying to sell Guido (Python BDFL) on the
use of Trac vs. Roundup for future Python development (e.g., Python
3000).

How would I make the case to him?

The main advantage I would see in Trac is it's excellent Subversion
integration, which is not really built-in to RoundUp, plus Trac's
much greater momentum in the OSS worlds.

Cheers!
--Chris Ryland / Em Software, Inc. / www.emsoftware.com


___
Trac mailing list
Trac@lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac



___
Trac mailing list
Trac@lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac




Cheers!
--Chris Ryland / Em Software, Inc. / www.emsoftware.com


___
Trac mailing list
Trac@lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac