Becoming a Member

If you are not a member of the google code project, but would like to contribute, here is what you can do:

1. Write your contribution as a patch, and submit it to one of the project admins ( ian/ian320, ame/hugo.persson) via email or a PM at tpforums.
2. If we like your work, and find the code useful and well-written, you will be a candidate for membership.
3. The existing members will discuss any new members and decide as a group whether or not to include someone new.
4. New members also must have a plan of what they will contribute (new features, keeping up with releases, etc)

Writing code

• Remember to use the issue list! When you want to work on something, or want others to work on it, make an issue. When you complete a task, close the corresponding issue.
• When committing, add comments explaining which issue you're fixing. Examples:
1. "In the last revision, r100 something broke. Fix for that." (r100 will be replaced with link to the specific revision automatically)
2. "Fixed  issue 99  by changing..." ( issue 99  will be replaced with a link to the issue)
• The same as above goes for creating issues: if you need to, reference the specific revision something broke or another related issue that must be accomplished first.
• Don't forget to update programs in the apps directory as well; we don't want the examples to be broken. It is a good idea to include them in your solution so that you get compile errors when you change things in TibiaAPI.
• Must use proper coding conventions (table based on http://www.irritatedvowel.com/Programming/Standards.aspx):

Coding Conventions (C# and C++)

• Braces always go on the next line

void Foo(string bar)
{
    if (bar == string.Empty)
    {
        // do something
    }
    else if (bar == "foo")
    {
        // do something else
    }
}

• If you are ever in doubt, look at other code; yours should match

Naming Convention

Reviewing code

• Please review the code that others have written often.
• Feel free to comment on their code at the revision page (at the bottom), and discuss potential changes or problems.