Changes between Version 3 and Version 4 of ContributePage


Ignore:
Timestamp:
May 4, 2015, 12:34:11 PM (10 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ContributePage

    v3 v4  
    11= Contribute to BOINC =
    22
    3 There are several areas in which you can to contribute to BOINC.
     3There are several areas in which you can contribute to BOINC.
    44
    5 Each area has its own communication channel, such as an email list.
     5Each area has its own communication channel (typically an email list).
    66If you want to contribute in an area, you should read the communication channel
    77to get an idea of what is involved.
     
    1010At some point, if you make a lot of good contributions,
    1111you can ask to become a committer yourself,
    12 by posting to the relevant email list.
     12by posting to the area's email list.
    1313
    1414== Programming ==
    1515
    16 Help develop and fix bugs in BOINC.
    17 Various technical skills (C++, PHP, CSS, SQL, WxWidgets) are required
     16Help develop, maintain, and debug BOINC.
     17Various technical skills (C++, PHP, CSS, SQL, !WxWidgets) are required
    1818for different parts of BOINC; details are [DevProjects here].
     19
     20The BOINC source code is maintained in [https://github.com/BOINC/boinc Github].
    1921
    2022 Communication:: the [http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev boinc_dev] email list
    2123 (for discussion)
    2224  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.
    2527
    2628== Testing ==
     
    3032 Communication:: the [http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha boinc_alpha] email list,
    3133  and the [https://github.com/BOINC/boinc Github issue tracking system].
     34  The boinc_alpha list is where new versions (for testing) are announced.
    3235 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].
    3437  You can also just submit bug reports on Github.
    35  Committers:: David Anderson, Rom Walton
     38 Committers:: David Anderson, Rom Walton.
    3639
    3740== Documentation ==
     
    4144   they're not publicly editable because of problems with spammers.
    4245   You can send revisions to a committer.
    43  Committers:: David Anderson, Rom Walton
     46 Committers:: David Anderson, Rom Walton.
    4447
    4548== Translation ==
     
    5255You can volunteer to translate this text into non-English languages.
    5356
    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.
    5759 Committers:: Rom Walton
    5860
     
    6567There are two customer support systems:
    6668the 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].
     69and [http://boinc.berkeley.edu/help.php an online system where users can contact you personally via Skype or email].
    6970
    7071 Communication:: the BOINC message boards,