Revision history [back]

I'll give my answers, perhaps others will add more details.

1. You only need to send a message to the ros-users mailing list containing the repository address.

   There may be additional "best practices" I don't know. If so, I hope someone will mention them.

2. Wiki pages are not created automatically. You are free to create them before or after announcing the new repository.

   Please do create them, using the appropriate wiki templates. Some fields will not appear until the indexer finds your code. That's OK.

   Personally, I like to create package and stack pages before they appear in the repository. Then, I can easily tell when the indexer has visited them.

3. Binary ROS releases are not required, but I would recommend them. A good general open source practice is to "release early and often".

I'll give my answers, perhaps others will add more details.Here is a good overview of creating your own ROS repository.

1. You only need to At a minimum, send a message to the ros-users mailing list containing the repository address.

   There Since git and hg repositories generally require separate source URLs for each stack, you may be additional "best practices" I don't know. If so, I hope someone will mention them.also provide a .rosinstall file, if desired.

2. Wiki pages are not created automatically. You are free to create them before or after announcing the new repository.

   Please do create them, using the appropriate wiki templates. Some fields will not appear until the indexer finds your code. That's OK.

   Personally, I like to create package and stack pages before they appear in the repository. Then, I can easily tell when the indexer has visited them.

3. Binary ROS releases are not required, but I would recommend them. A good general open source practice is to "release early and often".

Here is a good overview of creating your own ROS repository.

1. At a minimum, send a message to the ros-users mailing list containing the repository address.

   Since git and hg repositories generally require separate source URLs for each stack, you may also wish to provide a .rosinstall file, if desired.allowing fine-grained control over your part of the index. (For svn repositories, that is often not needed.)

2. Wiki pages are not created automatically. You are free to create them before or after announcing the new repository.

   Please do create them, using the appropriate wiki templates. Some fields will not appear until the indexer finds your code. That's OK.

   Personally, I like to create package and stack pages before they appear in the repository. Then, I can easily tell when the indexer has visited them.

3. Binary ROS releases are not required, but I would recommend them. A good general open source practice is to "release early and often".