[ros-users] Hydro Medusa Plan for code.ros.org

Tully Foote tfoote at willowgarage.com
Thu Jan 31 19:21:41 UTC 2013

We plan to keep maintaining kforge.ros.org going forward, we are not
actively migrating off of it. However we expect the number of active
projects to decrease over time as we and others follow our recommended
repository usage [1]

To Jack's question about links

Most automatic references should be fixed by updating references in
ros/rosdistro.  The only other place is any documentation on the wiki or in
the code.  One common place will be the link at the bottom of each page
pointing to the issues.


[1] http://www.ros.org/wiki/RecommendedRepositoryUsage

On Thu, Jan 31, 2013 at 10:47 AM, Jonathan Bohren <jonathan.bohren at gmail.com
> wrote:

> Also, what's the status/future of kforge.ros.org?
> -j
> On Thu, Jan 24, 2013 at 2:19 PM, Aaron Blasdel <ablasdel at willowgarage.com>wrote:
>> Hello Everyone,
>> This is a message to all packages maintainers.
>> We would like to announce our plan to suspend code hosting on
>> code.ros.org following the Hydro release and ask all maintainers of
>> packages hosted there to plan to migrate to GitHub during the Hydro cycle.
>>  All tickets and source control history can be preserved in this process.
>> For a little bit of background, at Willow Garage we have started using
>> GitHub regularly and now recommend it to the wider community[1] many of the
>> Willow hosted packages have been transferred already. And we plan to
>> continue migrating packages to GitHub.
>> As we are now recommending Github and actively moving packages off of
>> code.ros.org already we have determined that the effort to keep
>> code.ros.org running in its current form is not worth the benefit.  It
>> currently has significantly degraded performance, especially for tickets.
>> Using GitHub provides better and more up to date hosting opportunities for
>> all developers in the greater ROS community.
>> For help migrating your repositories please see the migration helper [2]
>> It has instructions for how to migrate both code and trac tickets to
>> GitHub.
>> Please let us know if you need help or guidance.  We are happy to help
>> facilitate and suggest into what organizations stacks could be migrated.
>> [1] http://www.ros.org/wiki/RecommendedRepositoryUsage
>> [2] http://www.ros.org/wiki/RecommendedRepositoryUsage/MigrationHelp
>> _______________________________________________
>> ros-users mailing list
>> ros-users at code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
> --
> Jonathan Bohren
> PhD Student
> Dynamical Systems and Control Laboratory
> Laboratory for Computational Sensing and Robotics
> The Johns Hopkins University
> (707) 520-4736
> jbo at jhu.edu
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users

Tully Foote
tfoote at willowgarage.com
(650) 475-2827
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20130131/fc7b5eff/attachment-0004.html>

More information about the ros-users mailing list