> On Jan 20, 2010, at 04:39:18, Samuli Seppänen wrote: > > >> Hi all, >> >> I dug a little deeper into Trac and to Redmine, which was another >> candidate for the (developer) site. I took a look at Git support which >> we need (if we need to start using Git later on). Trac has had some >> _serious_ performance problems when using the GitPlugin to browse Git >> repositories. These problems are apparently due to the architecture of >> the GitPlugin. It seems they have not yet been fixed. However, one "fix" >> may be to integrate GitWeb with Trac using the GitWebPlugin. Redmine, on >> the other hand, seems to support Git better, but has it's share of minor >> Git problems, too. Also, Redmine does not yet seem to support multiple >> Git branches without dirty hacks. Trac has a very wide array of actively >> developed plugins available. Redmine has quite a few, but not as many as >> Trac. Trac was also the clear favorite among everyone in the community >> site meeting. We also have in-house expertise with Trac and Python, >> which makes it easier for us to deploy and maintain. >> >> I've used both Trac and Redmine, and I think the main advantage of >> Redmine is better support for multiple projects. As the links Peter >> provided show there are several ways to host multiple projects using >> Trac. None of these are 100% solutions, but I'd put them in the "good >> enough" category. Also, better support for multiple projects should be >> coming in next release (0.12). It's not clear, however, when that >> release will be made (see http://trac.edgewall.org/roadmap). >> >> I suggest we choose Trac for our developer site. I think we should still >> have a simpler, less development-oriented site for casual users and for >> general, non-developer content (wiki, forums, etc.). I think both Trac >> and Redmine sites feel too developer-oriented, no matter how much the >> themes are customized. What do you think? >> > > As I suggested during the IRC meetings, there is not yet a need for git and > the features of git, or another VCS, as SVN is meeting the current needs. I > think the developer community would not be 'upset' by a change later if it > was deemed appropriate, and so a lot of time is unnecessarily being wasted on > researching this. > > Until SVN is failing the organization, just keep using it. > --- > Eric Crist > We agreed in the meeting that having _support_ for Git was important because we _may_ need it. Therefore it would be unwise to blindly select an application (say, Trac) without checking if Git is supported - at least on some level. I don't think the ~1 hour I spent verifying this was wasted time. Also, nobody is moving to Git, but we need to be able to do it, if necessary.
Agreed? -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
