Changes between Version 49 and Version 50 of DevProjects
- Timestamp:
- Oct 6, 2008, 12:22:17 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevProjects
v49 v50 1 = Development projects = 2 We need volunteers to help with software testing and development. If you have one or more of the relevant technical skills (C++ system programming, PHP/MySQL Web development, wxWidgets programming, autoconf/automake expertise, etc.) you may be able to help us maintain and enhance BOINC. 1 = Help wanted - programming = 3 2 4 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. 3 BOINC needs volunteers to help with software development. 4 BOINC consists of several areas, each with some required technical skills: 5 5 6 To get started, read about the [SoftwareDevelopment BOINC software development process]. 7 Find a small bug fix or enhancement to do (look at the [/trac/query BOINC bug database], the [/email_lists.php email lists], or [/dev/ message boards] for ideas). 8 Look at the source code and think about how you would implement it. 9 Then communicate with the [ProjectPeople area owner], sketching what you want to do and how. Work with the the area owner to carry out and check in the work. 6 || '''Area''' || '''Skills needed''' || 7 || Client || C++, system programming || 8 || Manager || C++, !WxWidgets, GUI and graphical design, usability || 9 || Server programs || C++, system programming, database design, MySQL || 10 || Web features || PHP, CSS, web design, database design, MySQL || 11 || Unix build system || autoconf, automake || 12 13 The University of California holds the copyright on all BOINC source code. 14 By submitting contributions to the BOINC code, you irrevocably assign all right, title, and interest, 15 including copyright and all copyright rights, in such contributions to The Regents of the University of California, 16 who may then use the code for any purpose that it desires. 17 18 == Finding something to work on == 19 20 There are several ways to get tasks to work on: 21 22 * Scan the [/trac/query BOINC bug database] for unresolved bugs or feature requests. 23 * Read the list of proposed features on this page. 24 * Scan the [/dev/ BOINC message boards] for ideas. 25 26 == Coordinating your work == 27 28 Once you pick out something to work on: 29 30 * Look at the source code and think about how you would implement it. 31 * Read about the [SoftwareDevelopment BOINC software development process]. 32 * Communicate with the [ProjectPeople area owner], and reach a consensus on exactly what you're going to do and how. Don't start coding until you do this. 33 34 35 == Submiting your work == 36 37 * Submit your work (as diffs or files) to the area owner, so that they can evaluate it and possibly check it in. 38 * If you are working on a large task and want to stay current with the trunk, we can create an SVN workspace for you (ask). 39 * Once you've contributed a certain amount of work, we'll give you SVN write access. 40 41 == Proposed features == 10 42 11 43 The following development projects are available … … 13 45 Suggest new items in the boinc_dev email list.)''' 14 46 15 == Web features==47 === Web features === 16 48 17 49 (Requires advanced knowledge of PHP and MySQL.) … … 51 83 52 84 53 == Applications==85 === Applications === 54 86 Easy: 55 87 * Create Makefiles and project files to build the sample applications using MinGW and Dev-C++. … … 63 95 * Distributed Python: Borrow or invent a notation for master/slave execution in Python. Develop a system that implements this on BOINC, i.e., creates WUs and applications, and harvests the results. A design document is [PythonAppDev here]. 64 96 65 == Core client==97 === Core client === 66 98 (Requires advanced C++ system programming experience) 67 99 … … 88 120 * XML stats: add lat/long to user record? 89 121 90 == Installer==122 === Installer === 91 123 * Check if host is configured to go into Standby mode after X idle minutes. If so, ask user if they want to let BOINC run for X minutes, then go into standby right after that. 92 124 93 == BOINC Manager==125 === BOINC Manager === 94 126 (Requires experience with !WxWidgets GUI toolkit) 95 127 … … 102 134 * Have the Manager do RPCs in a separate thread. 103 135 104 == Server/Back End == 136 === Server/Back End === 137 105 138 106 139 (Requires advanced C++/Unix system programming experience)
