Help on getting started as a GPSTk developer
Development of the GPSTk is performed in
Subversion. While specific patch can be submitted by email, the preferred method if for all developers to directly modify the
Subversion repository.
Anyone wishing to contribute has to get authorization to check in to subversion by the GPSTk
CoreTeam. The GPSTk
CoreTeam will retain the both right to rescind access to particular developers and to remove items from the repository that the GPSTk
CoreTeam judges to be inappropriate for the toolkit. The process to apply for a subversion write access is very simple:
- Read DeveloperResponsibilities to fully understand what you are getting into.
- All developers are recommended to subscribe to WebNotify in the Development web and WebNotify in the Documentation web, in order to be notified automatically when something changes in either web.
- You should also subscribe to the Subversion list on the GPSTkEmailLists for checkin notifications and occasional conversational discussions among developers.
- Create a Sourceforge account (http://sourceforge.net/account/newuser_emailverify.php). As part of this process you will choose a UNIX name for yourself. Take note of this UNIX name as you will need it later for access to the Sourceforge repository.
- Email the GPSTk CoreTeam at mailto:gpstk@arlutSPAMBOTBLOCKNOW.utexas.edu. If they don't already know you, introduce yourself and your plans for contribution to the GPSTk. In the email include the UNIX name of your development account with SourceForge.
Even before you get checkin rights, you can check out the Subversion repository and start developing. See the
SubversionReadme for getting started with Subversion. Also read the
CodingStandards.
GPSTk also has an IRC channel for developers; #gpstk carries general discussions about GPSTk, and is often the best place to get real-time developer support. See
GPSTkIRC for more information.
See the
LicensingAndCopyrightFAQ if you have questions about the licenses that apply to GPSTk, and how they might effect your work.
Discussion