|
Conventions and Guidelines |
|
Look here for the for the coding standards, naming conventions,
and other guidelines we use to help ensure SolarEclipse presents to
users and developers as a unified whole rather than as a loose
collection of parts.
|
|
CVS Repository |
|
We use the Concurrent Versioning System
(CVS) to support concurrent
distributed development, and we use Eclipse as our CVS client because
it supports CVS directly.. All SolarEclipse development is carried
out in this repository. The server supports both "extssh" and
"pserver" type CVS connections - "pserver" only works for anonymous
access.
|
|
Mailing Lists |
|
SolarEclipse uses mailing lists for development coordination, design
discussions, voting, announcements etc.
|
|