FlightGear Newsletter March 2015: Difference between revisions

Jump to navigation Jump to search
Finished editing now
mNo edit summary
(Finished editing now)
Line 28: Line 28:


== Project restructuring ==
== Project restructuring ==
Due to two recent developments, large parts of the FlightGear project are going to be moving.  The first is the announcement that Gitorious.org will shut down in May this year ([https://about.gitlab.com/2015/03/03/gitlab-acquires-gitorious/ read more]) and that Google Code will shut down in 2016 ([http://google-opensource.blogspot.co.uk/2015/03/farewell-to-google-code.html read more]).  This means that all the source code (SimGear and FlightGear), the bug tracker, and [[TerraSync]]{{clarify}} are moving.  In addition, just previous to these developments, [[fgdata]] was split, see [[#fgdata split|below]] for details.
Due to two recent developments, large parts of the FlightGear project are moving.  The first is the announcement that Gitorious.org will shut down in May this year ([https://about.gitlab.com/2015/03/03/gitlab-acquires-gitorious/ read more]) and the second is that Google Code will shut down in 2016 ([http://google-opensource.blogspot.co.uk/2015/03/farewell-to-google-code.html read more]).  These developments have affected the source code (SimGear and FlightGear), bug tracker, and [[TerraSync]] SVN repository are moving.  In addition, just previous to these developments, [[fgdata]] was split (see [[#fgdata split|below]] for details).


All repositories of the FlightGear project have been synchronized to [http://sourceforge.net/p/flightgear/_list/git SourceForge.net]<ref>{{cite web
All repositories of the FlightGear project have been synchronized to [http://sourceforge.net/p/flightgear/_list/git SourceForge.net]<ref>{{cite web
Line 40: Line 40:
Example for SimGear with read-only access:
Example for SimGear with read-only access:
<syntaxhighlight lang="bash">
<syntaxhighlight lang="bash">
git remote set-url origin git://git.code.sf.net/p/flightgear/simgear
git remote set-url origin <protocol>git.code.sf.net/p/flightgear/<sub-project>
</syntaxhighlight>
</syntaxhighlight>


Example for FlightGear source with read/write access:
<code><nowiki><protocol></nowiki></code> can be either of <code><nowiki>git://</nowiki></code> (read-only access) or <code><nowiki>http://</nowiki></code> (read/write access). See http://sourceforge.net/p/flightgear/_list/git for a list of what <code><nowiki><sub-project></nowiki></code> should (they should also be lowercase).
 
Example for [[SimGear]] with read/write access:
<syntaxhighlight lang="bash">
<syntaxhighlight lang="bash">
git remote set-url origin http://git.code.sf.net/p/flightgear/flightgear
git remote set-url origin http://git.code.sf.net/p/flightgear/simgear
</syntaxhighlight>
</syntaxhighlight>
{{Note|HTTPS access is no longer supported; you will have to change the relevant URLs.}}
The bug tracker has moved to http://sourceforge.net/p/flightgear/codetickets/<ref>{{cite web
|url    = http://sourceforge.net/p/flightgear/mailman/message/33600886
|title  = <nowiki>[Flightgear-devel] Bugtracker moving to sourceforge</nowiki>
|author = Torsten Dreyer
|date  = 2015-03-16
}}</ref>. All old issues/feature requests have been preserved.  The wiki template {{tl|Issue}} has been updated ([http://wiki.flightgear.org/index.php?title=Template:Issue&diff=82555&oldid=72743 diff]).
TerraSync is yet to be moved as of March 18.


Several (but not all) of the [[:Category:Git|Git related articles]] on the wiki have been updated, including [[FlightGear Git: data developers]].
Several (but not all) of the [[:Category:Git|Git related articles]] on the wiki have been updated, including [[FlightGear Git: data developers]].
Line 70: Line 61:
# Upload your public key.
# Upload your public key.
# Send your SourceForge username to Curt, Clément, James, or Torsten D, stating which repo(s) you want to be re-added to.
# Send your SourceForge username to Curt, Clément, James, or Torsten D, stating which repo(s) you want to be re-added to.
The bug tracker has moved to http://sourceforge.net/p/flightgear/codetickets/<ref>{{cite web
|url    = http://sourceforge.net/p/flightgear/mailman/message/33600886
|title  = <nowiki>[Flightgear-devel] Bugtracker moving to sourceforge</nowiki>
|author = Torsten Dreyer
|date  = 2015-03-16
}}</ref>. All old issues/feature requests have been preserved.  The wiki template {{tl|Issue}} has been updated ([http://wiki.flightgear.org/index.php?title=Template:Issue&diff=82555&oldid=72743 diff]).
TerraSync is yet to be moved as of March 22.


=== FGData split ===
=== FGData split ===
Line 190: Line 190:
== Scenery Corner ==
== Scenery Corner ==
=== Verona Villafranca 2D layout released ===
=== Verona Villafranca 2D layout released ===
[[User:Elgaton|elgaton]] has released the complete 2D layout for [[LIPX]]; the work is going to be submitted to the Airport Scenery Gateway at the end of March for inclusion in X-Plane and FlightGear. A scenery build can be downloaded from the [http://forum.flightgear.org/viewtopic.php?f=5&t=21576 official development thread on the forum]. 3D buildings will be added in the coming months.
{{usr|Elgaton}} has released the complete 2D layout for the [[Verona Villafranca Airport]] (LIPX).  It is going to be submitted to the Airport Scenery Gateway at the end of March for inclusion into X-Plane and FlightGear. See the [http://forum.flightgear.org/viewtopic.php?f=5&t=21576 forum thread] for download links. 3D buildings will be added in the coming months.
<gallery mode="packed">
<gallery mode="packed">
File:LIPX-RC2-panorama.png|The airport and the surrounding area.
LIPX-RC2-panorama.png|Airport and the surrounding area
File:LIPX-RC2-top.png|Top view.
LIPX-RC2-top.png|Top view
File:LIPX-RC2-apron.png|The apron now features up-to-date stands.
LIPX-RC2-apron.png|The apron now features up-to-date stands
File:LIPX-B-CRJ700.png|Holding short at B in a CRJ-700 (at night).
LIPX-B-CRJ700.png|Holding short at in the [[Bombardier CRJ700 series|CRJ700]] at night
</gallery>
</gallery>


== Community News ==
== Community News ==
=== FlightGear Space Program ===
=== FlightGear Space Program ===
[[File:Fgspbadge.png|thumb|FGSP Cosmonaut Badge "The Owl"]]
[[File:Fgspbadge.png|thumb|FGSP Cosmonaut Badge "The Owl"]]
[[File:spacetripready.png|link=FlightGear space program]]
[[File:spacetripready.png|link=FlightGear space program]]


Now is your time to become official cosmonaut of The FlightGear Space Program. Just downloading the famous '''[[Space Shuttle]]'''  that has been largely reworked, and select any of the available [[FlightGear_space_program_missions|missions]]. Report your succesfull orbit flight tracker screenie and you'll receive a custom badge of The FlightGear Space Program.
Now is your time to become official cosmonaut of The FlightGear Space Program. Just download the famous [[Space Shuttle]] and select any of the available [[FlightGear space program missions|missions]]. Report your succesfull orbit flight tracker screenie and you'll receive a custom badge of the FlightGear Space Program.


The Space Shuttle can be downloaded from {{repo link|site=gith|proj=herbyw/antonov-aircrafts|view=tree|text=the GitHub repository}} in either a ZIP file or by cloning.
The Space Shuttle can be downloaded from {{repo link|site=gith|proj=HerbyW/Antonov-Aircrafts|text=the GitHub repository}} either in a ZIP file or by cloning.


As an add-on also you can fly our Special Cargo Transport Missions with the heavily updated [[Antonov_An-12|An-12]], [[Antonov_An-22|An-22]], and [[An-225]] (mission transport variants).
As an add-on also you can fly our Special Cargo Transport Missions with the heavily updated [[Antonov An-12|An-12]], [[Antonov An-22|An-22]], and [[An-225]].


''Find out more about space flight in FlightGear at [[FlightGear space program]] …''
''Find out more about space flight in FlightGear at [[FlightGear space program]] …''
Line 229: Line 228:


=== FlightGear logos ===
=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (for example hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos.  And if you have some art skills, please don't hesitate to contribute with your own design creations.
If you want some graphic elements for your FlightGear-related site (for example a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos.  And if you have some art skills, please don't hesitate to contribute with your own design creations.


=== Screenshots ===
=== Screenshots ===
The FlightGear project always needs screenshots for the website, which show features that were added since the last release.  These shots should be of good quality, especially in content and technical image properties.  It is therefore recommended to use the best viable filter settings ([[antialiasing]], texture sharpening, etc.).  More info at [[Howto:Make nice screenshots]].
The FlightGear project always needs screenshots, which show features that were added since the last release.  These should be of good quality, especially in content and technical image properties.  It is therefore recommended to use the best viable filter settings ([[antialiasing]], texture sharpening, etc.).  More info at [[Howto:Make nice screenshots]].


[[Category:FlightGear Newsletter|2015 03]]
[[Category:FlightGear Newsletter|2015 03]]
[[Category:Changes after 3.4]]
[[Category:Changes after 3.4]]

Navigation menu