...

• We will discuss proposals from Matt and Igor on how to arrange our Java package space and CVS modules.
• AOB

Conclusions

We reached the following conclusions during the discussion:

• Create glast-java-cvs cvs in a separate repository
  • Use cvsspam for mail notifications
  • Use CVSWEB (at stanford) to view the pages
  • Have sandbox area for experimental modules

• Will use J2EE confluence area (perhaps renamed) for documentaion of convention etc.
  • Try to use more heirarchical structure
  • We should have getting started pages for Eclipse, Netbeans, ...

• Start with CVS, probably migrate to SVN when tool support and local experience has improved.

• Packages will be prefixed org.glast.
  • See if we can buy glast.org, or find another reasonable domain name

• We will use Matt's suggested code layout.
  • Jean-Paul had some concerns about Maven, in particular about stability of Maven over time and possible new initiatives like JSR-277. We agreed to use maven but try not to be overly dependent on it.

• Ask Mark to set up Cruise Control on one project to see how useful it will be.