KL-666 wrote:
- What material are we dealing with? Data? Software?
- What is a good way to work with that material? (developing and delivering it to users)
1. The material we are dealing with is 100% data. This is, terraGIT/terrasync content is Not a source code. It is presented in a form that is ready to be interpreted/rendered as Scenery for FlightGear.
2. TerraGIT and terrasync are both ready for delivering to users.
* terraGIT must be cloned in a local hard drive, and world scenery to be used must be initialized per tiles or other manner (see install script) to get partly or wholy world scenery ready in a local disk. TerraGIT also serves as development repository of this content, in the sense that you can submit updates to it, directly and with no intermediates (exemple, pushing a new airport layout, or a new terminal for Sao Paolo)
* terrasync is a content 100% similar is nature to that of terraGIT but it is distributed differently. Either on the fly, or via terrafs/terramaster or subversion.
Terrasync could also serve as a repository for pushing updates to this content, but no-one uses this as such.
The sources are located elsewhere, and the content is created, outside of the distribution ready sandboxes, such as terrasync/terraGIT.
Examples:
The "Scenery projects such as India or Philippines"
https://github.com/ProjectPhilippineshttps://github.com/projectindia-FGFShttps://github.com/NorwayProjector, the Scenery stand alone projects in FGMEMBERS-SCENERY
https://github.com/FGMEMBERS-SCENERYWhere to maintain sources content and to specifically have the "development" content of the ready-to-be-rendered scenerios in terrasync/terraGIT is a completely different bulk.