| 6 | |
| 7 | == What is here == |
| 8 | |
| 9 | This section of the site (the Trac install at dev.ibboard.co.uk) contains: |
| 10 | * our [/roadmap roadmap] for the application |
| 11 | * a [/browser browsable copy] of the source code and its revisions |
| 12 | * the [/query ticketing system] where users and developers can [newticket report bugs or request features] |
| 13 | * a [/timeline timeline] of changes made to tickets and source code. |
| 14 | |
| 15 | == What we need == |
| 16 | |
| 17 | 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: |
| 18 | |
| 19 | * '''Developers''' - anyone can freely check out the source code from svn://svn.ibboard.co.uk/warfoundry/. If you want to contribute code changes back then please [http://ibboard.co.uk/contact.php contact IBBoard]. |
| 20 | * '''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. |
| 21 | * '''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. |
| 22 | * '''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 |