Enforcement and honoring of obligations in the Galileo Release Train was the theme in part six of my interview in Eclipse Magazin.
There are two bodies at work here. First, is is the Planning Council that makes decisions with regard to the release train itself. Independent of the release train is the Eclipse Development Process. So the Planning Council is responsible for all the aforementioned list of release train obligations (i.e. the “must dos” and “should dos“), and it is the EMO that is responsible for making sure that all of the projects have, for example, clean intellectual property (IP). There is some overlap: both bodies are very concerned about community development and communication. My experience has been that the two bodies have worked very well together.
In term of enforcing the obligations, community pressure has done a very good job of making sure that projects meet their obligations. There have been a few times during the process where the Planning Council Chair, David Williams, has had to be stern with a project to honor their Galileo commitment, but these incidents have been resolved very quickly. As far as I know, only one project dropped out of the release train, but they did so of their own accord.
See part one, part two, part three, part four, and part five of this series.
