20,741
edits
FlightGear Git: splitting FGData: Difference between revisions
Jump to navigation
Jump to search
→Reasons to split fgdata
No edit summary |
|||
| Line 1: | Line 1: | ||
{{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: | ||
== News / Status (03/2015) == | |||
{{FGCquote | |||
|I am going to commence reducing FGDATA this weekend. The reasons for that<br/> | |||
action have been discussed here and on the forum in epic detail, so I won't<br/> | |||
repeat them.<br/> | |||
<br/> | |||
The result will be a new and much smaller git repository and it will only<br/> | |||
have the c172p and the ufo remaining.<br/> | |||
<br/> | |||
To avoid any unnecessary extra work, I will temporarily remove all<br/> | |||
contributors with write access except 2 or three admins on Friday afternoon<br/> | |||
(Central European Time Zone).<br/> | |||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33546900/ | |||
|title=<nowiki>[Flightgear-devel] FGData size reduction</nowiki> | |||
|author=<nowiki>Torsten Dreyer</nowiki> | |||
|date=<nowiki>2015-03-05</nowiki> | |||
}} | |||
}} | |||
{{FGCquote | |||
|Next, I'll do a initial commit of the base package aircraft to fgaddon/svn.<br/> | |||
Following that, I create a new git repo for a smaller git fgdata and push<br/> | |||
it to sourceforge.<br/> | |||
Finally, we re-add contributors with push permission.<br/> | |||
<br/> | |||
If anything goes wrong, the original fgdata will remain intact and can<br/> | |||
serve as a fallback. | |||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33546900/ | |||
|title=<nowiki>[Flightgear-devel] FGData size reduction</nowiki> | |||
|author=<nowiki>Torsten Dreyer</nowiki> | |||
|date=<nowiki>2015-03-05</nowiki> | |||
}} | |||
}} | |||
== Reasons to split fgdata == | == Reasons to split fgdata == | ||
| Line 35: | Line 71: | ||
* Clone the repository from a faster mirror, such as the mapserver. | * Clone the repository from a faster mirror, such as the mapserver. | ||
It should further be noticed that git's merging and update algoritms are sufficiently efficient to deal with our ever increasing repository, so no immediate problems are to be expected in this area. Given these considerations, it appears that there are sufficient alternatives to circumvent the initial clone problem, and that the size of the git repository as such poses no immediate problem. That said, there are a number of additional reasons that make it desireable to split the fgdata repository in smaller, more manageable chunks. | It should further be noticed that git's merging and update algoritms are sufficiently efficient to deal with our ever increasing repository, so no immediate problems are to be expected in this area. Given these considerations, it appears that there are sufficient alternatives to circumvent the initial clone problem, and that the size of the git repository as such poses no immediate problem. That said, there are a number of additional reasons that make it desireable to split the fgdata repository in smaller, more manageable chunks. | ||
== Options == | == Options == | ||