Latest revision as of 21:19, 2 February 2019

This page is out of date and should be removed soon.

Intro

SatNOGS uses GitHub for code, hardware, designs and issues repositories around the project. Each repository has a main and a co- maintainer who are ultimately responsible for committing code, versioning, accepting pull requests, triaging issues and generally owning the repo.

Naming

Any repo originating from SatNOGS project is named using `satnogs-<name>` (e.g. `satnogs-rotator`). We also maintain forks of other projects retaining their original names (e.g. `rtl-sdr`)

Versioning

Most **hardware** repos will be following this scheme:

- `master` is for current dev work.
- major versions will be branched out of `master` with major version number (e.g. `v2`).
- minor versions will be tags (e.g. `v2.1`).

All **software** repos are following this scheme:

- `master` reflects the production-ready state of the code.
- `dev` reflects the latest development code changes. This is the default merge target for Pull Requests.
- featured branches are created for development (e.g. `feature-add-single-view`),
- tags will be created for major revisions that we want to point to (e.g. `v3`).

Some repos (minority, like `satnogs-antennas`) will be following a folders-based versioning as it fits more their development scheme. (sorry git lovers!)