Issue 290 in rtm-ros-robotics: Moving to github?

[rtm-ros-...@googlecode.com]

Status: New
Owner: iisaac.s...@gmail.com
Labels: Type-Enhancement Priority-Medium

New issue 290 by gm130s: Moving to github?
http://code.google.com/p/rtm-ros-robotics/issues/detail?id=290

(Originally suggested mildly here [1])

Reason why I propose: looks like it's not common for svn repository to hold
several packages under trunk in general, and post-catkin toolset follows
the formulas rather strictly.

##There are a list of repositories [2] where multiple packages placed under
trunk, but none of those are catkinized.

We have been attempting changes particular to this non-standard svn setting
[3], [4] in order to take the most advantage of nice and easy tools from
ROS ecosystem, but as in [4] it's easy to hit the limitation.

[1] https://code.google.com/p/rtm-ros-robotics/issues/detail?id=137#c8
[2] https://github.com/ros/catkin/issues/513#issuecomment-24992051
[3] https://github.com/ros/catkin/issues/513
[4] https://github.com/ros/catkin/issues/556


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[rtm-ros-...@googlecode.com]

Comment #1 on issue 290 by kei.ok...@gmail.com: Moving to github?
http://code.google.com/p/rtm-ros-robotics/issues/detail?id=290

Although I have many reason not to move to github, it provides very strong
tools of CI before merging, that will help our effort to keep maintain
source code for different ros distributions. So the problem is when we
move? If I move the repository this weekend, how do other people think?

I'll follow this instructions :
http://trentm.com/2012/03/google-code-to-github.html

===

Basically, I prefer to use old technology/tools since basically robotics
needs variety of tools and components and they are not always keep updated.
For example, Hiro robot's controller computer (QNX) does not contains git
binary, our HRP2 robots still use ubuntu 8.04 due to the driver of DIO
board, that of course does not have git deb.

If we look bask last few years, the trend of VCS is changing from
svn(willowgarage) to hg(osrf/drc) and git(osrf/ros), so we can estimates
there are another VCS in few years and people will discuss about moving
form github to new X platform. Thus, post catkin toolset should be designed
more general, not to depends on one specific platform. So it worth to keep
sending feedback.

Finally, since this is the university's project and there are no central
admin that take care of all packages, each package is maintained by each
student so it is easy to split code and make branches if we move the
platform. If student only left less than one year to graduate, they choose
keep using old repository instead of moving to new one. From my experience
of moving internal repository to sourceforge it takes about a year to
remove internal repositories.

[rtm-ros-...@googlecode.com]

Comment #2 on issue 290 by kei.ok...@gmail.com: Moving to github?
http://code.google.com/p/rtm-ros-robotics/issues/detail?id=290

If we're ok with moving to github, how do we setup the repository?

put rtmros_common / openrtm_common under start-jsk ? or create new
organization named rtm-ros-robotics? other idea?

[rtm-ros-...@googlecode.com]

Updates:
Status: Started

Comment #3 on issue 290 by gm130s: Moving to github?
http://code.google.com/p/rtm-ros-robotics/issues/detail?id=290

I don't belong to a school so I'd try to hold back from the vote (but +1
for the move).

Switching from svn --> git can be seen as centralized VCS --> distributed.
Here there's a shift of paradigm that may last longer than an year.

Another way of seeing it is that ROS' choosing github is a switch from
own-hosted to public repository that's run by private company where we can
expect constant enhancement and good maintenance.

Since I'm one of the few core users of hironx, I'm willing to take charge
of it if that makes sense.