How to contribute

From Post-Apocalyptic RPG wiki

Jump to: navigation, search

Recruitment.png This article is a contribution how-to!

Contribution how-tos contain an introduction to all important topics and concepts a developer who would like to contribute to the project should know about. There are both department-specific contribution guides as well as one general project contribution guide.

This article covers all important aspects for people who would like to contribute to the project in general. Make sure to also read the department-specific contribution guides for the fields you consider contributing to.



In case you're contributing to an open source project for the very first time, you might not be familiar with the details how the development process works for most of these projects.

As that's a point that is confusing newcomers quite regularly, we've written down some notes how membership works in PARPG. The article also elaborates on how to contribute to the project in more substantial ways and how to gain commit access to the version control repository down the line.

Get in contact with the others

Ready for some brainstorming? You would like to provide your feedback? So get in contact with the other contributors. You can either visit the forums or try to catch somebody at the project's IRC channel in case you prefer live communication.

Provide early feedback

PARPG is still in early concept stage and the wiki articles for the different Development departments are waiting to get further fleshed out. You can help out by contributing with your expertise in the specific fields, e.g. by fleshing out the Glossary.

Introduce yourself

Getting to know each other is an important aspect of communication. Feel free to introduce yourself to the others at the board of the forums that is dedicated to this purpose:

Create a wiki profile

Another good way to find out even more of each other is to create a personal profile page at the wiki. You can do so by creating a new account and simply using your user page for the purpose. This kind of profile should contain at least the following basic information:

  • Motivation. What's your personal motivation to contribute to the project?
  • Experience. Prior experience in the field of (game) development and / or team projects.
  • Department. The development department(s) that you are contributing to: audio, game mechanics, graphics, programming, project management, writing.
  • Specific interests. What are your specific interests in your department(s) of choice? E.g. editor tool development, dialog writing, public relations, 3d model texturing, etc.
  • Additional information. There is a bunch of additional optional information that might be quite useful.
    • Timezone. The timezone you're residing in.
    • Development platform. Linux, Win32, Mac?
    • Development tools. IDEs, SVN clients, all kind of content creation tools.

Test the game

As PARPG is based on an open development philosophy, you can always grab the latest version of the game regardless of being involved in the development of the project or not. A guide how to Download the latest version has been recently written.

Get familiar with the workflow

We've agreed on a specific Workflow for PARPG development. While it will vary from department to department when it comes to details, some basic guidelines can be outlined that apply to every department. These guidelines were written with the Project philosophy ideas in mind: step by step, incremental, interative development and early testing and feedback.

Being familiar with the workflow of the team will help you to understand the development process better.

Retain an overview

The easiest way to stay up to date about what's going on, is to check out the new Planet PARPG. All project activity (posts at the forums, updates at the blog, SVN commits, trac tickets, etc.) is aggregated in one central place.

For feature prioritization we maintain a Feature list.

Add your Current task

Every development department (audio, graphics, mechanics, project management, programming & writing) has its own Current tasks article/section.

If you're working in the specific department, please add yourself there in alphabetic order. These lists are meant to be an easy way to let the other developers of the team know who's currently looking into or working on which part the game. Inactive developers should remove themselves from these lists when taking a break from the project.

Personal tools