[Documentation] [TitleIndex] [WordIndex

ROS Platform Group Meeting Notes 2013-03-13 http://etherpad.ros.org/p/ROS_Platform_Group_2013-03-13

In attendance:
Dirk
Isaac
Brian
William
Paul
Tully
Chad
Austin

Updates: 
Post Groovy Cleanup completed! https://github.com/ros/rosdistro/issues?milestone=5&state=open
66 Hydro packages released on Friday and built into debs over the weekend
Threshold for syncing is lowered to 60 for hydro

Action Items Carry over from last week: http://etherpad.ros.org/p/ROS_Platform_Group_2013-03-06
REP 132 Changelog Circulation Date discussion
headline discussion: date, time, additional text
Require date
Supports non scm imports, or out of date/inaccurate/incomplete scm entries
Plan to Support ISO standard (allow truncated version)
Can use date tool to generate full RFC script @ahendrix (fill out how debian does this)
Debian uses the date format from section 3.3 of RFC 2822: http://www.ietf.org/rfc/rfc2822.txt
On Ubuntu, 'date -R' generates an appropriately formatted timestamp. OS X does not have this flag. 
Equivalent date format string: "%a, %e %b %Y %T %z"
Also consider RFC 3339: http://www.ietf.org/rfc/rfc3339.txt (ISO 8601)
@ahendrix:write down spec what is allowed and update REP
No additional text in the headline, can be place in other headlines or as content under the headline
This is a top priority for work today.  
REP 133 Screen before circulating @dthomas @tfoote
REP 134 @wjwood to review
REP 135 Ready to vote? @chadrockey
Outstanding issues resolved, ready to merge and mark as active
REP 137 [Rosdistro] Ready to draft API on top of REP for reference implementation.  @po1 @tfoote @dthomas
add build configuration?
jenkins buildfarm address
apt repo address
specify sync criteria
REP 138 voting in progress.  FInished? @chadrockey
Add references, then ready to go active
Create a rosdistro merging status page. @tfoote
Alternative is to turn off the sourcedeb triggering, automatic reenable must be suppressed
Python Policy confirmation: https://github.com/ros/rosdistro/issues/506
@joq would like a way to flag packages as not python 3 compatible
Could use a version dependency on python, currently not supported by infrastructure
Could use an export flag, to get visibility onto the wiki
generally not liked, but not sure of a better solution.  Would it be a whitelist or blacklist?
description has the same effect
Could have a policy, bugs filed for python3 compatibility, maintainer should update files or not it in the package.xml
If not planning to support python3 note it in the description. 
We need to run raring prerelease and devel jobs to help catch this
Ticket roslaunch for enhancement for @dirk-thomas
Create catkinization backporting guidelines @tfoote 
re: xacro

Upcoming development efforts
Rosdistro API
More Hydro Releases
Gazebo Backports\
We're exploring policy of code review before commit.  Thoughts to start with a small set of packages.  
We'll look for one +1 and the requester is responsible for merging it.  The reviewer can merge it if they wish. If it's an external pull request it's the job of maintainers. 
Current packages
rosdistro(lib)
rosdep
bloom
catkin_pkg
all packages part of ros base

Updating Milestones from new schedule emailed March 4th @dirk-thomas
Announcement: http://news/2013/03/hydro-fork-update.html

Hydro Alpha Release Milestone: https://github.com/ros/rosdistro/issues?milestone=7&page=1&state=open

Hydro Beta Release Milestone: https://github.com/ros/rosdistro/issues?milestone=8&page=1&state=open

We'll plan to keep these up to date. 
(TK, in absence): REP134 (catkin_make_isolated) pull request changed according to Dirks comments, 3 comments were pending clarification
https://github.com/ros-infrastructure/rep/pull/20
Permission to delete items below if my answer to comment was satisfying
https://github.com/tkruse/rep/commit/c6f99e6c3e9f95b : "catkin workspace will make the default catkin build fail."
https://github.com/tkruse/rep/commit/fdf0ae60d5: "installing packages installs to the CMAKE_INSTALL_PREFIX"
https://github.com/tkruse/rep/commit/ab489e2c3e5a : Should package-specific setup.*sh be mentioned, or are they volatile?
Review these comments @william
(TK, in absence): OSRF "Organisation" at ohloh.net, Tully to write request?
http://meta.ohloh.net/2012/10/introducing-ohloh-organizations-a-new-view-on-foss/
Possibly a good idea, not sure what amount of time it will take to maintain.  @tfoote investigate

2024-12-07 14:59