Changes between Version 18 and Version 19 of DevProcess


Ignore:
Timestamp:
09/12/17 15:28:34 (9 months ago)
Author:
knreed
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DevProcess

    v18 v19  
    11= The BOINC development process =
     2BOINC is free software, distributed under the [http://www.gnu.org/copyleft/lesser.html Lesser General Public License] (LGPL), version 3 or later. The University of California holds the copyright on all BOINC source code. By submitting contributions to the BOINC code, you irrevocably assign all right, title, and interest, including copyright and all copyright rights, in such contributions to The Regents of the University of California, who may then use the code for any purpose that it desires.
    23
    3 BOINC is free software, distributed under the [http://www.gnu.org/copyleft/lesser.html Lesser General Public License]
    4 (LGPL), version 3 or later.
    5 The University of California holds the copyright on all BOINC source code.
    6 By submitting contributions to the BOINC code,
    7 you irrevocably assign all right, title, and interest, including copyright and all copyright rights,
    8 in such contributions to The Regents of the University of California,
    9 who may then use the code for any purpose that it desires.
     4 * [http://boinc.berkeley.edu/trac/wiki/Development_Workflow Development Workflow]
     5 * [wiki:DevQualityAssurance Quality Assurance Workflow] (under discussion)
     6 * [wiki:EmailLists boinc_dev], an email list for BOINC developers
     7 * [wiki:CodingStyle Coding style]
     8 * [wiki:DebugClientWin Debugging the client on Windows]
    109
    11  * [DevQualityAssurance Quality Assurance Workflow] (under discussion)
    12  * [EmailLists boinc_dev], an email list for BOINC developers
    13  * [CodingStyle Coding style]
    14  * [DebugClientWin Debugging the client on Windows]
     10Development is divided into several areas. Each area is managed by an 'owner'.
    1511
    16 Development is divided into several areas.
    17 Each area is managed by an 'owner'.
    18  
    19 || '''Area'''                        || '''Owner'''        || '''Key contributors''' ||
    20 || API                               || David Anderson     || ||
    21 || BOINC Manager                     || || Charlie Fenton ||
    22 || Client                            || David Anderson     || ||
    23 || Mac OS X                          || Charlie Fenton     || ||
    24 || Testing and release management    || || ||
    25 || Server                            || David Anderson     || Kevin Reed ||
    26 || Translations of GUI and web text  || || ||
    27 || Unix build system                 || Eric Korpela       || ||
    28 || Web features                      || David Anderson     || Rytis Slatkevicius, Janus Kristensen ||
     12|| '''Area''' || '''Owner''' || '''Key contributors''' ||
     13|| API || David Anderson || ||
     14|| BOINC Manager || || Charlie Fenton ||
     15|| Client || David Anderson || ||
     16|| Mac OS X || Charlie Fenton || ||
     17|| Testing and release management || || ||
     18|| Server || David Anderson || Kevin Reed ||
     19|| Translations of GUI and web text || || ||
     20|| Unix build system || Eric Korpela || ||
     21|| Web features || David Anderson || Rytis Slatkevicius, Janus Kristensen ||
    2922|| Windows installer and screensaver || || ||
    30 
    3123
    3224The BOINC development process involves interaction between various groups:
    3325
    3426== Participants ==
    35 
    36     * Report bugs on the BOINC message boards.
    37     * These are reported by message board moderators to the relevant area owner.
    38     * Participants may also file bug reports in Github.
     27 * Report bugs on the BOINC message boards.
     28 * These are reported by message board moderators to the relevant area owner.
     29 * Participants may also file bug reports in Github.
    3930
    4031== Area owners ==
    41 
    42     * Fix bugs or delegate to contributors.
     32 * Fix bugs or delegate to contributors.
    4333
    4434== Alpha testers ==
    45 
    46     * Test development releases and report problems via a Web-based system.
     35 * Test development releases and report problems via a Web-based system.
    4736
    4837== Release manager ==
    49 
    50     * Monitor the Alpha-test results and notify area owners of issues.
    51     * Decide when to create test releases; communicate with alpha testers via [//email_lists.php email list].
    52     * Decide when to make public releases.
     38 * Monitor the Alpha-test results and notify area owners of issues.
     39 * Decide when to create test releases; communicate with alpha testers via [//email_lists.php email list].
     40 * Decide when to make public releases.