Re: [Orekit Developers] Developer Guidelines

[Luc Maisonobe <Luc.Maisonobe@c-s.fr>]

Le 19/06/2014 14:04, Bob Reynders a écrit :
> Hello everyone,

Hi Bob,

> 
> Now that Forge is available again (was unavailable at the time of
> writing the first post) I found the guidelines page[1] which answered
> all questions except for the branching. 
> 
> Since we (the SOCIS participants) will be doing semi-longterm
> development the Orekit developers might have a preference towards Git
> development, a concrete example would be rebases vs merges.

Yes, we have some preferences.
As Orekit is a project operationaly used in space missions, write access
to it is subject to some specific rules described in the governance
document <https://www.orekit.org/forge/documents/4>. You don't really
need to read this document, as in fact for SOCIS students we have
already set up a separte process : they have a dedicated sub-project on
the forge and a dedicated repository.

For your project, I have set it up. The forge project is
<https://www.orekit.org/forge/projects/socis-2014-database> and you
already are declared as a developer, and the Git repository is here for
public read only <http://www.orekit.org/git/socis-2014-database> and
here <ssh://git@www.orekit.org/socis-2014-database.git> for restricted
read-write access.

I will ask you to sent directly to me the public part of an SSH key so I
can grant you write access to this base (you can create the key with
ssh-keygen from the openssh package if you work from a Linux desktop).
This repository is a clone of the original orekit base, and you can play
with it at will. I propose you to set up a branch for your experiments.
People who want to look at it can simply put this repository as an
additional remote and fetch your branch from it.

best regards,
Luc

> 
> Cheers
> Bob
> 
> [1] https://www.orekit.org/static/guidelines.html
> 
> 
> On 19 June 2014 13:12, Bob Reynders <tzbobr@gmail.com
> <mailto:tzbobr@gmail.com>> wrote:
> 
>     Hello everyone,
> 
>     My exam schedule is freeing up so I expect to get some work done in
>     the near future.
> 
>     Are there any guidelines for new contributers such as formatting
>     rules, unit test restrictions, Git feature branches, etc. that
>     should be considered?
> 
>     Cheers
>     Bob
> 
>