Hooray for Collaboa! =================== Collaboa is a sort of project tracker, mainly for developers using Subversion. It currently has a neat changeset and repository browser, as well as issue management through a simple to use ticketing system. Currently, the following features are available: * Repository browsing * Changeset viewer * Issue tracking * Milestone management Some features planned for future releases are: * Continuous integration of tests/builds For the Subversion specific features it uses the Ruby SWIG bindings included in Subversion 1.2.0 and up, which are wrapped in a library called ActionSubversion. Perhaps this wrapper library will one day be extracted enough to be useful for other people... See it live and download it ========================== It can be seen live and in action right here: http://dev.collaboa.org Since Collaboa is used to manage Collaboa the above is also the place to submit bug reports or patches. Downloads and other information can be found here: http://collaboa.org README is here: http://dev.collaboa.org/repository/file/trunk/README A little background... =====================I started working on Collaboa because I continued to be annoyed by some things in a certain Python based bugtracker. Now, as I''m sure you all can figure out when you look at Collaboa there was a few things I liked about that product. But in the end, the missing features and the small annoyances eventually led me into developing Collaboa. And to be honest I''m having a blast; sometimes "reinventing the wheel" can be both fun and useful. Cheers, Johan -- http://johansorensen.com http://theexciter.com
Awesome! Haven''t had the time to give it a real stress test yet, but it looks very promising. I''ve got the feeling that I''ll be ditching a certain Python based project management tool very, very soon :) //samuel 30 jun 2005 kl. 11.11 skrev Johan Sörensen:> Hooray for Collaboa! > ===================> > Collaboa is a sort of project tracker, mainly for developers using > Subversion. It currently has > a neat changeset and repository browser, as well as issue management > through a simple to use ticketing system. > > Currently, the following features are available: > * Repository browsing > * Changeset viewer > * Issue tracking > * Milestone management > > Some features planned for future releases are: > * Continuous integration of tests/builds > > For the Subversion specific features it uses the Ruby SWIG bindings > included in Subversion 1.2.0 and up, which are wrapped in a library > called ActionSubversion. Perhaps this wrapper library will one day be > extracted enough to be useful for other people... > > See it live and download it > ==========================> > It can be seen live and in action right here: http://dev.collaboa.org > Since Collaboa is used to manage Collaboa the above is also the place > to submit bug reports or patches. > > Downloads and other information can be found here: http://collaboa.org > README is here: http://dev.collaboa.org/repository/file/trunk/README > > A little background... > =====================> I started working on Collaboa because I continued to be annoyed by > some things in a certain Python based bugtracker. Now, as I''m sure you > all can figure out when you look at Collaboa there was a few things I > liked about that product. But in the end, the missing features and the > small annoyances eventually led me into developing Collaboa. And to be > honest I''m having a blast; sometimes "reinventing the wheel" can be > both fun and useful. > > > Cheers, > Johan > > -- > http://johansorensen.com > http://theexciter.com > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >_______________________ Samuel Kvarnbrink mail: samuel.kvarnbrink-SiIintg/mUyhy6ZWzZ/+Cw@public.gmane.org blog: http://samuelk.info "I once had a problem. I thought: "Oh, I know: I''ll just use XML!" Now I had two problems."
Looks promising! Good work! Flurin Johan Sörensen wrote:>Hooray for Collaboa! >===================> >Collaboa is a sort of project tracker, mainly for developers using >Subversion. It currently has >a neat changeset and repository browser, as well as issue management >through a simple to use ticketing system. > >Currently, the following features are available: >* Repository browsing >* Changeset viewer >* Issue tracking >* Milestone management > >Some features planned for future releases are: >* Continuous integration of tests/builds > >For the Subversion specific features it uses the Ruby SWIG bindings >included in Subversion 1.2.0 and up, which are wrapped in a library >called ActionSubversion. Perhaps this wrapper library will one day be >extracted enough to be useful for other people... > >See it live and download it >==========================> >It can be seen live and in action right here: http://dev.collaboa.org >Since Collaboa is used to manage Collaboa the above is also the place >to submit bug reports or patches. > >Downloads and other information can be found here: http://collaboa.org >README is here: http://dev.collaboa.org/repository/file/trunk/README > >A little background... >=====================>I started working on Collaboa because I continued to be annoyed by >some things in a certain Python based bugtracker. Now, as I''m sure you >all can figure out when you look at Collaboa there was a few things I >liked about that product. But in the end, the missing features and the >small annoyances eventually led me into developing Collaboa. And to be >honest I''m having a blast; sometimes "reinventing the wheel" can be >both fun and useful. > > >Cheers, >Johan > > >
On 6/30/05, Johan Sörensen <johans-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Collaboa is a sort of project tracker, mainly for developers using > Subversion. It currently has > a neat changeset and repository browser, as well as issue management > through a simple to use ticketing system.Very nice. -- Regards, John Wilger ----------- Alice came to a fork in the road. "Which road do I take?" she asked. "Where do you want to go?" responded the Cheshire cat. "I don''t know," Alice answered. "Then," said the cat, "it doesn''t matter." - Lewis Carrol, Alice in Wonderland
Johan, As one of the developers of Trac (<http://trac.edgewall.com/>), the "certain Python based bugtracker" that you mention, I would like to congratulate you the initial public release of Collaboa. Competition to Trac will only serve to spur on innovation in this niche. I look forward to the time when Collaboa is ready to innovate rather than shamelessly borrowing ideas and user interface from existing software. For a brief comparison of the similarities between Collaboa and Trac I''ve prepared a short writeup at <http://bdash.net.nz/2005/07/01/ collaboa-rips-off-trac-with-a-smile/>. Regards, A slightly annoyed Mark Rowe <http://bdash.net.nz/> PS: The above opinions are mine alone, and do not necessarily reflect those of the rest of the Trac development team. On 30/06/2005, at 21:11 , Johan Sörensen wrote:> A little background... > =====================> I started working on Collaboa because I continued to be annoyed by > some things in a certain Python based bugtracker. Now, as I''m sure you > all can figure out when you look at Collaboa there was a few things I > liked about that product. But in the end, the missing features and the > small annoyances eventually led me into developing Collaboa. And to be > honest I''m having a blast; sometimes "reinventing the wheel" can be > both fun and useful.
After reading your comments and Johan''s response, I think you''re overreacting (which, given that trac has been your baby for so long, you''re entitled to do). First of all, as Johan aptly pointed out, both projects are open source. A very common occurrence in the open source community is for somebody to like a project but not like some of its features and consequently fork it and modify it. Second of all, I don''t think the interface is that much of a ripoff. And where it is a ripoff, I think that is because he likes Trac for some things but not for others. He doesn''t want to change the things that work well. However, I do believe that Johan should have added the Trac team to his acknowledgements. Without their groundbreaking work nobody would have known what it was they wanted to improve. Carl On 6/30/05, Mark Rowe <rubyonrails.org-QNL+kH6D+s+9koe0gwxAeg@public.gmane.org> wrote:> > Johan, > > As one of the developers of Trac (<http://trac.edgewall.com/>), the > "certain Python based bugtracker" that you mention, I would like to > congratulate you the initial public release of Collaboa. Competition > to Trac will only serve to spur on innovation in this niche. I look > forward to the time when Collaboa is ready to innovate rather than > shamelessly borrowing ideas and user interface from existing software. > > For a brief comparison of the similarities between Collaboa and Trac > I''ve prepared a short writeup at <http://bdash.net.nz/2005/07/01/ > collaboa-rips-off-trac-with-a-smile/>. > > Regards, > > A slightly annoyed Mark Rowe > <http://bdash.net.nz/> > > PS: The above opinions are mine alone, and do not necessarily reflect > those of the rest of the Trac development team. > > On 30/06/2005, at 21:11 , Johan Sörensen wrote: > > > A little background... > > =====================> > I started working on Collaboa because I continued to be annoyed by > > some things in a certain Python based bugtracker. Now, as I''m sure you > > all can figure out when you look at Collaboa there was a few things I > > liked about that product. But in the end, the missing features and the > > small annoyances eventually led me into developing Collaboa. And to be > > honest I''m having a blast; sometimes "reinventing the wheel" can be > > both fun and useful._______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
On 6/30/05, Mark Rowe <rubyonrails.org-QNL+kH6D+s+9koe0gwxAeg@public.gmane.org> wrote:> For a brief comparison of the similarities between Collaboa and Trac > I''ve prepared a short writeup at <http://bdash.net.nz/2005/07/01/ > collaboa-rips-off-trac-with-a-smile/>.Hi Mark (and everyone else thinking about this), While Mark and me had a good talk on irc about this stuff I''d just like to point out to everyone else that I have huge respect for Trac and that, yes, Collaboa is heavily influenced by it, and at its current status perhaps even too heavily. Trac showed the world how nicely bug and version tracking should be done. But in the long run I want to Collaboa to take off in a different direction. Integration with CIA being one thing. Collaboa will never have a wiki is another. Hopefully there will be a place for both in the world, I''d still recommend Trac in certain situations. especially if an integrated wiki is wanted... Cheers, Johan
On 1/07/2005, at 02:59 , Carl Youngblood wrote:> After reading your comments and Johan''s response, I think you''re > overreacting (which, given that trac has been your baby for so > long, you''re > entitled to do). > > First of all, as Johan aptly pointed out, both projects are open > source. A > very common occurrence in the open source community is for somebody > to like > a project but not like some of its features and consequently fork > it and > modify it. > > Second of all, I don''t think the interface is that much of a > ripoff. And > where it is a ripoff, I think that is because he likes Trac for > some things > but not for others. He doesn''t want to change the things that work > well. > > However, I do believe that Johan should have added the Trac team to > his > acknowledgements. Without their groundbreaking work nobody would > have known > what it was they wanted to improve.*nods* As Johan mentioned in his follow-up email we discussed this briefly over IRC. My initial frustration was due to interpreting the wording of his announcement email as going out of it''s way to not mention Trac. He clarified that was intended in a tounge-in-cheek fashion. With that in mind, I agree that I overreacted. I would like to add that I was being sincere when I said that I like where Collaboa is headed and the direction that Johan intends to take it. Regards, Mark Rowe <http://bdash.net.nz/>
Johan Sörensen wrote:>Hi Mark (and everyone else thinking about this), > >While Mark and me had a good talk on irc about this stuff I''d just >like to point out to everyone else that I have huge respect for Trac >and that, yes, Collaboa is heavily influenced by it, and at its >current status perhaps even too heavily. Trac showed the world how >nicely bug and version tracking should be done. But in the long run I >want to Collaboa to take off in a different direction. Integration >with CIA being one thing. Collaboa will never have a wiki is another. > > >We don''t currently run sub-version, otherwise we would probably be using Trac now. When I heard about a Rails version of Trac I was quite interested, because I would be more willing to work on it then. But why no wiki EVER? This is a MAJOR attraction for me to Trac. Steve Tuckner
> -----Original Message----- > From: rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > [mailto:rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org] On Behalf Of stevetuckner > Sent: Thursday, June 30, 2005 10:34 AM > To: Johan Sörensen; rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > Subject: Re: [Rails] [ANN] Collaboa 0.5 > > We don''t currently run sub-version, otherwise we would > probably be using Trac now. When I heard about a Rails > version of Trac I was quite interested, because I would be > more willing to work on it then. But why no wiki EVER? This > is a MAJOR attraction for me to Trac. >Why not just use one of the existing Wiki engines? Most of them are much powerful and flexible than what''s built into Trac. As long as the tracking system is web-based, providing direct links from your wiki is trivial. We call our issues SCRs (software change requests), so in our wiki we simply enter SCR:xxxx and it''s turned into a direct link to the web page for that scr #. Having the bug tracking software contain an embedded wiki engine is entirely unnecessary and frankly, I''d prefer if it didn''t have one at all.
Bennett, Patrick wrote:> > > > >>-----Original Message----- >>From: rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >>[mailto:rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org] On Behalf Of stevetuckner >>Sent: Thursday, June 30, 2005 10:34 AM >>To: Johan Sörensen; rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >>Subject: Re: [Rails] [ANN] Collaboa 0.5 >> >>We don''t currently run sub-version, otherwise we would >>probably be using Trac now. When I heard about a Rails >>version of Trac I was quite interested, because I would be >>more willing to work on it then. But why no wiki EVER? This >>is a MAJOR attraction for me to Trac. >> >> >> > >Why not just use one of the existing Wiki engines? Most of them are much powerful and flexible than what''s built into Trac. >As long as the tracking system is web-based, providing direct links from your wiki is trivial. We call our issues SCRs (software change requests), so in our wiki we simply enter SCR:xxxx and it''s turned into a direct link to the web page for that scr #. Having the bug tracking software contain an embedded wiki engine is entirely unnecessary and frankly, I''d prefer if it didn''t have one at all. > > >As long as Colabra allows you to embed links to the wiki pages in its comment sections (say by using rdoc or textile, etc), then I don''t see why that couldn''t work. Steve Tuckner>_______________________________________________ >Rails mailing list >Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >http://lists.rubyonrails.org/mailman/listinfo/rails > > >_______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
I agree that no wiki is good. If the tool fulfills its function properly there should not be a need for a wiki. Things that are relevant to the purpose--changesets, commentary on these changesets, bug tracking, commentary on these bugs--will all be contained in other areas of the interface, and having a wiki where stuff can be discussed without being connected with the tickets and changesets with which it is connected would be counterproductive. Like he said, those who have a need can still add their own wiki. Carl On 6/30/05, Bennett, Patrick <Patrick.Bennett-Gh8QaqyRIws@public.gmane.org> wrote:> > > > > -----Original Message----- > > From: rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > > [mailto:rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org] On Behalf Of stevetuckner > > Sent: Thursday, June 30, 2005 10:34 AM > > To: Johan Sörensen; rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > > Subject: Re: [Rails] [ANN] Collaboa 0.5 > > > > We don''t currently run sub-version, otherwise we would > > probably be using Trac now. When I heard about a Rails > > version of Trac I was quite interested, because I would be > > more willing to work on it then. But why no wiki EVER? This > > is a MAJOR attraction for me to Trac. > > > > Why not just use one of the existing Wiki engines? Most of them are much > powerful and flexible than what''s built into Trac. > As long as the tracking system is web-based, providing direct links from > your wiki is trivial. We call our issues SCRs (software change requests), so > in our wiki we simply enter SCR:xxxx and it''s turned into a direct link to > the web page for that scr #. Having the bug tracking software contain an > embedded wiki engine is entirely unnecessary and frankly, I''d prefer if it > didn''t have one at all. >_______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
On 6/30/05, Bennett, Patrick <Patrick.Bennett-Gh8QaqyRIws@public.gmane.org> wrote:> > But why no wiki EVER? This > > is a MAJOR attraction for me to Trac. > > > > Why not just use one of the existing Wiki engines? Most of them are much powerful and flexible than what''s built into Trac.I''m afraid I have to agree here, while being able to link back and forth between changesets, tickets and so on is neat and can, if used correctly, create a good synergy for the development and documentation. But to be honest I don''t really think a wiki belongs together directly with something related to the sourcecode repository. Tickets/bugreports do, since they relate directly to the code. Continuous integration of builds belongs there, since it directly tests the code. Milestones sort of belongs there, but I''m starting to debate with myself whether I really want/need them..? Of course, you could say a wiki belongs there as well, since you can discuss and "document" the code etc, but I really think there''s better tools/wikis out there for this sort of thing... -johan -- http://johansorensen.com http://theexciter.com