Difference between revisions of "How to Help"

From FreeOrionWiki
Jump to: navigation, search
m
m (General)
(27 intermediate revisions by 5 users not shown)
Line 1: Line 1:
Free Orion is built and maintained entirely by volunteers.  Help from people with a wide variety of skills is needed to complete this project.
+
FreeOrion is built and maintained entirely by volunteers.  Help from people with a wide variety of skills is needed to complete the project.
  
  
* It's recommended that you familiarize yourself with the [[Requirements]].
+
==General==
  
* [[Programming_Work]]
+
[[Project Team Structure]] – [[Rules|Community Rules]]
  
* [[Graphics]]
+
==Design==
 +
 
 +
The easiest way to contribute when new to the project is to join in [http://freeorion.org/forum/viewforum.php?f=6 brainstorming] discussions on the forums.  It's recommended to familiarize oneself with the established and in-progress design [[Requirements]] and the most recent version of the program [http://sourceforge.net/project/showfiles.php?group_id=75752&package_id=111134 downloaded] or [[Compile|compiled]] from SVN.
 +
 
 +
Content creation is also requested.  Individual [https://github.com/freeorion/freeorion/blob/master/default/techs.txt techs], [https://github.com/freeorion/freeorion/blob/master/default/buildings.txt buildings], and [https://github.com/freeorion/freeorion/blob/master/default/specials.txt specials] are helpful, as well as discussion of the general thematic nature and structure of the [http://freeorion.org/forum/viewforum.php?f=15 tech tree] and other content. Here's a little info about [http://www.freeorion.org/forum/viewtopic.php?p=49968#p49968 designing Space Monsters].
 +
 
 +
The design process is discussed on the [[Game Design]] page.
 +
 
 +
==Programming==
 +
 
 +
Some of the issues on the [https://github.com/freeorion/freeorion/issues GitHub issues tracker] involve C++ or Python coding.
 +
 
 +
Testers may also be helpful, for bug reporting (see below) or help with bug fixing, even if not coders themselves.  If able to compile on various platforms to which programmers do not have access, and willing to assist a programmer with resolving bugs that appear only on your system, noting this in a bug report or on the forums is encouraged.
 +
 
 +
General programming information is available on the [[Programming]] page.
 +
 
 +
==Content Scripting==
 +
 
 +
Some of the issues on the [https://github.com/freeorion/freeorion/issues|GitHub issues tracker] involve python or FOCS scripting.
 +
 
 +
==Bug Reporting==
 +
 
 +
[https://github.com/freeorion/freeorion/issues Bug reporting] is appreciated.  Even better are patches to fix new or existing bugs.
 +
 
 +
==Play-testing==
 +
 
 +
While much is still incomplete, parts of FreeOrion are ready for
 +
[[Playtesting | Play-testing.]]
 +
 
 +
==Graphics and Art==
 +
 
 +
There is a list of [[Graphics Work]] available.
 +
 
 +
See the [http://www.freeorion.org/forum/viewtopic.php?f=10&t=2086 Guidelines to Contributing] on the forums.
 +
 
 +
==Music and Sound==
 +
 
 +
[[Audio]]
 +
 
 +
==Words==
 +
 
 +
===Translation===
 +
 
 +
[[Languages]]
 +
 
 +
===Documentation===
 +
 
 +
* [http://www.freeorion.org/index.php/V0.4_Quick_Play_Guide Keeping the quickplay guide up to date and helpful]
 +
* [http://www.freeorion.org/forum/viewtopic.php?f=15&t=6726 Adding articles to the 'Game Concepts' section of the 'Pedia]
 +
 
 +
===Writing===
 +
 
 +
[http://www.freeorion.org/forum/viewtopic.php?p=47729#p47729 'Pedia Species Write-ups]

Revision as of 06:29, 20 May 2017

FreeOrion is built and maintained entirely by volunteers. Help from people with a wide variety of skills is needed to complete the project.


General

Project Team StructureCommunity Rules

Design

The easiest way to contribute when new to the project is to join in brainstorming discussions on the forums. It's recommended to familiarize oneself with the established and in-progress design Requirements and the most recent version of the program downloaded or compiled from SVN.

Content creation is also requested. Individual techs, buildings, and specials are helpful, as well as discussion of the general thematic nature and structure of the tech tree and other content. Here's a little info about designing Space Monsters.

The design process is discussed on the Game Design page.

Programming

Some of the issues on the GitHub issues tracker involve C++ or Python coding.

Testers may also be helpful, for bug reporting (see below) or help with bug fixing, even if not coders themselves. If able to compile on various platforms to which programmers do not have access, and willing to assist a programmer with resolving bugs that appear only on your system, noting this in a bug report or on the forums is encouraged.

General programming information is available on the Programming page.

Content Scripting

Some of the issues on the issues tracker involve python or FOCS scripting.

Bug Reporting

Bug reporting is appreciated. Even better are patches to fix new or existing bugs.

Play-testing

While much is still incomplete, parts of FreeOrion are ready for Play-testing.

Graphics and Art

There is a list of Graphics Work available.

See the Guidelines to Contributing on the forums.

Music and Sound

Audio

Words

Translation

Languages

Documentation

Writing

'Pedia Species Write-ups