Members of the Science working group have enjoyed many benefits from the collaboration, below are some key benefits:
- True collaboration on common tools that benefit the community outside Eclipse such as the Eclipse January Project (libraries for handling numerical data in Java.). The Eclipse Advanced Visualization (EAVP) Project] could be a candidate for wide spread reuse.
- Simultaneous releases, which help drive release date selection for individual projects, gives the team a sense of accomplishment and leverages press releases to help gather attention.
- Simultaneous releases also help us get changes through the contribution questionnaire. Having other members of the Science TLP see the CQ process is helpful. It could also be that by having a larger combined release, we get more attention in the CQ process than we might if we were individuals. In addition, by doing the simultaneous Science release at a different time thatn the main Eclipse Release Train, we help even out the workload on the IP team.
- A smaller community of developers who will provide assistance with bringing up a new project. There is quite a bit to learn and the Eclipse mailing lists are great, but being able to ask an embarrassingly naive question to a smaller group is really helpful. Part of this is that if a project is a Science project, then the other members of the Science project have a stronger connection to new projects and have more invested in seeing the new project succeed.
- The Science TLP was able to work with the Eclipse org about licensing, which probably positively affected the EPL v2 design. The Science Charter includes an addendum that "approves the use of the GNU Lesser General Public License (LGPL) version 2.1 for dynamically linked Java-language thirdparty components distributed by projects under the Science Top-Level Project."
- We've found it easier to get committers added via the Science TLP, in part because the Science PMC have a different background and focus than other PMCs.