Hi Alon, Could give a few concrete examples of the problems you've encountered with Trac and/or Trac developers? I've used Trac myself almost daily for ~3 years with no problems. I don't think it ever even went down during that time. Also, nobody else in the community site meetings (11th and 28th) had any noteworthy problems with Trac.
Also, we're not looking into just a bug tracker. We need a wiki, forums, file releases, bug/feature request tracker etc. Trac combines many of these into a neat package. The alternative is take a bunch of excellent but separate services and integrate (=hack) them together. This gets very ugly very soon and requires a _lot_ of work: weeks or months instead of days. If Trac really proves to be a failure as you say we can migrate away from it. It will be somewhat painful, but definitely doable. The database scheme (at least the ticket part) is relatively straightforward to export and convert to, say, Redmine. Some data will inevitably get lost, though. Samuli > Trac is *THE* worse ticketing system there is on earth. > It is almost unmaintained and even if something happens at the project > it is minor and unusable. > For example ticket dependency and duplication is unavailable for years. > > If you like to have sane system, use bugzilla. > > Yes, I know this was raised in meeting, but I think someone is going > to regret this decision. > > 2010/1/31 Samuli Seppänen <sam...@openvpn.net>: > >> Here's the summary for last Thursday's community meeting. >> >> -- >> Samuli Seppänen >> Community Manager >> OpenVPN Technologies, Inc >> >> irc freenode net: mattock >> >> >> COMMUNITY MEETING >> >> Place: #openvpn-discussion on irc.freenode.net >> Date: Thursday, 28th January 2010 >> Time: 19:00 UTC >> >> Full log available here: >> >> http://secure-computing.net/logs/%23%23openvpn-discussion.log >> >> Next meeting on Thu 4th Feb 2010. Same place, same time. >> >> SUMMARY >> >> Decided to start with a single Trac-based site for the whole community >> rather than have separate user/developer sites. The main concern was the >> risk of content getting fragmented (e.g. developer content in user wiki and >> vice versa). This means Trac will need to be themed to make it as >> approachable as possible for "normal" users (=not look too >> developer-oriented). >> >> Agreed that we need a set of documents describing how OpenVPN is developed - >> including things like common coding conventions. This should improve code >> quality as well as make the process less taxing for core developers. >> >> Agreed that the content from the new community site needs to be >> >> a) mirrored to another server (e.g. ecrist's OpenvPN community server) >> b) backed up off-site (e.g. to ecrist's server and/or OpenVPN e.V.) >> c) accessible by a community member >> >> This helps prevent data loss for any reason - political or technical. >> >> Discussed community site spam prevention in some length: >> >> * There is an anti-spam plugin for Trac (see below) >> * A proper user registration process needs to be chosen - not too >> bureaucratical but not too automated, either >> * Forum posts could be automatically accepted only after the first few have >> been accepted manually by the admin(s) >> >> Discussed which forum software to use. PhpBB is apparently the best OSS >> solution out there. >> >> Discussed potentially useful Trac plugins: >> >> * http://trac.edgewall.org/wiki/PluginList >> * http://trac-hacks.org/ >> * http://trac-hacks.org/wiki/DiscussionPlugin (for forums, probably not as >> good as phpBB and such) >> * http://trac.edgewall.org/wiki/SpamFilter (spma filtering) >> * http://trac-hacks.org/wiki/TicketImportPlugin (for importing SF.net >> tickets) >> * http://trac-hacks.org/wiki/TracBuildbotIntegration (for automated building >> and regression testing with buildbot) >> * http://trac-hacks.org/wiki/MediaWikiPluginMacro (mediawiki syntax for Trac) >> * http://trac-hacks.org/wiki/TocMacro (automated Table of contents creation) >> * http://trac-hacks.org/wiki/DownloadsPlugin (downloads through Trac, e.g. >> for file releases) >> * http://trac-hacks.org/wiki/DefaultCcPlugin (a default CC for tickets, e.g. >> inform James or devel-list) >> * http://trac-hacks.org/wiki/IrcAnnouncerPlugin (Trac makes announcements of >> changes to IRC) >> * http://trac-hacks.org/wiki/IrcLogsPlugin (IRC logs to Trac) >> >> Also discussed IRC<->Trac integration using Trac's built-in RSS support. >> >> ------------------------------------------------------------------------------ >> The Planet: dedicated and managed hosting, cloud storage, colocation >> Stay online with enterprise data centers and the best network in the business >> Choose flexible plans and management services without long-term contracts >> Personal 24x7 support from experience hosting pros just a phone call away. >> http://p.sf.net/sfu/theplanet-com >> _______________________________________________ >> Openvpn-devel mailing list >> Openvpn-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/openvpn-devel >> >> >>
