779
edits
Changes
Jump to navigation
Jump to search
mLine 20:
Line 20: − + − + + + + + + + + + + + + + + + + + + + + + + + + +
→Current goals and projects
I tend to set my goals in 6-month cycles mirroring the Sugar release schedule, so these are my goals for the the '''0.86 release cycle (March 1, 2009 - September 1, 2009).''' This list is super-flexible; stuff changes all the time, random cool ideas come up, and so this has deliberately been planned with lots of wiggle room. As things change, I (usually remember to) edit this page to reflect that.
I tend to set my goals in 6-month cycles mirroring the Sugar release schedule, so these are my goals for the the '''0.86 release cycle (March 1, 2009 - September 1, 2009).''' This list is super-flexible; stuff changes all the time, random cool ideas come up, and so this has deliberately been planned with lots of wiggle room. As things change, I (usually remember to) edit this page to reflect that.
* Maintainer of the [http://git.sugarlabs.org/projects/irc IRC Activity].
=== Entry points for all SL teams ===
* Working on an [[Activity development sprint]] with Jerome Gotangco and a deployment in the Philippines.
'''Goal: There should be at least one mapped-out-and-tested new contributor experience for every SL team - something that takes people from "I want to get involved with Sugar by working on this team" to independently contributing and able to mentor newcomers to that team themselves. I want to personally experience, improve, and document them, and encourage others to go through them and give feedback.''' (All these things will be done in partnership with and with the approval of Team leaders.)
* Maintain the [http://git.sugarlabs.org/projects/irc IRC Activity] for Activity Team.
* Run at least one BugSquad sprint and mentor someone else in running a BugSquad sprint for BugSquad Team.
* Provide a weekly feedback report to Deployment Team for the Sugar deployments I'm involved with.
* Produce the next draft of a Sugar Deployment Guide with Deployment and Documentation teams, possibly at another FLOSSmanuals sprint.
* Work with Documentation Team to make guides for how to get started in each community team.
* Work with Design Team to design and execute an appropriate small project for this cycle (perhaps a "get swag!" listing page).
* Have at least 4 accepted patches to sugar-core or SoaS for this release cycle for DevelopmentTeam.
* Run an [[Activity development sprint]] with Jerome Gotangco and a deployment in the Philippines with a strong focus on educator feedback for the Education Team.
* Define and offer hosting service packages for Local Labs and Deployments with Infrastructure Team.
* Write a monthly group profile for Marketing Team.
* Make (or improve) a redirect bot for Wiki Team.
=== Well-defined open projects ===
=== Local Labs formation and communication should be easy ===
=== Strong team leadership ===
=== Make myself obsolete ===
=== Not sorted yet ===
* Testing the 0.84 release, focusing on the development and execution of [[smoke test]] procedures by working with the Olin College team's sprint cycles driven by Elsa Culler and Colin Zwiebel. After smoke testing is solid, I plan on working to improve the quality of bugs filed in Trac.
* Testing the 0.84 release, focusing on the development and execution of [[smoke test]] procedures by working with the Olin College team's sprint cycles driven by Elsa Culler and Colin Zwiebel. After smoke testing is solid, I plan on working to improve the quality of bugs filed in Trac.
* Doing QA for the [[AddonsPortal]] project. Need to set down testing and feedback cycles for that.
* Doing QA for the [[AddonsPortal]] project. Need to set down testing and feedback cycles for that.