(Initial import; some markup fixes) |
(→Writing Tasks for Wine: remove dead links, reference to SGML docs) |
||
Line 2: | Line 2: | ||
In the long run, documentation and coordinating development can be just as important to a software project as coding. Even if you don't feel comfortable programming, there are still many places where Wine could use your help. Language skills are the primary need for maintaining the wiki, translating different portions of the project, and writing good documentation. | In the long run, documentation and coordinating development can be just as important to a software project as coding. Even if you don't feel comfortable programming, there are still many places where Wine could use your help. Language skills are the primary need for maintaining the wiki, translating different portions of the project, and writing good documentation. | ||
Understanding the actual code that makes up Wine should only be necessary if you want to help make documentation for developers, and editing the wiki just requires writing in | Understanding the actual code that makes up Wine should only be necessary if you want to help make documentation for developers, and editing the wiki just requires writing in MediaWiki syntax. See [[Web Content Tasks]] for tips on editing the Wine wiki | ||
If you understand several languages, translations are a high priority. While downloading the Wine source code and building it to test your translations is recommended, a simpler method does exist if you lack the time or resources for building Wine from source. | If you understand several languages, translations are a high priority. While downloading the Wine source code and building it to test your translations is recommended, a simpler method does exist if you lack the time or resources for building Wine from source. See [[Translating]] for more information. | ||
There are a few other pages you may find helpful or interesting: | There are a few other pages you may find helpful or interesting: | ||
*Two sites with automatic stats on Wine's translation progress [http://source.winehq.org/transl/ here] and [http://fgouget.free.fr/wine-po/ here] (different methods result in different values) | *Two sites with automatic stats on Wine's translation progress [http://source.winehq.org/transl/ here] and [http://fgouget.free.fr/wine-po/ here] (different methods result in different values) |
Revision as of 21:37, 11 February 2016
Writing Tasks for Wine
In the long run, documentation and coordinating development can be just as important to a software project as coding. Even if you don't feel comfortable programming, there are still many places where Wine could use your help. Language skills are the primary need for maintaining the wiki, translating different portions of the project, and writing good documentation.
Understanding the actual code that makes up Wine should only be necessary if you want to help make documentation for developers, and editing the wiki just requires writing in MediaWiki syntax. See Web Content Tasks for tips on editing the Wine wiki
If you understand several languages, translations are a high priority. While downloading the Wine source code and building it to test your translations is recommended, a simpler method does exist if you lack the time or resources for building Wine from source. See Translating for more information.
There are a few other pages you may find helpful or interesting: