Changes between Version 7 and Version 8 of Development/NewDeveloperGuide

Timestamp:

07/31/10 19:49:59 (9 years ago)

Author:

ibboard

Comment:

--

Development/NewDeveloperGuide

@@ -36 +36 @@
 == I'm new to large projects - where do I start? ==
 
-It depends where your interest is! WarFoundry isn't an overly large project, but it does come as a number of projects. If you're interested in usability and front-end work then check out the GTK# or WinForms interfaces for Linux and Windows respectively. If you want to add back-end functionality then check out the main WarFoundry API project. If you want to help with other file formats then either check out the pre-existing project (e.g. Rollcall or ArmyBuilder) or start your own project from scratch to support another file format.
+It depends where your interest is! WarFoundry isn't an overly large project, but it does come as a number of projects. If you're interested in usability and front-end work then check out the Qt#, GTK# or WinForms interfaces for Linux and Windows respectively. If you want to add back-end functionality then check out the main WarFoundry API project. If you want to help with other file formats then either check out the pre-existing project (e.g. Rollcall or ArmyBuilder) or start your own project from scratch to support another file format.
 
-If you want a specific task to start working on, then there are always [/query bugs and feature requests] for you to investigate. To accept a bug and work on it, sign up for an account, ask IBBoard to make you a "developer", get Subversion access, accept the bug and then commit the fix. Any work on bugs and features would be appreciated, but working on tickets tagged against earlier milestones first is better!
+If you want a specific task to start working on, then there are always [/query bugs and feature requests] for you to investigate. The [tag:papercut 'Papercut'] bugs are generally small bugs that can be picked up and fixed without much in-depth knowledge of WarFoundry. To accept a bug and work on it, sign up for an account, ask IBBoard to make you a "developer", get Subversion access, accept the bug and then commit the fix. Any work on bugs and features would be appreciated, but working on tickets tagged against earlier milestones first is better!
 
 == How does the ticketing system work and how does it help? ==