[Documentation] [TitleIndex] [WordIndex

ROS Platform Group

The ROS platform group manages ROS releases and maintains core ROS packages for messaging, language support,building, packaging, etc.

Meeting Notes

This group organizes weekly meeting in the spirit of agile methods, to report on progress and help with blocking issues. Participants have mostly been Willow Garage staff or external package maintainers. Sometimes technical issues are mentioned that may be of interest to wider audiences. The notes here are an attempt to reveal these topics to the general public. For lengthy technical discussions, the mailing lists remain the medium of choice to integrate the community.

For questions and comments visit the ROS Buildsystem Special Interest Group

/Template

2013-03-20

/2013-03-20

2013-03-13

/2013-03-13

2013-03-06

/2013-03-06

27/02/2013

19/02/2013

12/02/2013

05/02/2013

29/01/2013

22/01/2013

Switch for Hydro to OSRF-provided debs only

15/01/2013

08/01/2013

18/12/2012

11/12/2012

Open Issues:

Updates:

catkin_make_prerequisites

need to find consensus on functionality, naming, etc.

goal is to make building a workspace more convenient when it contains non-catkin packages (flann, kdl, opencv, pcl, etc...), these packages do have a package.xml file (for dependencies) with the export tag <build_type>catkin(default)|cmake</build_type> but no catkin-enhanced CMakeLists.txt.

The flow would be:

  1. catkin_make_prerequisites (no target passing, flags go through)
  2. catkin_make
    1. now things are built into devel
  3. catkin_make_prerequisites --install
  4. catkin_make install
    1. now everything is installed into the install space

catkin should skip packages with the <build_type> tag not equal to catkin (which is default)

04/12/2012

Open Issues:

Updates:

27/11/2012

Open Issues:

Updates:

Hydro Planning

Hydro back in the rhythm, shoot for 1 week after ubuntu in april. Short cycle, mostly just refinements on Groovy

We’re going to be kicking off a Software QA Certification project to develop metrics and ways to verify that the metric is being met. WG workshop within 2 weeks.

We need standard best practices for how to develop effectively. Eg our recommendation to use github. We need to write down some guidelines to bring software engineering to more of the company and hopefully community. WG focus group for developing this process. Multiple levels of process, different levels of process for core released code, vs research /intern software. Goal to have a draft by the end of the year.

As we look toward Hydro development I’d like to take the SIGs to another level and make semi official projects of them which have their own goals and leaders. This is more of a meta discussion about how we should set that up.

20/11/2012

Open Issues:

Updates:

13/11/2012

Open Issues:

Updates:

05/11/2012

Open Issues:

Updates:

29/10/2012

Open Issues:

Updates:


2024-03-23 12:49