779
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: − + Line 19:
Line 19: + + + + + + + + − + + + + Line 31:
Line 42: − + + − + − === Local Labs formation and communication should be easy ===+ − === Strong team leadership ===+ − + − === 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. − * Doing QA for the [[Addons Portal]] project. Need to set down testing and feedback cycles for that. − * Helping out with odd jobs for [[Marketing Team]], mostly involving community development (right now: clarifying the distinction between university chapters, ambassadors, Local Labs, geographic interest groups, and deployment teams, alongside the Deployment Team). − * Google Summer of Code 2009 coordination, along with other spring/summer '09 internship/mentorship initiatives. − * [[Marketing Team/Sugar_stories|Interviewing Sugar Labs contributors]] for profiles for the Marketing team.
no edit summary
{{TOCright}} My name is [http://blog.melchua.com/about/ Mel Chua], and this page describes the OLPC-related projects I'm working on. Feel free to [http://blog.melchua.com/contact/ contact me] with any comments, questions, or ideas you might have, or check and see if I'll be [http://www.dopplr.com/traveller/mchua/ traveling near you] sometime soon.
{{TOCright}} My name is [http://blog.melchua.com/about/ Mel Chua], and this page describes the Sugar-related projects I'm working on. Feel free to [http://blog.melchua.com/contact/ contact me] with any comments, questions, or ideas you might have, or check and see if I'll be [http://www.dopplr.com/traveller/mchua/ traveling near you] sometime soon.
English is my native language. I have a basic understanding of [http://en.wikipedia.org/wiki/American_sign_language ASL]. 这个用户是能够有助于满足于基本 水平的 中国人。 この利用者は少しだけ日本語を話すことができます。 Estoy aprendiendo español. Sto imparando l’italiano. Ako ay pag-aaral ng Tagalog.
English is my native language. I have a basic understanding of [http://en.wikipedia.org/wiki/American_sign_language ASL]. 这个用户是能够有助于满足于基本 水平的 中国人。 この利用者は少しだけ日本語を話すことができます。 Estoy aprendiendo español. Sto imparando l’italiano. Ako ay pag-aaral ng Tagalog.
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.
I was sidelined with RSI for much of this release cycle, so priorities have been adjusted accordingly. For
* Google Summer of Code 2009 co-coordination with Jameson Quinn, focused on linking each student project with a Sugar deployment for testing and feedback (including starting a SoaS pilot near them, if needed - this is how I'd prefer to do it).
== Future goals and projects ==
Feel free to pick up on these or let me know if you would like to help!
=== Entry points for all SL teams ===
=== Entry points for all SL teams ===
'''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.)
'''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. This should be done by contributors who want to personally experience, improve, and document them, and encourage others to go through them and give feedback.''' (All these things would be done in partnership with and with the approval of Team leaders.)
Here are projects for each team that could be picked up. I am willing to help match people with mentors for each task. The point of doing these things is not just "do this for team X," but to explore how welcoming team X is to newcomers who want to contribute, and how this experience could be improved - think of yourself as a mystery shopper, except not-so-mysterious (the fact that you're doing this to test out "newbie routes" is totally transparent).
* [[Marketing Team/Sugar_stories|Interviewing Sugar Labs contributors]] for profiles for the Marketing team.
* Maintain the [http://git.sugarlabs.org/projects/irc IRC Activity] for Activity Team.
* 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.
* Run at least one BugSquad sprint and mentor someone else in running a BugSquad sprint for BugSquad Team.
* Work with Design Team to design and execute an appropriate small project for this cycle (perhaps a "get swag!" listing page).
* 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 Development Team.
* Have at least 4 accepted patches to sugar-core or SoaS for this release cycle for Development Team.
* 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.
* Run an [[Activity development sprint]] 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.
* Define and offer hosting service packages for Local Labs and Deployments with Infrastructure Team.
* Write a monthly group profile for Marketing Team.
* Write a monthly group profile for Marketing Team.
* Make (or improve) a redirect bot for Wiki Team.
* Make (or improve) a redirect bot for Wiki Team.
* Doing QA for the [[Addons Portal]] project. The first step is to find out (or write down) testing and feedback cycles for its development.
=== Well-defined open projects ===
=== Well-defined open tasks ===
SL's trac should include a component for each team's tasks (not just code bugs!) and also a keyword for newbies to search for, so we can tag getting-started tasks. Each of these getting-started tasks should have a mentor associated with it and information that would enable each newbie to find that mentor to shepherd and sponsor them through the beginning-contributor process. Finally, the task log should be kept populated with useful things to do and monitored through at least the first dozen newbies to see how they experience it, then passed on to one of those newcomers to maintain. I would be willing to mentor this task.
One could imagine a similar (maintained) list of open projects (concrete accomplishments larger than a single task). This may actually be a better place to start. The first task would be writing up a short guide as to what constitutes a good project proposal and submitting the draft to [http://lists.sugarlabs.org/listinfo/iaep iaep] for feedback. I would be willing to mentor this task.
=== Make myself obsolete ===
=== Local Labs formation and communication should be easy ===
There should be a guide and case studies for formation of Local Labs. The interface for participating this way should be clear - what is a Local Lab? Why would you start one? What are the requirements to do so? And so forth. This is probably best done in conjunction with groups who are in the process of starting Local Labs right now. I would be willing to help find someone to mentor this task (I imagine there are better mentors for this than me).
== History ==
== History ==
I do stuff. This page needs a facelift.
I do stuff. This page needs a facelift.