1 Code Conventions

This section provides a few general conventions for GeoServer developers, about formatting code, testing, directory structures, refactoring, and logging.

• 1 Formatting — Information on how to format your code to match the rest of the codebase
• 2 Subversion conventions — Recommendations for using GeoServer's SVN
• 3 Logging — Most GeoServer logging conventions are directly inherited from GeoTools
• 4 Refractoring — Recommendations for performing refactors of code in GeoServer
• 5 Bug Fixing

2 Documentation Guidelines

run geoserver and open the config ui

3 Project Roles

• 0 Project Steering Committee
• 1 Getting Commit Status

4 Testing

• 1 Unit and functional tests — Testing performed during the GeoServer build is the first safety net against bugs and regressions
• 3 CITE tests — The CITE Conformance Tests of the Open Geospatial Consortium are the best functional tests we have of GeoServer
  • 1 Running CITE Tests
• 4 Hand Testing

5 Change Conventions

This section contains procedures for small fixes up to major improvements

• 1 Reporting Issues — How to report issues in GeoServer
  • Creating a Patch
• 2 GeoServer Improvement Proposal — A GSIP - GeoServer Improvement Proposal is the formal mechanism used to perform any sort of major change in the GeoServer project
• 3 Merge Procedure — Guidelines on performing merges in the codebase

6 Communication

The various avenues for communication within the GeoServer Project

• 1 Mailing lists — Links for archives and subscription management
• 2 Issue Tracker — Our JIRA issue tracker is one of the primary modes of communication
• 3 IRC
  • IRC Meeting Log Feb 19 2008
• 4 GeoServer Improvement Proposals — How the project communicates about large changes - a persistent mechanism that all stakeholders can comment on

7 Releasing

h1. Create a GeoServer Release

• Deploying — Deploy GeoServer jars to the Maven Repository
• Pre-Release Testing Walkthrough

8 Licensing

• Contributor Agreement
• Do I need a proprietary license FAQ