Difference between revisions of "Sugar on a Stick/Activity Criteria/Status"
| Line 63: | Line 63: | ||
IDEA: Color code activities listed based on criteria fulfilled | IDEA: Color code activities listed based on criteria fulfilled | ||
| − | + | Rationale: Gives a visual cue for developers that one or more criteria are not complete or accurate. | |
| − | + | Test: Activities are listed in RED until each criteria has been addressed and filled in with an active link. | |
[[Instructions]]: Add activity to list. Test each criteria and set status appropriately. When all criteria are fulfilled, color of activity changes to BLACK. | [[Instructions]]: Add activity to list. Test each criteria and set status appropriately. When all criteria are fulfilled, color of activity changes to BLACK. | ||
| Line 72: | Line 72: | ||
IDEA: Add +/- ranking to criteria in table | IDEA: Add +/- ranking to criteria in table | ||
| − | + | Rationale: Add ranking to criteria to encourage better documentation. | |
| − | + | Test: Validate if minimum criteria has been met. Subjective assessment follows to determine + or - ranking. | |
| − | + | Instructions: By default, a checkmark (and hyperlink) is placed in the table for each criteria met. If the documentation at the link destination is an excellent example, add a + to the checkmark in table. If it's poor or incomplete documentation, add a - to the checkmark. | |
Revision as of 13:31, 16 June 2010
Activity table
| Activity | Pedagogy | Fedora repo | ASLO * | Pootle | Usage page | Development page | Tickets | Smoke test | Journal | Collaboration |
|---|---|---|---|---|---|---|---|---|---|---|
| Fructose | ||||||||||
| browse | ✓ | ✓ | ✓ | ✓ | ? | ? | ✓ | ? | ✓ | ✓ |
| calculate | ✓ | ✓ | ✓ | ✓ | ? | ? | ✓ | ? | ✓ | ✓ |
| chat | ✓ | ✓ | ✓ | ✓ | ? | ? | ✓ | ? | ✓ | ✓ |
| etoys | ✓ | ? | ✓ | ✓ | ✓ | x | ✓ | ? | ✓ | ✓ |
| imageviewer | ✓ | ✓ | ✓ | ✓ | ? | ? | ✓ | ? | ✓ | ✓ |
| jukebox | ✓ | ✓ | ✓ | ✓ | ? | ? | ✓ | ? | ✓ | ✓ |
| log | ✓ | ✓ | ✓ | ✓ | ? | ? | ✓ | ? | ✓ | x |
| pippy | ✓ | ✓ | ✓ | ✓ | ? | ? | ✓ | ? | ✓ | ✓ |
| read | ✓ | ✓ | ✓ | ✓ | ? | ? | ✓ | ? | ✓ | ✓ |
| terminal | ✓ | ✓ | ✓ | ✓ | ? | ? | ✓ | ? | ✓ | ✓ |
| turtleeblocks | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| write | ✓ | ✓ | ✓ | ✓ | ? | ? | ✓ | ? | ✓ | ✓ |
| Honey | ||||||||||
| physics | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ? | ✓ | x |
| visual match | ✓ | ✓ | ✓ | ✓ | ✓ | x | ✓ | x | ✓ | ✓ |
| abacus | ✓ | In review | ✓ | ✓ | ✓ | ✓ | ✓ | x | ✓ | x |
| sliderule | ✓ | x | ✓ | ✓ | ✓ | x | ✓ | x | ✓ | x |
| ruler | ✓ | x | ✓ | ✓ | ✓ | x | ✓ | x | ✓ | x |
| Uncategorized | ||||||||||
| memorize | ? | ✓ | ✓ | ? | ✓ | ? | ? | ? | ? | ? |
| maze | ? | ✓ | ? | ? | ? | ? | ? | ? | ? | ? |
* Note that to be included on ASLO, an activity must have a license as described here.
Activities to add to the table
- more activities to evaluate: xoirc, moon, labyrinth, typing turtle, tamtam suite, speak, measure, turtleart, implode, scratch, slider, jigsaw, flipsticks, phototoon, record, infoslicer, ...
Ideas for revision
Have a criteria, or want to revise one? This is the section to do it in.
Add your own idea here
IDEA: Color code activities listed based on criteria fulfilled
Rationale: Gives a visual cue for developers that one or more criteria are not complete or accurate.
Test: Activities are listed in RED until each criteria has been addressed and filled in with an active link.
Instructions: Add activity to list. Test each criteria and set status appropriately. When all criteria are fulfilled, color of activity changes to BLACK.
IDEA: Add +/- ranking to criteria in table
Rationale: Add ranking to criteria to encourage better documentation.
Test: Validate if minimum criteria has been met. Subjective assessment follows to determine + or - ranking.
Instructions: By default, a checkmark (and hyperlink) is placed in the table for each criteria met. If the documentation at the link destination is an excellent example, add a + to the checkmark in table. If it's poor or incomplete documentation, add a - to the checkmark.
Be sure to describe:
Rationale: Where does this requirement come from and why is it important?
Test: how we can make sure that the requirement is met - what sort of testing needs to be done to verify this?
Instructions: links to instructions on how Activity authors and maintainers can fulfill the requirement, if possible.