wavepacket-ng-devel

[Wavepacket-ng-devel] Tracking system

[Ulf L. <ul...@wa...>]

Hi,

we further need something to keep track of all tasks and who is doing
what. What we would need is to create tasks with text and such and
change their status (working on it, up for review, done). The rest are
convenience features, but might still be a killer argument. Things like
grouping tasks together into some distinct project, task dependencies,
blocking tasks when they are stuck somehow, ... you name it.

The options so far (please extend if you know more):

* The sourceforge tracker. You should all have permissions up to admin
  to test out a tracker at https://sourceforge.net/p/wavepacket/tickets.

  The advantage is that it is directly integrated in sourceforge.
  However, I have not tried it out yet, so please play around and tell
  if it would be usable.

* A kanban board: http://kanbanize.com is free and we use it with
  freelords quite successfully.

* Andrea mentioned Jira. I have no experience with it at all, so please
  add your arguments, knowledge etc.

* ...?


Ulf

Re: [Wavepacket-ng-devel] Tracking system

[Piotr B. <dms...@gm...>]

Hi,

I'm currently working with Mantis bugtracker. Works quite well.

Piotr

2012/12/5 Ulf Lorenz <ul...@wa...>

> Hi,
>
> we further need something to keep track of all tasks and who is doing
> what. What we would need is to create tasks with text and such and
> change their status (working on it, up for review, done). The rest are
> convenience features, but might still be a killer argument. Things like
> grouping tasks together into some distinct project, task dependencies,
> blocking tasks when they are stuck somehow, ... you name it.
>
> The options so far (please extend if you know more):
>
> * The sourceforge tracker. You should all have permissions up to admin
>   to test out a tracker at https://sourceforge.net/p/wavepacket/tickets.
>
>   The advantage is that it is directly integrated in sourceforge.
>   However, I have not tried it out yet, so please play around and tell
>   if it would be usable.
>
> * A kanban board: http://kanbanize.com is free and we use it with
>   freelords quite successfully.
>
> * Andrea mentioned Jira. I have no experience with it at all, so please
>   add your arguments, knowledge etc.
>
> * ...?
>
>
> 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
>

Re: [Wavepacket-ng-devel] Tracking system

[Ulf L. <ul...@wa...>]

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

Re: [Wavepacket-ng-devel] Tracking system

[Burkhard S. <Bur...@fu...>]

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        |
*---------------------------+----------------------------------------*

Re: [Wavepacket-ng-devel] Tracking system

[Ulf L. <ul...@wa...>]

On Mon, 17 Dec 2012 09:23:02 +0100
Burkhard Schmidt <Bur...@fu...> wrote:

> 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?

Well, having all data available on one view might be a good thing.

In any case, since there were no other replies, I would suggest to
first go for the internal ticket system, and then go to a kanban board
(or something else if someone has strong opinions) if this fails to
work out.


Ulf