On Friday 12 August 2011 14:35:36 Tim Moore wrote:
> However, before I start adding repositories for completely
> new aircraft, we should think about why new aircraft should be under
> the Flightgear project.
> 
> Pros: centeralized location for obtaining aircraft, Flightgear "seal
> of approval"
> Cons: Flightgear project has to manage new repos, aircraft must be
> under the license that Flightgear chooses (GPL)
> 
> Other thoughts? Perhaps the wiki would be a better place to promulgate
> aircraft! Tim
> 
On the pros side, maybe some sort of automatic solution similar to terrasync 
could be implemented for aircraft, this solution would then benefit from a 
centralized location (although that is not necessary, repository location 
could be added as a tag in the aircraft -set.xml file).

------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system, 
user administration capabilities and model configuration. Take 
the hassle out of deploying and managing Subversion and the 
tools developers use with it. 
http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to