Groovy Planning

Planning for Groovy will be done via Special Interest Groups (SIGs). These SIGs will be determined by the community and anyone interested in participating/contributing will be allowed to sign up.

For reference, see the Fuerte SIGs.


The deadlines for the Groovy SIGs has been adjusted to allow in person meetings (both planned and impromptu) at ROSCon.

  • May 20: SIG Signup
  • May 20: Deadline for first SIG meetings
  • May 27: Deadline for posting notes from first SIG meeting
  • October ? [planned for August 15]: Primary freeze. APIs with dependencies frozen
  • December 10 [planned for October 15]: Groovy Beta Release. Packaging complete, all APIs frozen.
  • December 31 [planned for November 15]: Groovy Release

Primary freeze: any APIs that are heavily used should be frozen here. New feature development that does not affect existing APIs may continue. Also, packaging for release can continue (e.g. stack/package organization, rosdeps, etc...).

Final freeze: all APIs and packaging frozen. Releases with features should have occurred before this date so that integration is tested. While some breaks/bugs are expected, features that have failed to land/integrate at this time will be removed ("failed to integrate" == "causes unexpected downstream breakage").


Phase I (SIG proposal/signup)

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.

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.

Phase II (SIG meetings)

After the signup period, any SIG that has at least two people signed up for it will be considered valid.

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 September 28th.
  3. Each SIG group will post their planning notes as a sub-page of<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.


Add your SIG below

Wiki: groovy/Planning (last edited 2013-01-15 22:07:16 by ThibaultKruse)