FGMEMBERS wiki Page deleted by the core group

[IAHM-COL]

Hi All. As of today the core developers took action and permanently deleted FGMEMBERS Flightgear Wiki Page
(technically, Hooray pull'd the trigger)

http://wiki.flightgear.org/FGMEMBERS



the original content of the page is posted below for reference

[IAHM-COL]

Code: Select all


'''FGMEMBERS''' is ...

* A Git repo of aircraft for FlightGear from various sources, using git sub modules
* A group of aircraft and scenery developers and contributors on github
* A fork of [[FGAddon]], which may also contain aircraft without explicit permission/support and collaboration from its original developers. An aircraft showing up in FGMEMBERS doesn't necessarily mean that the original developers endorse this.<ref>{{cite web |url=http://forum.flightgear.org/viewtopic.php?f=42&t=26043&hilit=parasitic&start=135#p241138 |title=Re: FGAddon vs. FGMEMBERS, bus factors etc. |author=IAHM-COL |date=Thu Apr 30, 2015 |publisher=FlightGear forum |accessdate=Fri Jun 12, 2015 }}</ref>
* Initiated by a single contributor, [https://github.com/IAHM-COL IAHM-COL].

== Repositories ==
The repositories are actually several repositories arranged under five groups.  The groups split content into aircraft, scenery and other data as well as content published under the [[GNU General Public License]] (GNU GPL) or under other licenses.<ref>{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=231382#p231382 |title=Cloning fgdata with GIT submodules |author=IAHM-COL |date=Thu Feb 05, 2015 |publisher=FlightGear forum |accessdate=Fri Jun 12, 2015 }}</ref><ref>{{cite web |url=https://forum.flightgear.org/viewtopic.php?p=246659#p246659 |title=FGMEMBERS: The Family |author=IAHM-COL |date=Thu Jun 11, 2015 |publisher=FlightGear forum |accessdate=Fri Jun 12, 2015 }}</ref>  Common other licenses are the Creative Commons licenses.

{| class="wikitable"
! Group !! Location !! Content !! Remarks
|-
| FGDATA || https://sourceforge.net/p/fgdata/submodules/ci/next/tree/
| Fork of the FGDATA repository
| Is this a part of FGMEMBERS?  Group maintained by IAHM-COL alone (Jun 2015).
|-
| FGMEMBERS || https://github.com/FGMEMBERS
| GPL licensed aircraft
|
|-
| FGMEMBERS-NONGPL || https://github.com/FGMEMBERS-NONGPL
| Non-GPL licensed aircraft.
| Group maintained by IAHM-COL alone (Jun 2015).
|-
| FGMEMBERS-SCENERY || https://github.com/FGMEMBERS-SCENERY
| GPL licensed scenery.
| Group maintained by IAHM-COL alone (Jun 2015).
|-
| FGMEMBERS-SCENERY-NONGPL || https://github.com/FGMEMBERS-SCENERY-NONGPL
| Non-GPL licensed scenery.
| Group maintained by IAHM-COL alone (Jun 2015).
|}

== How to use ==
=== Preparation ===
(Do this only once)

Clone the "submodules" fork of fgdata (1.3 GB):

<syntaxhighlight lang="bash">
git clone http://git.code.sf.net/p/fgdata/submodules fgdata
</syntaxhighlight>

{{Note|You need to redirect your fligthgear launcher to use the new fgdata directory obtained, as the $FG_ROOT. You will also need to match the version file with the version you are running. FGDATA with submodules is available for FG3.4 or later}}

==Init the submodules==

You can initialize only a few desired Aircraft [Really, as many as you want]. The update step will only install/update those submodules initialized. per example

<syntaxhighlight lang="bash">
cd fgdata
git submodule init Aircraft/777
git submodule init Aircraft/A320neo
git submodule init Aircraft/A330-200
git submodule init Aircraft/{767,Comet-J,Jumbolino,b1900d}  # Initializes a comma separated list of aircraft
git submodule init Aircraft/L*     #Initializes any aircraft with a name beginning with Capital L
git submodule init Aircraft/[Aa]*  #Initializes any aircraft with a name beginning with A or a
</syntaxhighlight>

=== Download or update Initialized aircraft ===

The command update will now allow you to either 1) Install, or 2) Update already installed aircraft on the fly. This command only fetches submodules already initialized, and thus allowing you to control very finely, which aircraft you are interested in obtaining for testing/flying purposes.

<syntaxhighlight lang="bash">
git submodule update
</syntaxhighlight>

Alternatively, you can specify which particular submdodule you want to update. Notice that this needs to be initialized previously

<syntaxhighlight lang="bash">
git submodule update Aircraft/767
</syntaxhighlight>

Everyonce in a while, (some of) the aircraft undergo updates, you can fastly update your installed aircraft, by simply doing

<syntaxhighlight lang="bash">
git pull
git submodule update
</syntaxhighlight>

=== Download/update ALL aircraft ===
{{Note|More than 700 aircraft or about 25 GB!}}

(At a speed of ~100kb/s, the entire collection of planes, from 14bis to 787-8 took about 6-7 hours!)

To obtain all the Aircraft hosted and developed in FGMEMBERS, simply initialize all the package and update.  To initialize all the Aircraft, and thus enabling installing all of them, use init command without a parameter.

<syntaxhighlight lang="bash">
cd fgdata
git submodule init
</syntaxhighlight>

Then, you can update the Initialized aircraf (which in this case means all)

<syntaxhighlight lang="bash">
git submodule update
</syntaxhighlight>

Importantly, once you have successfully obtained all the aircraft, fetching the newest code by the developers is very easy, fast, and efficient. You do not need to download the complete aircraft(s) again, since git will only download the newest code/changes, which is very convenient manner to maintain yourself updated

<syntaxhighlight lang="bash">
cd fgdata
git pull
git submodule update
</syntaxhighlight>

== Deinitialize/Deinstall an Aircraft ==

To deinstall any Aircraft, simply deinit the respective submodule. This will clear your disk space as well, but you will still be able to reinitialize at a later time

Example, deleting the Antonov-An-12 (if previously initialized/updated)

<syntaxhighlight lang="bash">
cd fgdata
git submodule deinit Aircraft/Antonov-An-12
</syntaxhighlight>

== Footnotes ==
{{appendix}}

== Related content ==
* http://forum.flightgear.org/viewtopic.php?f=28&t=25314&start=45#p234592

[[Category:Community]]

-->


[SHM]

Do you think that me posting the screenshots recently or making hooray's PM public was one of the cause of deletion?

[J Maverick 16]

All I hope is that they don't try to remove FGMEMBERS itself, I'm not so advanced to use SourceForge to submit my projects and download stuff.
Regards, Mav

[KL-666]

Really sad to see the pathological protectiveness getting into an obsession to destroy. Very childish this behaviour.

Kind regards, Vincent

[SHM]

@Maverick They will never be able to touch Fgmembers.

[KL-666]

Hooray comes up with a strange story about this on the other forum, claiming:

1) There is nothing meaningful on the page. Wrong: few posts back you can read there is usefull information.

2) There have not been made many changes on that page. What kind of logic is that? Do we now also have to constantly modify history books to keep them valid?

Kind regards, Vincent

[IAHM-COL]

I've been receiving quite a few PMs related to this, despite the deletion being self-explanatory to anyone looking at the revision log of the article, the talk page, the discussions on the forum, and the reason specified.

Note that there's no loss of data here at all.

Here's the PM I sent to a number of users who are also active over at the fgmembers forum:

The wiki article had been nominated for deletion for the last 7 months, all our/my offers to reinstate it, some made in public, many others made in private to various people, were not followed up on, including my most recent offer.

The article has basically been inactive since its inception, I am the one who started it originally and who spent some time to document fgmembers, despite not agreeing with some actions - it took literally 4+ months before fgmembers-affiliated users got involved to help add to the article.

Since, according to the revision logs, IAHM-COL obviously spent some time to add to the article at some point, I don't want to see his work going to the wastebin or the deletion to be misinterpreted, so if they'd like to recreate the article elsewhere, I am sending you the contents via a pastebin link, it should be straightforward to preserve that article via github or some other 3rd party resource (e.g. Peter Brendt's jabberwocky server at bluehost): http://pastebin.com/tJSHi2FG

Note that the deletion of the article is basically a "NOP", because it wasn't really being used or useful at all, there's currently tons of misinformation being spread by various users over at the jbw forum, but anybody familiar with the wiki article, and the wiki in general, will agree that this is just regular housekeeping, just like other inactive/outdated and unmaintained articles need to be reviewed, and are routinely nominated for deletion before they are deleted.

In addition, this action was mine alone - this is not part of some kind of "master plan" as some people make it sound, forum moderators (and even other wiki admins) were not involved in my decision to delete this particular article, simply because I started it and I bootstrapped it, so I didn't feel compelled to consult back with others.

[IAHM-COL]

I request this page to be reinstated in the FlightGear Wki, where it belongs.
It contains very important information on how you set up FGDATA next to work with submodules and give users a better way of fetching the aircraft hosted in FGMEMBERS.

It is absurd than on one side you claim "Hijacking" of the mumble -- an unfounded allegation. And for the other side, you act this way towards other people's work.

Thanks

[J Maverick 16]

I'll be updating all my wiki pages then...
Regards, Mav