I am a bit biased because i am using trac and there are a lot plugins for trac: * http://trac-hacks.org/ - vote plugin(s) - code review plugin - xmlrpc interface so you can use external scripts - ...
I have read some pages and this also used for codereviews: * http://www.reviewboard.org/ * http://www.chipx86.com/blog/2007/05/17/review-board-making-code-reviews-awesome/ I have done some searches and found something new that looks promising: * http://pinaxproject.com/ * http://pinaxproject.com/docs/0.7/customization.html On 13 dec 2010, at 20:17, Carolyn Rowland wrote: > > Community, > > So we have a list of suggestions to Mark. Some of these were "here's > what I use" without much explanation: > > - github (https://github.com/cfengine - Aleksey's site) > +github wikis (example: https://github.com/mojombo/jekyll/wiki) > (does the addition of a wiki and gitpages negate the issues > people have posted, including Mark?) > - foswiki (http://foswiki.org/) - (the fork of twiki) > - snipplr (http://snipplr.com/) - Not hosted on cfengine.org, > requires coding by Mark & Co.-- not ideal to reinvent the wheel > - svn/ViewVC (http://www.viewvc.org/) > - svn/websvn (http://www.websvn.info/) > - docuwiki (www.docuwiki.org/) > - Trac (trac.edgewall.org/) > - Redmine (http://www.redmine.org/) - Project management/ticketing > - svn/homegrown (Mark and friends write something) > > Some questions for us: > Do we really need another wiki (foswiki[1], docuwiki, etc.)? > - Maybe we need a better wiki? > > Do we really want Mark to assess all of these solutions and pick one? > > Do we agree with Mark's list of wants (see "Mark's list" below)? > - Is that what the community wants/needs? If we leave it > to Mark and then are not satisfied... well you can finish > the sentence. > - Are we missing anything? > - Is there a priority to the list? > > As for tools and sites, are there community sites that really work for > you, that provide some or all of the functionality we are looking for > here? > > So, where do we go from here? Is it now up to Mark to fix everything > and make it right for us? > > We can look to Mark for direction, but ultimately it is the community > that will use the solution. Mark is offering guidance but I think > he seriously wants to know what we think not only about tools but about > the requirements. > > It seems like someone has run across these requirements. We cannot be > the first. Our solution may be out there, already implemented... > somewhere. Finding it might be the trick (release the hounds!). > > > Mark's list: > 0. A flat, management free interface > 1. Version control on code with comments (like svn) that track changes > so everyone can see > 2. The ability for people to add comments and even vote > 3. The ability to scan everything and build a knowledge base around it, > highlight syntax and link to the manuals > 4. A simple easy to read interface > > I second Mark's suggestion of taking the time to get it right. If we > rush into anything now, we'll have to back out of it to go to the > better solution. > > Carolyn > > [1] I would avoid twiki and use foswiki as another poster indicated. > Active development is happening in foswiki. > > > > On Mon, Dec 13, 2010 at 05:45:42PM +0100, no-re...@cfengine.com wrote: >> Forum: Cfengine Help >> Subject: Re: Once more unto the code bridge: repository >> Author: mark >> Link to topic: https://cfengine.com/forum/read.php?3,19721,19759#msg-19759 >> >> Cfengine is all about Knowledge Management these days, which is what this is >> about. It is an exciting project. >> >> I am motivated to try an experiment in the new year to make a simple system >> around svn and friends. We don't have to rush this. Better to take a little >> longer and get it right, if we have something temporary for the here and >> now. >> >> I am thinking about this as I am listening to all the comments (and I am >> listening even when I am not replying). The more everyone discusses this, >> the more inspired we'll all be methinks (waxing lyrically with a second >> shakespearian reference...). >> I appreciate the feedback about twiki and github etc. It helps me to assess >> these things without having the time to explore too much myself. >> >> _______________________________________________ >> Help-cfengine mailing list >> Help-cfengine@cfengine.org >> https://cfengine.org/mailman/listinfo/help-cfengine > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine -- Bas van der Vlies b...@sara.nl _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
