simple issue tracking system

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

simple issue tracking system

Radu B. Rusu
Administrator
How do folks feel about a simpler tracking system where we could get a nice roadmap page with features, bugs, etc?

I'm thinking something like this: http://zwiki.org/IssueTracker. The inspiration came after seeing a rather static page
that the Eigen folks used for a TODO list: http://eigen.tuxfamily.org/index.php?title=Todo_for_3.0. Add colors to that,
and that would be great for simpletons like me!

Or is everyone else but me really gotten used to the Trac system? :) I find it too complex, with too many options that I
never use most of the time. Or does anyone know how to customize its template similarly to the way CMS systems do?


PS. Please don't turn this into one of those svn vs git discussions. ;)

Thanks,
Radu.
_______________________________________________
[hidden email] / http://pointclouds.org
https://code.ros.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: simple issue tracking system

Jack O'Quin
On Sun, Dec 12, 2010 at 9:58 PM, Radu Bogdan Rusu <[hidden email]> wrote:
> How do folks feel about a simpler tracking system where we could get a nice roadmap page with features, bugs, etc?

I am not particularly fond of Trac or any other issue tracking system
I have used over the years.

But, going to a "simpler" system increases complexity for almost
everyone, since we must still use Trac for all the other ROS
components. We probably also have to register yet another ID for the
new system.

Doesn't seem so good to me.
--
 joq
_______________________________________________
[hidden email] / http://pointclouds.org
https://code.ros.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: simple issue tracking system

Radu B. Rusu
Administrator
Jack,

These are fair observations. Thanks.

On 12/12/2010 08:10 PM, Jack O'Quin wrote:

> On Sun, Dec 12, 2010 at 9:58 PM, Radu Bogdan Rusu<[hidden email]>  wrote:
>> How do folks feel about a simpler tracking system where we could get a nice roadmap page with features, bugs, etc?
>
> I am not particularly fond of Trac or any other issue tracking system
> I have used over the years.
>
> But, going to a "simpler" system increases complexity for almost
> everyone, since we must still use Trac for all the other ROS
> components. We probably also have to register yet another ID for the
> new system.
>
> Doesn't seem so good to me.

What we might be looking for here is a system that allow us to draw a roadmap with feature requests and wish lists for
the future. We don't want a trac-like system where bugs/features are assigned to a single person. We want these to be
open so that everyone who is interested in participating can pick up components and help.


Troy had a brilliant idea that we might try to implement, provided that there's interest: before every release, we do a
bugsprint + intensive communication (possibly via IRC or similar) with those interested in helping out. We might start
small with a few, and then grow and/or reduce based on interest/demand. The web page that I have in mind would help with
this too.


We have a lot of resources at Willow Garage for projects like PCL and there's probably orders of magnitude more in the
community. Giving everyone a fair chance to contribute, and step up, would mean a lot, and everyone would benefit. Open
source BSD projects are awesome! :)


Cheers,
Radu.
--
http://pointclouds.org
_______________________________________________
[hidden email] / http://pointclouds.org
https://code.ros.org/mailman/listinfo/pcl-users
Reply | Threaded
Open this post in threaded view
|

Re: simple issue tracking system

Alex Bravo
In reply to this post by Radu B. Rusu

We don't want a trac-like system where bugs/features are assigned to a single person. We want these to be
open so that everyone who is interested in participating can pick up components and help.


Troy had a brilliant idea that we might try to implement, provided that there's interest: before every release, we do a
bugsprint + intensive communication (possibly via IRC or similar) with those interested in helping out.
 
Great idea.
 
Fixing [simple] bugs in existing code is one of the best ways to learn a new system, right behind reading code and wiki and doing tutorials.
 
Alex Bravo

_______________________________________________
[hidden email] / http://pointclouds.org
https://code.ros.org/mailman/listinfo/pcl-users