Now that I know how things are set up, it makes sense to me and seems perfectly reasonable. Thanks for the clarifications. On Fri, Jul 9, 2010 at 4:34 PM, Ken Conley wrote: > Hi Advait, > > Your previous experience was probably because someone had already > created the package wiki pages. > > It's a bit of a compromise -- the 'browse' tab will show you *every* > known ROS package in the universe, the wiki only shows you ones where > some effort in creating documentation has been expended. As it only > takes 5 seconds to create a package page, this has been a low-effort, > but useful filter. There's a lot of churn in the ROS package universe > and this layer lets you 'curate' the packages you wish to present on > the gt-ros-pkg page. > > Suggestions are always welcome as the growth of ROS packages and > public repos has been staggering this year, and it's been a bit of > race to keep up. > >  - Ken > > On Fri, Jul 9, 2010 at 1:21 PM, Advait Jain wrote: >> Hi Ken, >> >> Some examples of packages in gt-ros-pkg that are not showing up are >> hrl_segway_omni,  2010_icra_epc_pull, phantom_omni. None of these >> packages has a wiki page on ros.org. >> >> My understanding was that the macro creates a link from the subversion >> repository to a wiki page using the manifest.xml, we can then go in >> and add more documentation. It seemed like that is what happened when >> we first created our repository homepage on ros.org - all our existing >> packages showed up with an wiki page that had the PackageHeader macro. >> >> I created a wiki page for 2010_icra_epc_pull and it is now showing up >> in the list of packages. >> >> Advait >> >> >> On Fri, Jul 9, 2010 at 3:49 PM, Ken Conley wrote: >>> Hi Advait, >>> >>> The macro is wiki-based, so it will only list packages that have wiki >>> pages on ROS.org. Specifically, it looks for wiki pages with >>> '/gt-ros-pkg' in the text. Our infrastructure attempts to >>> automatically insert this into the appropriate pages, but there are >>> occasional issues that we can debug if you can provide examples of it >>> not working. >>> >>> Hope this helps, >>> Kne >>> >>> On Fri, Jul 9, 2010 at 12:16 PM, Advait Jain wrote: >>>> It seems that the <>>> -CategoryRepo)>> macro is not working for us. The new packages that we >>>> have added to our ROS repository do not show up in the list. Is this >>>> macro being used incorrectly? >>>> >>>> This is our repository homepage on ros.org: >>>> http://www.ros.org/wiki/gt-ros-pkg >>>> >>>> Advait >>>> _______________________________________________ >>>> ros-users mailing list >>>> ros-users@code.ros.org >>>> https://code.ros.org/mailman/listinfo/ros-users >>>> >>> _______________________________________________ >>> ros-users mailing list >>> ros-users@code.ros.org >>> https://code.ros.org/mailman/listinfo/ros-users >>> >> >> >> >> -- >> PhD student >> College of Computing >> Georgia Tech >> >> http://www.cc.gatech.edu/~advait >> _______________________________________________ >> ros-users mailing list >> ros-users@code.ros.org >> https://code.ros.org/mailman/listinfo/ros-users >> > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > https://code.ros.org/mailman/listinfo/ros-users >