6,566
edits
FlightGear Git: splitting FGData: Difference between revisions
Jump to navigation
Jump to search
FlightGear Git: splitting FGData (view source)
Revision as of 20:42, 22 September 2015
, 22 September 2015Added Johan's historical box to the top to avoid confusion.
(Added Johan's historical box to the top to avoid confusion.) |
|||
| Line 1: | Line 1: | ||
{{historical | |||
| reason = This split had been discussed for many years and finally begun in September 2014. See [[FlightGear Newsletter September 2014#Aircraft moved to SVN]]. | |||
| talk = Talk:FlightGear Git: splitting fgdata#Keeping the page though it is soon outdated | |||
| date = 27 December 2014 | |||
| nocat = 1 <!-- As this is an example --> | |||
}} | |||
{{Project Issues}} | {{Project Issues}} | ||
After much discussion on the mailing list, it was decided to put the existing attempt to split FGdata on hold until further notice. The main reason for postponing the split was that, while it was considered a well intended initiative, the end result of the splitting process itself left the FlightGear fgdata project in a less than desirable state. For this reason, before another splitting attempt is to be undertaken, the pro's and con's of each step should be carefully evaluated. This article discusses some of our options and will formulate a plan of approach that can be presented to -and discussed in further depth- on the developers mailing list. Several reasons have been put forth to split fgdata: | After much discussion on the mailing list, it was decided to put the existing attempt to split FGdata on hold until further notice. The main reason for postponing the split was that, while it was considered a well intended initiative, the end result of the splitting process itself left the FlightGear fgdata project in a less than desirable state. For this reason, before another splitting attempt is to be undertaken, the pro's and con's of each step should be carefully evaluated. This article discusses some of our options and will formulate a plan of approach that can be presented to -and discussed in further depth- on the developers mailing list. Several reasons have been put forth to split fgdata: | ||