From: Burkhard S. <Bur...@fu...> - 2012-12-17 08:23:09
|
Hi everybody, even without knowing the alternatives from my own experience, I would nevertheless favor the SourceForge internal tracker (ticket system). Even though it may not be the most flexible system, it will always have the advantage of being embedded in the Allura interface and thus being able to link most directly to the other Allura tools such as the Wiki, the code (svn, git,hg) tools etc ... Why making things more complicated than necessary? Best regards from Berlin Burkhard On 16.12.2012 22:18, Ulf Lorenz wrote: > Hi again, > > to continue the discussion with the tracking system, I have now had > an, albeit brief, look at the Sourceforge tracking system, and Jira. > Feel free to contradict or generally discuss. > > First Jira. I see two problems here: > > 1. It is too complex. You can administrate several projects, link > everything together with release history and whatnot; basically, > perfect for a complex company. However, when I look at some publicly > available setups, I get the feeling you need to read a manual first. > In other words, a bit too heavy for the <= half a dozen developers. > 2. While it is free for open source projects, as far as I understand, > the idea is that you install a trial version and somehow apply for > the full version. If possible, I would like to avoid having to > care for another piece of software, but rather use a Cloud service > here. > > > Regarding the sourceforge internal tracker, it looks like your standard > tracker setup. You have milestones which consists of single tasks, > which each have a couple of customizable fields, some text, and a > discussion. What I dislike here is that if you have a couple of tasks > around (10 unclosed tasks might not be uncommon), it might be a bit > annoying to get a quick one-second glance about the status. Otherwise, > it might be possible to tweak it to our use. > > > Mantis is probably in the same vein as the sourceforge tracker. Unless > there is some free hosting, I would suggest against it, again to avoid > having to care for additional software. > > > For the kanban board, I have attached two screen shots for how we use > it in freelords. Basically, we create a new swimlane (/row) for each > design task (silver), in which we put and move around smaller coding > tasks (green/brown). > > > In summary, I would suggest either to try out the internal tracker > (because it is internal and something new for me), or the kanban board > (works fine with this style of project development). > > > Comments? > > > Ulf > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > > > _______________________________________________ > Wavepacket-ng-devel mailing list > Wav...@li... > https://lists.sourceforge.net/lists/listinfo/wavepacket-ng-devel -- *---------------------------+----------------------------------------* | PD Dr. Burkhard Schmidt | Mailto:bur...@fu... | | Freie Universitaet Berlin | HTTP://page.mi.fu-berlin.de/bsch63 | | Institute for Mathematics | Phone : (+49) 30 / 838 - 75 369 | | Arnimallee 6 | (+49) 30 / 838 - 75 367 (secr) | | D-14195 Berlin-Dahlem | Fax : (+49) 30 / 838 - 75 412 | *---------------------------+----------------------------------------* |