[Ros-release] how about a single issue tracker?

Jack O'Quin jack.oquin at gmail.com
Tue Dec 13 17:28:05 UTC 2011

On Thu, Dec 8, 2011 at 8:14 PM, Tully Foote <tfoote at willowgarage.com> wrote:
> I definitely agree that this is becoming a challenge to manage and we should
> make sure it is easy to use.
> However, I believe that the one tracker system is extremely imposing to
> external developers and near impossible already.  And as we work toward
> making external library integration easier this goes the opposite direction.
>  And as we're approaching the point that external libraries can simply add
> "ROS Compatability" with a few metadata files we can't tell them to use our
> tracker.  And if we have one main one and many small ones, we still have the
> same problem.

How about a unified tracker for just the code hosted at WG, including
code.ros.org and kforge.ros.org? Kforge made the problem worse by
dividing tracking into overly small chunks.

Seems like that would solve 90% of the problem without stepping on
federated development turf.

More information about the Ros-release mailing list