Changes between Version 3 and Version 4 of BadgesOld
- Timestamp:
- Nov 14, 2013, 7:08:55 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BadgesOld
v3 v4 1 = Proposal: badges and achievements for volunteer contributions [[BR]]=1 = Proposal: badges and achievements for volunteer contributions = 2 2 == Motivation == 3 3 The heading says it all: (volunteer) motivation. The general idea is to have BOINC support the notion of "badges" that represent various achievements and can be assigned to a volunteer's profile. Those badges should motivate the volunteers to keep contributing as they, apart from (un-sexy) credits alone, can show off their individual contributions in a more tangible and meaningful way. The idea isn't new and projects like World Community Grid already support the assignment of achievement badges which are then displayed in the community section, e.g. as part of the forum post author details. We, the Einstein@Home and Joachim Fritsch, propose to standardise and extend this feature to all interested BOINC projects and beyond. 4 4 5 == == 6 == == 7 == Note == 5 '''Note''' 6 8 7 ''The following represents a proposal, a basis for discussion. It's still work in progress! '' 9 8 … … 13 12 * Origin: badges should be assignable by projects and, eventually, in a cross-project way. 14 13 * Numbers: the numbers of assigned badges shouldn't be constrained. The could be tens of badges per volunteer, so prepare to visualise those. 15 * Assignment: assignments should support temporary and unlimited badges.14 * Assignment: assignments should support temporary (incl. renewal) and unlimited badges. 16 15 * Visibility: badges should be visible across the whole BOINC universe, at least in managers (desktop/mobile) and the web front-end (forums/profile), eventually even on the stats sites. 17 16 * Types: badges should be represented by icons/images, supported by textual descriptions. There should also be the means to represent different levels of the same badge type (e.g. a "Continued Support" badge in "Bronze", "Silver" or "Gold") 18 17 * Assignees: badges should be assignable to users as well as teams. 19 18 20 == Implementation ideas == 19 == Implementation notes == 20 * Badge "format" 21 * Image 22 * Bitmaps or vector graphics? 23 * For bitmaps: pre-defined set of resolutions? 24 * Which formats to support (GUI toolkit and browser compatibility)? 25 * Descriptive text 26 * Title 27 * Level 28 * Description 29 * Eventually multi-language 30 * Origin (name of project, cross-project) 31 * Time of awarding (e.g. for sorting) 32 * Display 33 * Forums 34 * Be sure to avoid clutter: limit number and link to full list 35 * Make entire badge display optional via community preference 36 * Support badges display as port of "user of the month" feature 37 * Show descriptive text when hovering over badge (mouse/tool-tip) 38 * Teams 39 * Show team badges also in profiles of team members (somewhat separately) 40 * Search (web) 41 * Support user profile searches filtered by badges 42 * Support team searches filtered by badges 43 * Server 44 * Project-specific badges defined in project database 45 * Rule-based assignment: use SQL to determine eligible users/teams per defined badge 46 * Project task to update the assignments by processing ruleset 47 * Support manual assignment of badges 48 * Stats site support 49 * Extend user profiles and team data to include badge references 50 * Provide set of (project) badges in dedicated download (sub)directory, tailored for (r)sync. 51 21 52 22 53 … … 26 57 27 58 == Open questions and challenges == 28 29 59 * How to ship the badges (images) efficiently? 60 * Should they be downloaded on demand (via URL) or shipped as "project file" (download on project attach/update)? 61 * Should they be downloaded as compound images (see stats site forum signature images) or separately? 62 * How to ship badge assignment data to the managers? 63 * Part of scheduler request (length constraints!)? 64 * User-specific notices/RSS feed? 65 * Periodic web RPCs? 66 * Should updates (images and data) be incremental or always be a full snapshot (e.g. to support badge removal)? 30 67 * How to implement cross-project badges? Are stats sites (e.g. BOINCstats) the natural place to do that? 68 * We could define a set of standard badges to allow stats site-agnostic assignment 69 * Should stats sites be allowed to come up with their own set of cross-project badges? 31 70 32 71 == Work package assignments == 33 72 * Desktop manager: Rom/Charlie 34 73 * Android app: Joachim 35 * Server: 74 * Server: David and/or E@H (TBD) 36 75 * DB: 37 76 * C++ bindings:
