Changes between Version 10 and Version 11 of WikiStart


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

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v10 v11  
    1616== What we need ==
    1717
    18 WarFoundry needs help in several areas, all of which help the development of WarFoundry but not all of which need you to code. As an open source application it's easy to get involved. The main areas that we currently need help with are:
     18WarFoundry needs help in several areas, all of which help the development of WarFoundry but not all of which need you to code. As an open source application it's easy to [wiki:GetInvolved Get Involved]. The main areas that we currently need help with are:
    1919
    2020 * '''Developers''' - anyone can freely check out the source code from svn://svn.ibboard.co.uk/warfoundry/ - set-up instructions are available in our [wiki:Development/GettingStarted Getting Started guide]. If you want to contribute code changes back then please [http://ibboard.co.uk/contact.php contact IBBoard].
    2121 * '''Users''' - an application isn't very useful without users. The current design direction works along the lines of what seems to be needed with a basis in Warhammer and Warhammer 40,000, but with flexibility to cover a generic system. The more users we get from different game systems the better we can support them.
    2222 * '''Documentation''' - by the time the tool reaches its first release we'll need documentation on how to use it and how to create files for it. Although the Developers know the program, they're not always the best ones to describe its use to the general public, so specific documenters are always helpful.
    23  * '''Graphics/UI''' - a lot of open source applications can be functionally great but have a poor user interface. The split between a back-end API library and front-end UIs makes creating new interfaces easier, but any graphical input would be appreciated
     23 * '''Graphics/UI''' - a lot of open source applications can be functionally great but have a poor user interface. The split between a back-end API library and front-end UIs makes creating new interfaces easier, but any graphical input would be appreciated.