10,505
edits
Changes
Jump to navigation
Jump to search
Line 60:
Line 60: − + Line 82:
Line 82: − +
→Questions
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?
Would it make sense to consistently add keywords that map to the Sugar modules?
Would it make sense to consistently add '''keywords''' that map to the Sugar modules or should these be '''components'''?
* sugar
* sugar
* sugar-base
* sugar-base
:Low: odds and ends
:Low: odds and ends
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?
[[Category:Developer]]
[[Category:Developer]]