20,741
edits
FGAddon: Difference between revisions
Jump to navigation
Jump to search
→History
m (Adapt git repository setup description to the new sourceforge interface) |
|||
| Line 17: | Line 17: | ||
In August 2015, a new FlightGear policy document was written to codify the unwritten standards of the project<ref>[http://article.gmane.org/gmane.games.flightgear.devel/78713 FlightGear Policy Document and V4.X Roadmap], draft document.</ref>. With this document, the licensing policy for the FlightGear aircraft has been updated from being GPLv2-only to now being a GPLv2+ or GPL-compatible<ref>[http://www.gnu.org/licenses/license-list.en.html GNU license compatibility list].</ref> stance. However, to combat licence proliferation complications for the integrity and good of the FlightGear project, it is strongly recommended that original content be GPLv2+ licensed. | In August 2015, a new FlightGear policy document was written to codify the unwritten standards of the project<ref>[http://article.gmane.org/gmane.games.flightgear.devel/78713 FlightGear Policy Document and V4.X Roadmap], draft document.</ref>. With this document, the licensing policy for the FlightGear aircraft has been updated from being GPLv2-only to now being a GPLv2+ or GPL-compatible<ref>[http://www.gnu.org/licenses/license-list.en.html GNU license compatibility list].</ref> stance. However, to combat licence proliferation complications for the integrity and good of the FlightGear project, it is strongly recommended that original content be GPLv2+ licensed. | ||
<!-- | |||
{{FGCquote | |||
|1= The short summary is that we already were maintaining a well established presence on sourceforge. So after quite a bit of discussion, we decided to consolidate there. In addition, we had a perpetual complaint that the fgdata git repository was far too big for most people to initially download (1Gb+). Thus we split off most of the aircraft (expecting unbounded future growth potential) into an svn repository called fgaddon. Sourceforge supports both git and svn repositories. This puts a dependency on a central svn server for our fgaddon aircraft repository, but lightens the weight for anyone wanting to checkout a copy of everything (you don't need a copy of the entire development history, and a copy of every version ever created of every aircraft if you just want to have the latest versions.) Plus svn allows checking out subtrees (without needing the whole repository) so this can also serve as a potential JIT single aircraft service provider. Of course there are always multiple ways to solve every problem and of course every engineering decision has trade offs. Github is a nice provider, no doubt. I have been using them for a number of my own personal repositories. Git of course has ways to address many of the issues we have addressed, but of course everything has strengths and weaknesses. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/35054405/ | |||
| title = <nowiki>Re: [Flightgear-devel] FlightGear and GitHub</nowiki> | |||
| author = <nowiki>Curtis Olson</nowiki> | |||
| date = Apr 30th, 2016 | |||
| added = Apr 30th, 2016 | |||
| script_version = 0.25 | |||
}} | |||
}} | |||
--> | |||
== Obtaining aircraft == | == Obtaining aircraft == | ||