Changes between Version 3 and Version 4 of ContributePage
- Timestamp:
- May 4, 2015, 12:34:11 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ContributePage
v3 v4 1 1 = Contribute to BOINC = 2 2 3 There are several areas in which you can tocontribute to BOINC.3 There are several areas in which you can contribute to BOINC. 4 4 5 Each area has its own communication channel , such as an email list.5 Each area has its own communication channel (typically an email list). 6 6 If you want to contribute in an area, you should read the communication channel 7 7 to get an idea of what is involved. … … 10 10 At some point, if you make a lot of good contributions, 11 11 you can ask to become a committer yourself, 12 by posting to the relevantemail list.12 by posting to the area's email list. 13 13 14 14 == Programming == 15 15 16 Help develop and fix bugs inBOINC.17 Various technical skills (C++, PHP, CSS, SQL, WxWidgets) are required16 Help develop, maintain, and debug BOINC. 17 Various technical skills (C++, PHP, CSS, SQL, !WxWidgets) are required 18 18 for different parts of BOINC; details are [DevProjects here]. 19 20 The BOINC source code is maintained in [https://github.com/BOINC/boinc Github]. 19 21 20 22 Communication:: the [http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev boinc_dev] email list 21 23 (for discussion) 22 24 and the Github issue tracking system (for specific bugs and feature requests). 23 To contribute:: submit patches (either via Github, or email diffs to [boinc_dev]).24 Committers:: David Anderson, Rom Walton, ...25 To contribute:: submit patches (either via Github, or email diffs to boinc_dev). 26 Committers:: David Anderson, Rom Walton, Rytis Slatkevicius, Christian Beer, Nicolas Alvarez, Eric Korpela. 25 27 26 28 == Testing == … … 30 32 Communication:: the [http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha boinc_alpha] email list, 31 33 and the [https://github.com/BOINC/boinc Github issue tracking system]. 34 The boinc_alpha list is where new versions (for testing) are announced. 32 35 To contribute:: the best way to contribute is by [http://boinc.berkeley.edu/alpha/ joining 33 the BOINC Alpha Test project .36 the BOINC Alpha Test project]. 34 37 You can also just submit bug reports on Github. 35 Committers:: David Anderson, Rom Walton 38 Committers:: David Anderson, Rom Walton. 36 39 37 40 == Documentation == … … 41 44 they're not publicly editable because of problems with spammers. 42 45 You can send revisions to a committer. 43 Committers:: David Anderson, Rom Walton 46 Committers:: David Anderson, Rom Walton. 44 47 45 48 == Translation == … … 52 55 You can volunteer to translate this text into non-English languages. 53 56 54 Communication:: the [http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_loc boinc_loc] email list. 55 To contribute:: sign up (by posting a request on the email list) to 56 do translation for a language of your choice. 57 Communication:: The [http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_loc boinc_loc] email list. 58 To contribute:: Post a request on the email list to do translation for a language of your choice. 57 59 Committers:: Rom Walton 58 60 … … 65 67 There are two customer support systems: 66 68 the message boards on the BOINC web site, 67 and [http://boinc.berkeley.edu/help.php an online system 68 where users can contact you personally via Skype or email]. 69 and [http://boinc.berkeley.edu/help.php an online system where users can contact you personally via Skype or email]. 69 70 70 71 Communication:: the BOINC message boards,