IntroductionMeasuring productivity of a developer objectively is not an easy task. We use developer points that each developer assigns to themselves. RulesEvery week, all developers describe their main contributions to this project, and how many points they think they deserve for their work (on a scale from 1 to 100). Here are some rough guides how points can be given: | 20 - 100 points | Major development & implementation work of highly demanded core features to the main trunk. | | 10 - 60 points | Development of examples, actions, views; extension of functionality, debugging; design, artwork; writing documentation. | | 3 - 30 points | Useful suggestions for implementation; solving particular open problems for this project; smaller programming improvements. | | 1 - 5 points | Participation in group discussion, wiki page editing, suggestions that bring the project forward. | | 0 points | Sorry, didn't have any time this week. |
Below, please write down how many points you think you deserve for each week's contribution to this project, and a short summary of your contribution. Please try to be truthful to yourself, and compare your contribution to the contributions and points by others. You can adjust your points later if you think you have done more or less than some other person. If you don't agree with someone else's points, you may contact the person, the project owner, or discuss this in the group. This may always be cross-checked with subversion logs for code and wiki and group discussion entries. At the end, any grant received will be divided according to the sum of points obtained by then: The qualifying grant of round 1 (if applicable) is split according to developer points earned in round 1. The final grant of round 2 (if applicable) is split according to the sum of developer points earned in round 1 and round 2. Donations that are received up to one month after the end of the competition or that are specifically designated to the developers of the competition are also split according to the sum of points earned in round 1 and round 2. The pointsThe weeks start Tuesday and end on Monday, because the competition will end on Monday. Round 1 ends on Apr 14, 2008; round 2 ends on June 30, 2008. (8 weeks left after May 6, 2008) Week 22: Apr 29 - May 5, 2008- Zero: 10 points small bugfix
Week 21: Apr 22 - Apr 28, 2008- Peli: 10 points: small bug fixes.
Week 20: Apr 15 - Apr 21, 2008: Release 0.1.7- Peli: 30 points: various bug fixes.
- Zero: 40 points: managedServices, reworked DateTime Alert
Week 19: Apr 8 - Apr 14, 2008: Release 0.1.6, Deadline round 1- Peli: 100 points: Wii mote patch, SplashPlay enhancements, various bug fixes, prepare single apk.
- Zero: 70 points various buxfixes.
- friedger: 80 points: inital values for judges, fixes for alerts, tagging
Week 18: Apr 1 - Apr 7, 2008- Peli: 50 points: ShoppingList themes + basic location alert.
- Zero: 40 points: Alert Services
Week 17: Mar 25 - Mar 31, 2008: Release 0.1.5- Peli: 50 points: SensorSimulator fixes, ShoppingList GTalk.
- Zero: 40 points: AlertProvider KISS
- friedger: 60 points: locations with alerts+extras, merge duplicate tagging views, various bug fixes
Week 16: Mar 18 - Mar 24, 2008- Peli: 60 points: SplashPlay.
- Zero: 5 points: concept for alerts
- friedger: 15 points: minor enhancements intents, locations.
Week 15: Mar 11 - Mar 17, 2008: Release 0.1.4- friedger: 50 points: List of Intents added
- friedger: 30 points: Improve LocationsView (moved from FavoriteLocations)
- Peli: 80 points: Compile release, MediaPlayer, MediaBrowser, started on SplashPlay.
- Zero: 60 points: atom support for newsreader, bugfixes. newsreader service improvements,magnolia layout improvements
Week 14: Mar 4 - Mar 10, 2008- Peli: 40 points: SensorSimulator (sensor rates); fix issues.
- friedger: 15 points: Minor improvments, Bolt support added.
- Zero: 40 points: Mailprovider
Week 13: Feb 26 - Mar 3, 2008- Peli: 40 points: SensorSimulator improvements; JavaDoc.
- Zero: 80 points: Newsreader 0.1, started MailProvider
- friedger: 60 points: Acceptance test added.
Week 12: Feb 19 - Feb 25, 2008: Release 0.1.3- friedger: 20 points: Convenience methods for Tagging + bug fixing
- Peli: 50 points: Shopping list + PresentPicker + SensorSimulator Settings to m5; new OpenIntentsView + new Icons.
Week 11: Feb 12 - Feb 18, 2008- friedger: 10 points: icons for Tagging
- Peli: 40 points: Update to m5 + Zero's ant scripts improved.
- Zero: 50 points: Update core to m5 + basic ant scripts
Week 10: Feb 5 - Feb 11, 2008Week 9: Jan 29 - Feb 4, 2008- Peli: 10 points: Sensor Simulator: small improvements.
- friedger: 40 points: ContentBrowser with package list.
Week 8: Jan 22 - Jan 28, 2008: Release 0.1.2- Zero: 45 points: Tagging on magnolia & delicious api
- Peli: 40 points: Sensor Simulator, OpenGLSensors demo
- friedger: 60 points: ContentIndexProvider added
Week 7: Jan 15 - Jan 21, 2008- Zero: 20 points: Atom Format support for News Provider
- Peli: 50 points: Sensor Simulator + settings view.
Week 6: Jan 8 - Jan 14, 2008- Peli: 20 points: Starting work on Sensor Simulator.
Week 5: Jan 1 - Jan 7, 2008: Release 0.1.1- Peli: 50 points: Present Picker sample application.
Week 4: Dec 25 - 31, 2007: Release 0.1.0- Peli: 60 points: Shopping list KISS features.
Week 3: Dec 18 - 24, 2007- Peli: 20 points: Compile release 0.1.0.
Week 2: Dec 11 - 17, 2007- Peli: 30 points: Set up release plan, introduce KISS features for CentralTagging and CentralShoppingList.
- friedger: 50 points: Location Provider
- friedger: 50 points: Favorite Location Activity
- friedger: 50 points: Tag Provider
- friedger: 50 points: Tag Activitiy
Week 1: Dec 6 - 10, 2007- Peli: 30 points: Set up basic work frame.
|
Sign in to add a comment
