On Nov 15, 2007 5:40 AM, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote: > So I set up Trac: > > http://trac.enlightenment.org/e > > As per the news: > > http://www.enlightenment.org/p.php?p=news/show&l=en&news_id=6 > > it's intended for project tracking. tracking our TODO items, etc. etc. it > seems > it's only me that likes TODO in CVS. no one else except a few core devs even > knows its there. so i am thinking that we use trac to put up the TODO items > and > file tickets for them - then we can track what is to be done, even have > discussions on each item - draw up wiki-like documents on them, find out who > is > doing them etc. etc. > > it even provides a NICE wishlist system. it's friendlier than bugzilla, but > not > as powerful.
Ok, I really like trac, but keeping both doesn't solve the previous problem of people not using bugzilla, instead it create another point of replication. I also like bugzilla completeness, but unless we'll create hierarchical bug dependencies, it doesn't worth the pain. So, let's try to eliminate one? Pro-Trac: it's simpler and provides wiki and scm view (I know git and svn works, but does cvs?) Pro-Bugzilla: it's complete, you can have hierarchical bugs and with that have todo lists. I rather keep the bugzilla + mediawiki instead of going Trac. Maybe someone could customize bugzilla's UI? -- Gustavo Sverzut Barbieri -------------------------------------- Jabber: [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] ICQ#: 17249123 Skype: gsbarbieri Mobile: +55 (81) 9927 0010 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
