[ros-users] Groovy Planning SIGs

[Tully Foote]

Hi everyone,

We are beginning the planning cycle for our next ROS Distribution, ROS
Groovy Galapagos, in order to make it easier for people to get involved and
also
handle the breadth of areas that ROS-related software deals with.

If you go to:

http://www.ros.org/wiki/groovy/Planning

You will see an editable list of Special Interest Groups (SIGs).
Below each SIG is a brief description as well as a signup list.  We
have seeded the list so that people have some examples to go by.

The process is very simple:

 1. Propose an SIG: anyone can propose an SIG.  Please only propose an
SIG if you are willing to contribute.
 2. Signup for an SIG: anyone can signup for an SIG.  Please only
signup for an SIG if you are willing to contribute (e.g. code).

The signup period will last until May 20th (The end of ROSCON).

After the signup period, any SIG that has at least two people signed
up for it will be considered valid.  If you are proposing a SIG, we
urge you to recruit authors/maintainers of the relevant software --
the authority of what goes in/out of a library remains with the
maintainer/author, so their buy-in is crucial.  Similarly, we
encourage authors/maintainers to signup for SIGs that are relevant to
their software.

The follow-up process is also very simple:

 1. Each SIG designates a SIG Coordinator.  If an SIG cannot agree on
a coordinator, one will be chosen for you.
 2. The coordinator will organize planning meeting(s) for the SIG.
This can be over IRC, video chat, at IROS, or whatever medium bests
fits the composition of your SIG. The deadline for these meetings is
May 20th.
 3. Each SIG group will post their planning notes as a sub-page of
http://ros.org/wiki/groovy/Planning/<SIG-NAME>.  The deadline for
posting these notes is May 27th.  SIGs can have followup
meetings, but this initial deadline is to ensure that the SIG is
activated.

The plans are just that -- plans.  It is up to the members of each SIG
to achieve as much of that plan as possible in time for the freeze
dates of ROS Groovy (remember, there's always H Turtle).

As always, we appreciate your participation.  We hope this more
distributed process will better match the distributed nature of ROS
development.

regards,

 -- your friendly neighborhood SIG meta-coordinators
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/ros-users/attachments/20120508/0cd2b0c9/attachment-0003.html>