-
Notifications
You must be signed in to change notification settings - Fork 21
How to collaborate_old
You can contribute to OpenGoo in several ways, this page helps you in understand the required contributors and the rules to follow.
Any kind of help is really appreciate, whether you are a programmer, sketcher, musician, writer or an artist in general. Players are really appreciate in reporting bugs or unwanted behaviours too!
Although programmers are the mostly required in the development process, we need sketchers for new or improved artworks and level design, musicians for new sounds and soundtracks and writers for the game story.
You should have a github account to contribute to OpenGoo even if you aren't a programmer, infact all the tasks are set up and taken on github in the issues' section. Filter the page issues with the labels filter on the lower left side of the page.
With the first alpha of the game a bug reporting system will be included in OpenGOO, so far you can write directly on the official Facebook page or on the Google+ page.
Everyone must sign up in the official mailing list and say what kind of task they can accomplish. The tasks will be discussed and, in case, taken.
To sign up in the mailing list send an empy email to: opengoo-request@freelists.org with 'subscribe' in the subject field, and write your emails to opengoo@freelists.org
Actually is the most required role. We need game artworks to design the look and shape of the game. Artworks can cover menu's concepts, goo's design, banners for youtube's videos or the website and level design.
Here there's the game's palette for the colors.
Same of sketchers, they can compose new sounds or songs for the game. More information will be described in the task.
We want to drive the development process of the game and help the team in finding the tasks to work out.
The development process will be iterative, every iteration will complete a milestone, a list of several goals to achieve (issues).
Issues are described goals a contributor can take and develop directly on github. When a goal is reached the issue is closed.
Every contributor must take a task assigning himself to an open issue. Many contributors can work together on the same task, just comment the issue with this syntax:
+[#github-name](#email-address)=#type_of_contributor; #task_description(optional).
per every contributor.
If someone leaves the task just comment the issue with:
-[#github-name].
Example:
+[Mandarancio](manda.mgf@gmail.com)=coder; sound initialization.
If you want to report a bug open a new issue with a description and mark it with the 'Bug' label. If you want to fix that issue you can also take the task.
When you want to suggest new ideas open a new issue with a detailed description of the idea and mark it with the 'Proposed' label. Then wait for approval. You can also take the proposed task.