Development workflow

This article is outdated but is kept for historical reference. The Gitorious open source infrastructure has been shut down and all of the FlightGear source code and data repositories migrated to SourceForge. See also the discussion page.

This page outlines some first steps on how to do (code) development for FlightGear.

The Big Picture

The FlightGear sources are hosted at SourceForge: https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/

As a safety precaution, the commit access to those repositories is not public and hence development work has to be somewhat staged.

Once this staging is done, there are two major possible ways for the done work to find its way back into the official sources:

1. A person with commit access OK's the work and commits it, using her or his account.
2. A merge request has been filed and somebody with the proper access performs the merge.

Fortunately the staging necessary for both approaches is essentially the same

Using a Personal Gitorious Repository

NOTE: This is essentially my tale. AndersG guided me through the process and I wanted to record/report it somewhere. Hcc23 13:59, 19 May 2011 (EDT)

1. Create (or login to) a Gitorious account at https://www.gitorious.org/login
   1. If you have a Google account (e.g. Gmail), you can use that to login:
   2. Click Or log in with OpenID
   3. Enter https://profiles.google.com/yourGoogleLoginName, replacing yourGoogleLoginName with your Google login (i.e. whatever you have in front of @googlemail.com or @gmail.com).

The Clone repository button on https://gitorious.org/fg copies (clones) a Gitorious repository into ones private Gitorious account.