10,579
edits
Changes
Jump to navigation
Jump to search
Line 2:
Line 2: + + + Line 16:
Line 19: + Line 26:
Line 30: +
→Questions
==Questions==
==Questions==
===Milestones/Versions===
Would it make sense to have a Sugar '''milestone''' (e.g., Sugar 0.82) that is distinct from the OLPC milestones? Or would it make more sense to have a Sugar '''version''' that maps to an OLPC milestone?
Would it make sense to have a Sugar '''milestone''' (e.g., Sugar 0.82) that is distinct from the OLPC milestones? Or would it make more sense to have a Sugar '''version''' that maps to an OLPC milestone?
===Keywords/Components===
Would it make sense to consistently add '''keywords''' that map to the Sugar modules or should these be '''components'''?
Would it make sense to consistently add '''keywords''' that map to the Sugar modules or should these be '''components'''?
* sugar
* sugar
** ''et alia''
** ''et alia''
===Priorities===
The assignment of '''priorities''' is the difficult one. We need to come up with definitions and a process. A first pass:
The assignment of '''priorities''' is the difficult one. We need to come up with definitions and a process. A first pass:
:Low: odds and ends
:Low: odds and ends
===Verify===
Would it be possible to assign teams to each ticket, where we identify up front someone who agrees to '''verify''' a ticket, and someone who agrees to test a fix? Maybe we can accumulate a list of volunteers who'd be willing to be assigned in a work-wheel-like system?
Would it be possible to assign teams to each ticket, where we identify up front someone who agrees to '''verify''' a ticket, and someone who agrees to test a fix? Maybe we can accumulate a list of volunteers who'd be willing to be assigned in a work-wheel-like system?