PioneerWiki - User contributions [en]

User:Ae-2222

2012-10-15T08:58:16Z

Ae-2222:

=== Things I can review ===

*Science-y/Algorithmic things

:*Procedural things - Terrain, sysgen, fractal math etc.

:*Shaders

etc.

----

==== Temporary IRC logs discussing design issues around Brianetta's idea concerning a way to solve the distance closure (interception) problem with Newtonian flight ====

[http://pastebin.com/Z8hdKwpL 1]
[http://pastebin.com/E2Q7FEjt 2]

Some much older discussion about combat/FTL that was archived for another person, that still isn't summarised in the wiki [http://pastebin.com/Re20q6rU 3]
----

[[User_talk:Ae-2222|My talk page ]] - This is a Pioneer wiki, so talk pages should be used freely and are a useful way to get in touch if you are not on IRC and it's too minor/person specific for the Mailing List - feel free to leave messages there (this goes for anyone with general questions about Pioneer's terrain or any areas I've worked on, as well)

Mods

2012-10-08T12:49:12Z

Ae-2222: Move mod compilations to separate table.

== Available Mods ==

=== How to install Mods ===

Since Alpha 22 Pioneer has had support for modding. This is done by allowing core game data to be added to or overwritten by data in your userdir (that is, <code>'My Docs/Pioneer'</code> for Windows, <code>'~/.pioneer'</code> for Linux, and <code>'~/Library/Application Support/Pioneer'</code> for OSX).

You have two options for adding files:

* Put them in userdir/data. Any files in this dir will be visible to the game as part of its normal data/ dir.
* Put them in a zip file in userdir/mods. The zip file contents will be visible to the game as part of its normal data/ dir.

If a file in your userdir (data or mod) conflicts with one in the core datadir, your copy will be used. You can use this fact to replace core files.

This mechanism can be used for any file under data/ - ships, models, systems, music, fonts, textures, whatever.

== List of known Mods ==
{| class="wikitable"
|+Current known Mod Packages
|-
!Mod Name
!Mod Description
!Author(s)
!Version
!Tested with Pioneer*
!Size
!Download link
|-
|Graveyard
|Example of bundling multiple files in a mod. Adds a custom system "Graveyard" (up and to the right of Sol) and a script that does something when you jump there.
|[[User:RobN|RobN]]
|1.0
|Alpha22
|1kb
|[http://eatenbyagrue.org/f/pioneer/graveyard.zip graveyard.zip]
|-
|RedSol
|Example of replacing a core file. Replaces the system def for Sol with one that has a red star.
|[[User:RobN|RobN]]
|1.0
|Alpha22
|1kb
|[http://eatenbyagrue.org/f/pioneer/redsol.zip redsol.zip]
|-
|Moon Heightmap
|Higher res heightmap which replaces the 2mb default heightmap.
|Unknown
|1.0
|Alpha26
|33Mb
|[http://wikisend.com/download/359748/moon-hi-res-heightmap.zip moon-hi-res-heightmap.zip]
|-
|Apollo LEM Lunar orbit save file for Alpha26 - Updated with Ultra Low fuel LEM landing challenge (-w- cargo to jettison)
|3 saves with Lunar lander in unpowered orbit over moon with low fuel(requires HighRes.Moon_Apollo.LEM.a26Mod)
|baobobafet
|1.0
|Alpha26
|520kb
|[http://www.mediafire.com/?sy5d6i4n8vz10c4]
|-
|Not really a Mod - This is for people who have - or are familiar with either Xpadder, 3D Pro Joystick or the G-13 Gameboard.
|Extreme 3D Pro Joystick Xpadder profile and G-13 gameboard Basic Template - printable key & joystick button reference. Version 3 update.
|Baobobafet
|1.0
|Alpha26
|4490kb
|[https://docs.google.com/open?id=0B5dK9aniVGUnM09GRU1qVFJWemM] [http://www.mediafire.com/?ncnh6bpdvna34n2]
|
|}

*'' Version number represents what the module was tested/built against. There is no guarantee that it will work for later versions.''

== List of known Mod Compilations ==

{| class="wikitable"
|+Current known Mod Compilation Packages
|-
!Mod Name
!Mod Description
!Author(s)
!Version
!Tested with Pioneer*
!Size
!Download link
|-
|HiRes Moon & Apollo LEM Mod
|High res Moon heightmap & flyable Apollo Eagle Lander with docs & nav maps.
|Unknown
|1.0
|Alpha26
|35.3Mb
|[https://docs.google.com/open?id=0B4TOJEZxkYiVbUllYTdKS1RwaEU]
|
|}

*'' Version number represents what the module compilation was tested/built against. There is no guarantee that it will work for later versions.''

'''''The who/when/where for mod storage/testing/package compilation is still to be established. As with all things concerning Pioneer it is up to interested parties to resolve this. There is the beginnings of a discussion on the [[Talk:Mods|discussion page]] as not everyone is on the mailing list yet (another could be started on a specific task page if anyone wants to). You need to register to edit pages and contribute.'''''

Mods

2012-10-08T12:29:07Z

Ae-2222: Add mod version number to mod table.

== Available Mods ==

=== How to install Mods ===

Since Alpha 22 Pioneer has had support for modding. This is done by allowing core game data to be added to or overwritten by data in your userdir (that is, <code>'My Docs/Pioneer'</code> for Windows, <code>'~/.pioneer'</code> for Linux, and <code>'~/Library/Application Support/Pioneer'</code> for OSX).

You have two options for adding files:

* Put them in userdir/data. Any files in this dir will be visible to the game as part of its normal data/ dir.
* Put them in a zip file in userdir/mods. The zip file contents will be visible to the game as part of its normal data/ dir.

If a file in your userdir (data or mod) conflicts with one in the core datadir, your copy will be used. You can use this fact to replace core files.

This mechanism can be used for any file under data/ - ships, models, systems, music, fonts, textures, whatever.

== List of known Mods ==
{| class="wikitable"
|+Current known Mod Packages
|-
!Mod Name
!Mod Description
!Author
!Version
!Tested with Pioneer*
!Size
!Download link
|-
|Graveyard
|Example of bundling multiple files in a mod. Adds a custom system "Graveyard" (up and to the right of Sol) and a script that does something when you jump there.
|[[User:RobN|RobN]]
|1.0
|Alpha22
|1kb
|[http://eatenbyagrue.org/f/pioneer/graveyard.zip graveyard.zip]
|-
|RedSol
|Example of replacing a core file. Replaces the system def for Sol with one that has a red star.
|[[User:RobN|RobN]]
|1.0
|Alpha22
|1kb
|[http://eatenbyagrue.org/f/pioneer/redsol.zip redsol.zip]
|-
|Moon Heightmap
|Higher res heightmap which replaces the 2mb default heightmap.
|Unknown
|1.0
|Alpha26
|33Mb
|[http://wikisend.com/download/359748/moon-hi-res-heightmap.zip moon-hi-res-heightmap.zip]
|-
|HiRes Moon & Apollo LEM Mod
|High res Moon heightmap & flyable Apollo Eagle Lander with docs & nav maps.
|Unknown
|1.0
|Alpha26
|35.3Mb
|[https://docs.google.com/open?id=0B4TOJEZxkYiVbUllYTdKS1RwaEU]
|-
|Apollo LEM Lunar orbit save file for Alpha26 - Updated with Ultra Low fuel LEM landing challenge (-w- cargo to jettison)
|3 saves with Lunar lander in unpowered orbit over moon with low fuel(requires HighRes.Moon_Apollo.LEM.a26Mod)
|baobobafet
|1.0
|Alpha26
|520kb
|[http://www.mediafire.com/?sy5d6i4n8vz10c4]
|-
|Not really a Mod - This is for people who have - or are familiar with either Xpadder, 3D Pro Joystick or the G-13 Gameboard.
|Extreme 3D Pro Joystick Xpadder profile and G-13 gameboard Basic Template - printable key & joystick button reference. Version 3 update.
|Baobobafet
|1.0
|Alpha26
|4490kb
|[https://docs.google.com/open?id=0B5dK9aniVGUnM09GRU1qVFJWemM] [http://www.mediafire.com/?ncnh6bpdvna34n2]
|
|}

*'' Version number represents what the module was tested/built against. There is no guarantee that it will work for later versions.''

'''''The who/when/where for mod storage/testing/package compilation is still to be established. As with all things concerning Pioneer it is up to interested parties to resolve this. There is the beginnings of a discussion on the [[Talk:Mods|discussion page]] as not everyone is on the mailing list yet (another could be started on a specific task page if anyone wants to). You need to register to edit pages and contribute.'''''

Talk:Mods

2012-09-24T10:30:24Z

Ae-2222:

Hello:)

Eventually, interested parties will need to figure out where/who/how to deal with things related to mods (as well as any other part of Pioneer).

This discussion page ''and possibly a task page'' could be used for coordinating specific things with those not on IRC (the mailinglist is another option, but wiki allows structured multi-page discussion that people can follow easily).

Just click edit at top and type discussion here. There's a preview, but if you make a mistake or anything you can just edit again. I'll start it off:)

----

===Where to host files===

* Sourceforge is an option. They have both bandwidth and persistence of uploads. Pioneer already uses sourceforge for downloads.

----

===Who to manage hosting/check files/maintain wiki pages/create packages of compatible mods===

*

----

Talk:Mods

2012-09-24T08:12:02Z

Ae-2222:

Hello:)

Eventually, interested parties will need to figure out where/who/how to deal with things related to mods (as well as any other part of Pioneer).

This discussion page ''and possibly a task page'' could be used for coordinating specific things with those not on IRC (the mailinglist is another option, but wiki allows structured multi-page discussion that people can follow easily).

Just click edit at top and type discussion here. There's a preview, but if you make a mistake or anything you can just edit again. I'll start it off:)

----

===Where to host files===

Ae: Sourceforge is an option. They have both bandwidth and persistence of uploads. Pioneer already uses sourceforge for downloads.

----

===Who to manage hosting/check files/maintain wiki pages/create packages of compatible mods===

----

Talk:Mods

2012-09-24T08:09:57Z

Ae-2222: Start discussion page about mods.

Hello:)

Eventually, interested parties will need to figure out where/who/how to deal with things related to mods (as well as any other part of Pioneer).

This discussion page ''and possibly a task page'' could be used for coordinating specific things with those not on IRC (the mailinglist is another option, but wiki allows structured multi-page discussion that people can follow easily).

Just click edit at top and type discussion here. There's a preview, but if you make a mistake or anything you can just edit again. I'll start it off:)

----

===Where to host files===

Ae: Sourceforge is an option. They have both bandwidth and persistence of uploads. Pioneer already uses sourceforge for downloads.

----

===Who to manage hosting/check files/maintain wiki pages/create packages of compatible mods===

Mods

2012-09-24T06:50:30Z

Ae-2222: Added temporary link for moon hi res heightmap.

Getting started

2012-09-13T12:01:26Z

Ae-2222:

'''To Create a new page:''' type the URL of the page you would like to create e.g. http://pioneerwiki.com/wiki/Mods . You will then be taken to an empty page. Click the "edit this page" link and write in the edit box and save. Keep in mind there is a ''preview button'' and remember that ''content can be changed as often as you like''. Headings, italicisation and other effects are achieved simply by placing special characters around text e.g. use two apostrophes on either side to italicise. There is a short tutorial on the basics [http://how-to.wikia.com/wiki/How_to_use_basic_wiki_markup_to_format_on_Wikihowto_and_other_MediaWiki_sites here] and a comprehensive list of wiki formatting [http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet here].

'''This is ''your'' Pioneer wiki, and not Wikipedia!'''

Be free with using talk pages to organise and collaborate.

Things this wiki might potentially be used for:
* Tutorials, FAQs, detailed proposals of ideas, summaries of discussions, screenshots/pioneer video links, lists of useful resources by topic (coding, creative stimulus), personal pages containing notes/to-do lists and other material related to pioneer, task status pages for focus groups in relation to translating, mod packaging etc., introductory briefings for new contributors by area. In addition to the usual project documentation.

[[Sandbox|Sandbox page]] for playing around with editing.

----

[http://www.youtube.com/watch?v=xvLIR1FbC2Y&feature=share&list=PL93B4061F73606FE6 Youtube - simple wiki editing tutorial]

[http://youtu.be/pQJs3MQFgKA Youtube - tutorial showing how simple it is to create a table or chart]

Getting started

2012-09-13T11:56:01Z

Ae-2222: Correct video.

Getting started

2012-09-13T11:53:11Z

Ae-2222: Add link to youtube tutorial.

'''To Create a new page:''' type the URL of the page you would like to create e.g. http://pioneerwiki.com/wiki/Mods . You will then be taken to an empty page. Click the "edit this page" link and write in the edit box and save. Keep in mind there is a ''preview button'' and remember that ''content can be changed as often as you like''. Headings, italicisation and other effects are achieved simply by placing special characters around text e.g. use two apostrophes on either side to italicise. There is a short tutorial on the basics [http://how-to.wikia.com/wiki/How_to_use_basic_wiki_markup_to_format_on_Wikihowto_and_other_MediaWiki_sites here] and a comprehensive list of wiki formatting [http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet here].

'''This is ''your'' Pioneer wiki, and not Wikipedia!'''

Be free with using talk pages to organise and collaborate.

Things this wiki might potentially be used for:
* Tutorials, FAQs, detailed proposals of ideas, summaries of discussions, screenshots/pioneer video links, lists of useful resources by topic (coding, creative stimulus), personal pages containing notes/to-do lists and other material related to pioneer, task status pages for focus groups in relation to translating, mod packaging etc., introductory briefings for new contributors by area. In addition to the usual project documentation.

[[Sandbox|Sandbox page]] for playing around with editing.

----

[http://www.youtube.com/watch?v=qbhCmnjg3Ys&feature=share&list=PL93B4061F73606FE6 Youtube - simple wiki editing tutorial]

User:Ae-2222

2012-09-13T11:36:40Z

Ae-2222: Start Ae-2222 user page.

=== Things I can review ===

* Science-y/Algorithmic things

* Procedural things - Terrain, sysgen, fractal math etc.

* Shaders

etc.

----

[[User_talk:Ae-2222|My talk page ]] - This is a Pioneer wiki, so talk pages should be used freely and are a useful way to get in touch if you are not on IRC and it's too minor/person specific for the Mailing List - feel free to leave messages there

User talk:Ae-2222

2012-09-13T11:26:05Z

Ae-2222: Created page with "'''Leave messages here:)''' ==== Person 1 ==== ==== Person 2 ===="

'''Leave messages here:)'''

==== Person 1 ====

==== Person 2 ====

Pioneer Wiki

2012-09-07T09:05:43Z

Ae-2222: Add link designworkflow.

Pioneer is a space adventure game set in the milkyway galaxy at the turn of the 31st century.

The game is open-ended, and you are free to explore the millions of star systems in the game. You can land on planets, slingshot past gas giants, and burn yourself to a crisp flying between binary star systems.

When Pioneer is finished there will be many ways to make ends meet: piracy, smuggling, bounty-hunting, mining, doing missions for the various factions fighting for power, freedom or self-determination

----
Please make this wiki nice. Copy the content over from the [https://github.com/pioneerspacesim/pioneer/wiki GitHub wiki], add stuff about mods, dev, whatever. Be awesome! [[Getting started|How to get started]].

And write a nice front page and get rid of this, ok? :)

Pioneer is brung to you by a flock of [https://github.com/pioneerspacesim/pioneer/blob/master/AUTHORS.txt opensource beardy-weirdies], and is [http://www.gnu.org/licenses/gpl.html Free Software]

==Site Map==

===General===
* [[FAQ]]
* [[Mods]]
* [[In the media]]

===Development===
* [[Our Development Model]]
* [[Design_Workflow|Our Design and Project Management Workflow]]

Design Workflow

2012-09-07T07:45:01Z

Ae-2222:

Table thingy outlining the appropriate places for use at different stages of the workflow for both design and resolution of issues. Experimenting with tables:). Still WIP, feel free to reformat/fix/make clearer.

{| class="wikitable"
|-
! '''Stage 1.
Informally bounce ideas off people to see if they are worth bringing to the attention of the entire community''' (purely optional)
! '''Stage 2.
Put things up for discussion'''
! '''Stage 3.
Detailed discussion'''
! '''Stage 4.
Documenting outcomes (When a solution has been found or discussion has slowed down/stalled and is unlikely to resume in the near future)'''
|-
| '''IRC''' - the most feedback. Engine room of opensource projects and used for collaboration ''exlusively'' by a lot of contributors.
|| '''Issue tracker''' - is focused enough to allow immediate solution. ''Workflow ends here.''
|| '''Mailing list''' and possibly a '''pirate pad''' for issues that are too extensive or benefit from realtime or re-structurability aspects.
|| '''Wiki'''
|-
| '''Forums'''
|| '''Mailing list''' - Discussion of project policy or wider design issues
|| It's possible to use wiki pages like a piratepad
|| Multiple issues in '''Issue tracker''' - ''focused'' and ''implementable'' tasks
|-
|
|| Detailed proposal on the '''Wiki''' then linked to the '''Mailing list'''
||
||
|}

The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are ''available only through Github/mailinglist'' or forum for collaboration and new contributors only observe ''Github or the Wiki''. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not ''visible to the critical audience'', it ''disturbs the process of reviewing'' a Pull Request or discussing the present issue, and it ''makes things hard to find'' later.

'''''If a new Policy or Design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)'''''

Design Workflow

2012-09-07T07:36:48Z

Ae-2222:

Table thingy of Workflow for design/resolution of issues. Experimenting with tables:). Still WIP, feel free to reformat/fix/make clearer.

{| class="wikitable"
|-
! '''Stage 1.
Informally bounce ideas off people to see if they are worth bringing to the attention of the entire community''' (purely optional)
! '''Stage 2.
Put things up for discussion'''
! '''Stage 3.
Detailed discussion'''
! '''Stage 4.
Documenting outcomes (When a solution has been found or discussion has slowed down/stalled and is unlikely to resume in the near future)'''
|-
| '''IRC''' - the most feedback. Engine room of opensource projects and used for collaboration ''exlusively'' by a lot of contributors.
|| '''Issue tracker''' - is focused enough to allow immediate solution. ''Workflow ends here.''
|| '''Mailing list''' and possibly a '''pirate pad''' for issues that are too extensive or benefit from realtime or re-structurability aspects.
|| '''Wiki'''
|-
| '''Forums'''
|| '''Mailing list''' - Discussion of project policy or wider design issues
|| It's possible to use wiki pages like a piratepad
|| Multiple issues in '''Issue tracker''' - ''focused'' and ''implementable'' tasks
|-
|
|| Detailed proposal on the '''Wiki''' then linked to the '''Mailing list'''
||
||
|}

The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are ''available only through Github/mailinglist'' or forum for collaboration and new contributors only observe ''Github or the Wiki''. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not ''visible to the critical audience'', it ''disturbs the process of reviewing'' a Pull Request or discussing the present issue, and it ''makes things hard to find'' later.

'''''If a new Policy or Design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)'''''

Design Workflow

2012-09-07T07:35:46Z

Ae-2222:

Table thingy of Workflow for design/resolution of issues. Experimenting with tables:). Still WIP, feel free to reformat/fix/make clearer.

{| class="wikitable"
|-
! '''Stage 1.
Informally bounce ideas off people to see if they are worth bringing to the attention of the entire community''' (purely optional)
! '''Stage 2.
Put things up for discussion'''
! '''Stage 3.
Detailed discussion'''
! '''Stage 4.
Documenting outcomes (When a solution has been found or discussion has slowed down/stalled and is unlikely to resume in the near future)'''
|-
| '''IRC''' - the most feedback. Engine room of opensource projects and used for collaboration ''exlusively'' by a lot of contributors.
|| '''Issue tracker''' - is focused enough to allow immediate solution. ''Workflow ends here.''
|| '''Mailing list''' and possibly a '''pirate pad''' for issues that are too extensive or benefit from realtime or re-structurability aspects.
|| '''Wiki'''
|-
| '''Forums'''
|| '''Mailing list''' - Discussion of project policy or wider design issues
|| It's possible to use wiki pages like a piratepad
|| Multiple issues in '''Issue tracker''' - ''focused'' and ''implementable'' tasks
|-
|
|| Detailed proposal on the '''Wiki''' then linked to the '''Mailing list'''
||
||
|}

The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are ''available only through Github/mailinglist'' or forum for collaboration and new contributors only observe ''Github or the Wiki''. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not ''visible to the critical audience'', it ''disturbs the process of reviewing'' a Pull Request or discussing the present issue, and it ''makes things hard to find'' later.

'''''If a new Policy/design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)'''''

Design Workflow

2012-09-07T07:25:27Z

Ae-2222:

Table thingy of Workflow for design/resolution of issues. Experimenting with tables:). Still WIP, feel free to reformat/fix/make clearer.

{| class="wikitable"
|-
! '''Stage 1.
Informally bounce ideas off people to see if they are worth bringing to the attention of the entire community''' (purely optional)
! '''Stage 2.
Put things up for discussion'''
! '''Stage 3.
Detailed discussion'''
! '''Stage 4.
Documenting outcomes (When a solution has been found or discussion has slowed down/stalled and is unlikely to resume in the near future)'''
|-
| '''IRC''' - the most feedback. Engine room of opensource projects and used for collaboration ''exlusively'' by a lot of contributors.
|| '''Issue tracker''' - is focused enough to allow immediate solution. ''Workflow ends here.''
|| '''Mailing list''' and possibly a '''pirate pad''' for issues that are too extensive or benefit from realtime or re-structurability aspects.
|| '''Wiki'''
|-
| '''Forums'''
|| '''Mailing list''' - Discussion of project policy or wider design issues
|| It's possible to use wiki pages like a piratepad
|| Multiple issues in '''Issue tracker''' - ''focused'' and ''implementable'' tasks
|-
|
|| Detailed proposal on the '''Wiki''' then linked to the '''Mailing list'''
||
||
|}

The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are available only through Github/mailinglist or forum for collaboration and new contributors only observe Github or the Wiki. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not visible to the critical audience, it disturbs the process of reviewing a Pull Request or discussing the present issue, and it makes things hard to find later.

''If a new Policy/design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)''

Design Workflow

2012-09-07T07:23:30Z

Ae-2222:

Table thingy of Workflow for design/resolution of issues. Experimenting with tables:). Still WIP, feel free to reformat/fix/make clearer.

{| class="wikitable"
|-
! '''Stage 1.
Informally bounce ideas off people to see if they are worth bringing to the attention of the entire community''' (purely optional)
! '''Stage 2.
Put things up for discussion'''
! '''Stage 3.
Detailed discussion'''
! '''Stage 4.
Documenting outcomes (When a solution has been found or discussion has slowed down/stalled and is unlikely to resume in the near future)'''
|-
| '''IRC''' - the most feedback. Engine room of opensource projects and used for collaboration ''exlusively'' by a lot of contributors.
|| '''Issue tracker''' - is focused enough to allow immediate solution. ''Workflow ends here.''
|| '''Mailing list''' and possibly a '''pirate pad''' for issues that are too extensive or benefit from realtime or re-structurability aspects.
|| '''Wiki'''
|-
| '''Forums'''
|| '''Mailing list''' - Discussion of project policy or wider design issues
|| It's possible to use wiki pages like a piratepad
|| Multiple issues in '''Issue tracker''' - ''focused'' and ''implementable'' tasks
|-
|
|| Detailed proposal on the '''Wiki''' then linked to the '''Mailing list'''
||
||
|}

The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are available only through Github/mailinglist or forum for collaboration and new contributors only observe Github or the Wiki. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not visible to the critical audience, it disturbs the process of reviewing a Pull Request or discussing the present issue, and it makes things hard to find later. If a new Policy/design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)

Design Workflow

2012-09-07T07:17:45Z

Ae-2222:

Table thingy of Workflow for design/resolution of issues. Experimenting with tables:). Still WIP, feel free to reformat/fix/make clearer.

{| class="wikitable"
|-
! '''Stage 1.
Informally bounce ideas off people to see if they are worth bringing to the attention of the entire community''' (purely optional)
! '''Stage 2.
Put things up for discussion'''
! '''Stage 3.
Detailed discussion'''
! '''Stage 4.
Documenting outcomes (When a solution has been found or discussion has slowed down/stalled and is unlikely to resume in the near future)'''
|-
| '''IRC''' - the most feedback. Engine room of opensource projects and used for collaboration exlusively by a lot of contributors.
|| '''Issue tracker''' - is focused enough to allow immediate solution. ''Workflow ends here.''
|| '''Mailing list''' and possibly a '''pirate pad''' for issues that are too extensive or benefit from realtime or re-structurability aspects.
|| '''Wiki'''
|-
| '''Forums'''
|| '''Mailing list''' - Discussion of project policy or wider design issues
|| It's possible to use wiki pages like a piratepad
|| Multiple issues in '''Issue tracker''' - ''focused'' and ''implementable'' tasks
|-
|
|| Detailed proposal on the '''Wiki''' then linked to the '''Mailing list'''
||
||
|}

The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are available only through Github/mailinglist or forum for collaboration and new contributors only observe Github or the Wiki. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not visible to the critical audience, it disturbs the process of reviewing a Pull Request or discussing the present issue, and it makes things hard to find later. If a new Policy/design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)

Design Workflow

2012-09-07T07:16:09Z

Ae-2222:

Table thingy of Workflow for design/resolution of issues. Experimenting with tables:). Still WIP, feel free to reformat/fix/make clearer.

{| class="wikitable"
|-
! '''Stage 1.
Informally bounce ideas off people to see if they are worth bringing to the attention of the entire community''' (purely optional)
! '''Stage 2.
Put things up for discussion'''
! '''Stage 3.
Detailed discussion'''
! '''Stage 4.
Documenting outcomes (When a solution has been found or discussion has slowed down/stalled and is unlikely to resume in the near future)'''
|-
| '''IRC''' - the most feedback. Engine room of opensource projects and used for collaboration exlusively by a lot of contributors.
|| '''Issue tracker''' - is focused enough to allow immediate solution. ''Workflow ends here.''
|| '''Mailing list''' and possibly a '''pirate pad''' for issues that are too extensive or benefit from realtime or re-structurability aspects.
|| '''Wiki'''
|-
| '''Forums'''
|| '''Mailing list''' - Discussion of project policy or wider design issues
|| It's possible to use wiki pages like a piratepad
|| Multiple issues in '''Issue tracker''' - ''focused'' and ''implementable'' tasks
|-
|
|| Detailed proposal on '''Wiki''' then linked to '''mailing list'''
||
||
|}

The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are available only through Github/mailinglist or forum for collaboration and new contributors only observe Github or the Wiki. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not visible to the critical audience, it disturbs the process of reviewing a Pull Request or discussing the present issue, and it makes things hard to find later. If a new Policy/design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)

Design Workflow

2012-09-07T07:15:29Z

Ae-2222:

Table thingy of Workflow for design/resolution of issues. Experimenting with tables:). Still WIP, feel free to reformat/fix/make clearer.

{| class="wikitable"
|-
! '''Stage 1.
Informally bounce ideas off people to see if they are worth bringing to the attention of the entire community''' (purely optional)
! '''Stage 2.
Put things up for discussion'''
! '''Stage 3.
Detailed discussion'''
! '''Stage 4.
Documenting outcomes (When a solution has been found or discussion has slowed down/stalled and is unlikely to resume in the near future)'''
|-
| '''IRC''' - the most feedback. Engine room of opensource projects and used for collaboration exlusively by a lot of contributors.
|| '''Issue tracker''' - is focused enough to allow immediate solution. ''Workflow ends here.''
|| '''Mailing list''' and possibly a '''pirate pad''' for issues that are too extensive or benefit from realtime or re-structurability aspects.
|| Wiki
|-
| '''Forums'''
|| '''Mailing list''' - Discussion of project policy or wider design issues
|| It's possible to use wiki pages like a piratepad
|| Multiple issues in Issue tracker - ''focused'' and ''implementable'' tasks
|-
|
|| Detailed proposal on '''Wiki''' then linked to '''mailing list'''
||
||
|}

The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are available only through Github/mailinglist or forum for collaboration and new contributors only observe Github or the Wiki. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not visible to the critical audience, it disturbs the process of reviewing a Pull Request or discussing the present issue, and it makes things hard to find later. If a new Policy/design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)

Design Workflow

2012-09-07T07:13:26Z

Ae-2222: Create design workflow table.

Table thingy of Workflow for design/resolution of issues. Experimenting with tables:). Still WIP, feel free to reformat/fix/make clearer.

{| class="wikitable"
|-
! '''Stage 1.
Informally bounce ideas off people to see if they are worth bringing to the attention of the entire community''' (purely optional)
! '''Stage 2.
Put things up for discussion'''
! '''Stage 3.
Detailed discussion'''
! '''Stage 4.
Documenting outcomes (When a solution has been found or discussion has slowed down/stalled and is unlikely to resume in the near future)'''
|-
| '''IRC''' - the most feedback. Engine room of opensource projects and used for collaboration exlusively by a lot of contributors.
|| '''Issue tracker''' - is focused enough to allow immediate solution. ''Workflow ends here.''
|| '''Mailing list''' and possibly a '''pirate pad''' for issues that are too extensive or benefit from realtime or re-structurability aspects.
||
|-
| Forums
|| '''Mailing list''' - Discussion of project policy or wider design issues
|| It's possible to use wiki pages like a piratepad
||
|-
|
|| Detailed proposal on '''Wiki''' then linked to '''mailing list'''
||
||
|}

The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are available only through Github/mailinglist or forum for collaboration and new contributors only observe Github or the Wiki. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not visible to the critical audience, it disturbs the process of reviewing a Pull Request or discussing the present issue, and it makes things hard to find later. If a new Policy/design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)

Getting started

2012-09-06T12:26:31Z

Ae-2222:

Pioneer Wiki

2012-09-06T10:52:22Z

Ae-2222:

Pioneer is some kind of game thing.

Please make this wiki nice. Copy the content over from the [https://github.com/pioneerspacesim/pioneer/wiki GitHub wiki], add stuff about mods, dev, whatever. Be awesome!

And write a nice front page and get rid of this, ok? :)

Pioneer is brung to you by a flock of [https://github.com/pioneerspacesim/pioneer/blob/master/AUTHORS.txt opensource beardy-weirdies], and is [http://www.gnu.org/licenses/gpl.html Free Software]

----

'''To Create a new page:''' type the URL of the page you would like to create e.g. http://pioneerwiki.com/wiki/Mods . You will then be taken to an empty page. Click the "edit this page" link and write in the edit box. Keep in mind there is a ''preview button'' and remember that ''content can be changed as often as you like''.

'''This is ''your'' Pioneer wiki, and not Wikipedia!'''

Be free with using talk pages to organise and collaborate.

Things this wiki might potentially be used for:
* Tutorials, FAQs, detailed proposals of ideas, summaries of discussions, screenshots/pioneer video links, lists of useful resources by topic (coding, creative stimulus), personal pages containing notes/to-do lists and other material related to pioneer, task status pages for focus groups in relation to translating, mod packaging etc., introductory briefings for new contributors by area. In addition to the usual project documentation.

It might be advisable to link new pages here in the short term so others can add content. Use the external link button on the editbox and paste your URL.[http://pioneerwiki.com/wiki/Sandbox Sandbox page] for playing around with editing.

[http://pioneerwiki.com/wiki/Mods '''Mods''']

Sandbox

2012-09-06T10:48:26Z

Ae-2222: Create sandbox for experimentation.

Feel free to experiment with editing.

Pioneer Wiki

2012-09-06T10:38:57Z

Ae-2222: Add a short explanation of page creation etc..

Mods

2012-09-06T10:01:36Z

Ae-2222: Start mod page.

== Available Mods ==

=== How to install Mods ===

Feel free to reorganise and edit this page as much as you like. This is to just start wiki editing off.

=== Alpha 26 ===

==== Mod Packages ====

==== Mods ====

===== Heightmaps =====

====== Moon heightmap ======

Size: 33mb

Description: Higher res heightmap which replaces the 2mb default heightmap.

Link: Forthcoming:).

=== Alpha 25 ===

=== Alpha 24 ===