Changes between Version 1 and Version 2 of GetInvolved


Ignore:
Timestamp:
03/03/09 20:30:56 (11 years ago)
Author:
ibboard
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GetInvolved

    v1 v2  
    1616If you want to contribute bug report/feature tickets then you'll need to [/register register] an account on this site.
    1717
     18== File Creators ==
     19
     20File Creators are closer to developers, but don't need to work with the source code. Rollcall previously had [http://www.hiveworldterra.co.uk/Downloads/cat_Warhammer40000ADFs.html lots of ADF files], but WarFoundry will start off with no native files. Plans are afoot to build file editor apps, but any text-based file can also be created by hand.
     21
     22We don't currently have documentation of the file format, or even a finalised format, but when we do then we'll need people to create race definitions.
     23
    1824== Developers ==
    1925
     
    2127
    2228To get a developer account, sign up on Trac and then contact IBBoard (either [http://forums.hiveworldterra.co.uk/memberlist.php?mode=viewprofile&u=2 through the forums] or [http://ibboard.co.uk/contact.php his website]) to get the account promoted to a "developer" account and a Subversion account created. Once you set up your Subversion repositories with a username and password you will be able to commit to both the WarFoundry and IBBoard utils repositories.
     29
     30== Documenters ==
     31
     32There are two main parts of documentation - user and developer. User documentation helps people get started with the tool or use advanced features, while developer documentation helps people understand the API so that they can get to grips with it or write plugins.
     33
     34Once we approach our first stable release then contributions of user guides could be put together in the [http://forums.hiveworldterra.co.uk/viewforum.php?f=39 forums] before being copied to the main website.
     35
     36Most of the developer documentation should be written as the developer's write the API (documenting what public methods do so that they can be tested and so that they have a defined contract of what they will do given certain inputs). A large enough project is always difficult to get started with though, so introductory tutorials adding small features or step-by-step guides to creating plugins may prove useful.
     37
     38== Designers/GUI/Graphics ==
     39
     40A lot of open source applications can be functionally great but have a poor user interface and it can be a poor user interface over a great program that puts people off using it. The split between a back-end API library and front-end UIs makes creating new interfaces easier, but input on existing interfaces, new icons and other graphical feedback would also be appreciated. Any contributions should generally be posted in the [http://forums.hiveworldterra.co.uk/viewforum.php?f=39 forums], but designers/graphics contributors may get developer accounts on Trac and Subversion if useful and necessary.