Changes between Version 14 and Version 15 of DevProjects
- Timestamp:
- Nov 2, 2007, 2:23:53 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevProjects
v14 v15 7 7 To get started, find a small bug fix or enhancement to do (look at the BOINC bug database, the email lists, or message boards for ideas). Look at the source code and think about how you would implement it. 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. 8 8 9 The following medium-to-largedevelopment projects are available:9 The following development projects are available: 10 10 11 * Applications 11 == Applications == 12 13 Easy: 14 * Create Makefiles and project files to build the sample applications using MinGW and DevC++. 15 Medium: 16 * Write example FORTRAN application and Makefiles/ project files 17 Hard: 12 18 * Write an example compound application (and suggest API revisions to make this easier). 13 * Create Makefiles and project files to build the sample applications using MinGW and DevC++.14 19 * Investigate the crlibm library for generating identical results across processors (or at least reducing the number of cases for HR). 15 20 * Java support: core client checks for the existence of JVM, reports version to scheduler. Write Java wrapper (runs JVM, gives it jar files). Note: Sztaki has already done some part of this. 16 21 * Same, .NET 17 22 * 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. 18 * Write example FORTRAN application and Makefiles/ project files 19 * Core client: 23 24 == Core client == 25 Medium: 20 26 * Add a preferences for total download and upload in a month (many Australian ISPs have monthly limits), or per X hours of processing time (see email from Kevin Reed). 27 * Don't enforce RAM limits unless free RAM is low 28 * GUI RPC to tell apps to checkpoint and quit. 29 Hard: 21 30 * Have the core client sense CPU temperature and throttle CPU if it goes too high. Open-source software for this (on Linux) is at http://www.lm-sensors.org/. 22 31 * Windows: get proxy config info directly from the OS … … 27 36 * Integrate !BitTorrent ([http://www.rasterbar.com/products/libtorrent/ libtorrent]?) with the core client. 28 37 * Do potentially slow RPCs and other tasks (such as computing disk usage) in a separate thread. 29 * Don't enforce RAM limits unless free RAM is low30 38 * Log result start/ends (for use by 3rd-party software like !BoincView). 31 39 * Prevent disk space usage from exceeding user preferences, and enforce resource shares, with file deletion according to project policy. 32 40 * Make messages of class MSG_USER_ERROR translatable. 33 * GUI RPC to tell apps to checkpoint and quit.34 41 * Vista: if get 'about to shut down' msg from OS, stop apps immediately (don't tell them to checkpoint). Investigate. 35 42 * XML stats: add lat/long to user record? 36 * BOINC Manager: 43 == BOINC Manager == 44 Easy: 37 45 * If using an AMS, put link to AMS (or user page) in sys tray popup, elsewhere 46 Hard: 38 47 * Properties pages for projects, jobs 39 48 * Turn off alerts (Rom's working on this) 40 49 * Have the Manager do RPCs in a separate thread. 41 * Server/Back End: 50 == Server/Back End == 51 Medium: 42 52 * When using HR, if the scheduler has sent one result of a WU using a particular app version, it should use the same app version for other results from that WU. 53 Hard: 43 54 * Implement a mechanism so that server software detects incompatible database format 44 55 * Scheduler: implement mechanisms so that server: 45 56 * Attempts to send results from the same WU to hosts with similar speed, so that a fast host doesn't have to wait weeks to get credit. 46 57 * Implement a 'benchmark result' mechanism: every host runs a benchmark result per app version, and the CPU time determines credit/CPU for future results 47 * Web features: 48 * User flag: team admin. 49 * Team flag: approval required. 50 * Groups (sub-teams). New DB table with name, description, team ID, flags, forum ID. Flags: 51 * Group membership table. 58 == Web features == 59 Easy: 60 * Convert PHP code to use [PhpDb the new database abstraction layer]. 61 * Combine user page and profile 62 * Change the ops/ web pages to require login by a user with admin privileges. 63 * Change default Q&A page to refer BOINC-specific questions to BOINC web site 64 65 Medium: 66 * Add a mechanism where team members can be designated as 'admins', and have some of the powers of the founder. 67 * Add a mechanism where joining a team or group requires approval of an admin. 68 * Groups (sub-teams). New DB table with name, description, team ID, flags, forum ID. Group membership table. 69 Hard: 52 70 * Propagate profiles between projects. When create or edit profile, if attached to other projects, show 'propagate changes' page, with checkboxes for other projects (must have same password on other projects). Add web RPCs for updating profile (args: user ID, profile, password hash). Implement this so that page doesn't block waiting for replies from RPCs. NOTE: this may not be a good idea - spammers could exploit it. 53 71 * Same for forum preferences 54 * Combine user page and profile55 72 * Add new profile features: 56 73 * 'Buddy lists' 57 74 * list of recent posts and threads this person created, on this and other projects 58 75 * other features from social networking sites? 59 * Change the ops/ web pages to require login by a user with admin privileges.60 76 * Add 'referral' mechanism: new user creates account, enters email of 'referrer' (or goes to URL that has it embedded). Give referrer a fraction of credit (or a 1-time bonus). List referrals on user page (show only those still active). Add new referral table to DB. 61 77 * Make it easy for teams to offer a client download that features their skin, and pre-register the user on that team for any projects he attaches to. 62 * Change default Q&A page to refer BOINC-specific questions to BOINC web site 63 64 Please check with [ProjectPeople David Anderson] before undertaking any of these. 78 Please check with [ProjectPeople area owner or David Anderson] before undertaking any of these.