779
edits
Changes
Talk:Sugar on a Stick/Getting Involved (view source)
Revision as of 00:19, 26 April 2010
, 00:19, 26 April 2010Created page with ''''content from a brainstorm on april 25, 2010 by Sebastian Dziallas and Mel Chua, to be revisited later.''' link to openhatch here? * what kind of …'
'''content from a brainstorm on april 25, 2010 by [[User:Sdz|Sebastian Dziallas]] and [[User:Mchua|Mel Chua]], to be revisited later.'''
link to openhatch here?
* what kind of contributors are we looking for (I know, "all types," but specifically what sort of talent is needed to do what kind of tasks right now, just for the development of v.4?)
* bug triagers for support
* package maintainers
* testers
* deployers
* more here
* for each contributor type:
** what background do they need to have / skills they should acquire?
* bug triagers: familiarity with the sugar environment, being able to differentiate between components (to assign a ticket to the appropriate component), know how to get access to logs (makes debugging easier)
* packagers: read rpm creation guide, have a look at a sample activity (class Mel and Sebastian taught - logs), get Fedora account, become a packager
* testers: not much, everyone can test! also hint to nightly builds (need test cases!)
* deployers: not in our target group here? otherwise: are you a teacher? start *your* deployment and contribute to make SoaS even more awesome, we also help with remixes and stuff to fit your needs
* pedagogical designers: teachers, parents, and others in education, coming up with curricular materials for using Sugar Activities in the classroom, and designs/modifications for Activities to better fit pedagogical goals
** what tasks need to be completed? why are they important, how do they fit into the bigger picture?
* bug triagers: make sure that our users aren't left high and dry. we need to be able to track issues and to react to them, interact directly both with users and developers to make sure stuff is properly assigned
* packagers: must be able to react immediately to new releases, package them and push updates as needed, has a high responsability, has to interact with testers
* testers: *test* and file tickets on issues you encounter, add logs (link to Mel's guide)
* deployment: we need information from the field - deployments are what we're doing this for, so get started and become a part of it!
** how do they get started? what interface do we want to have with them (forum, chat, etc?) how do they get to those? what sort of timescale are they looking at? (weekly meetings? how quickly can they expect feedback?)
http://openhatch.org/+projects/Sugar on a Stick (<--- wooooo :) -- let's get something like help.sugaronastick.org ?
http://openhatch.org/+projects/sugar (<---somebody who wants to help!!!)
link to openhatch here?
* what kind of contributors are we looking for (I know, "all types," but specifically what sort of talent is needed to do what kind of tasks right now, just for the development of v.4?)
* bug triagers for support
* package maintainers
* testers
* deployers
* more here
* for each contributor type:
** what background do they need to have / skills they should acquire?
* bug triagers: familiarity with the sugar environment, being able to differentiate between components (to assign a ticket to the appropriate component), know how to get access to logs (makes debugging easier)
* packagers: read rpm creation guide, have a look at a sample activity (class Mel and Sebastian taught - logs), get Fedora account, become a packager
* testers: not much, everyone can test! also hint to nightly builds (need test cases!)
* deployers: not in our target group here? otherwise: are you a teacher? start *your* deployment and contribute to make SoaS even more awesome, we also help with remixes and stuff to fit your needs
* pedagogical designers: teachers, parents, and others in education, coming up with curricular materials for using Sugar Activities in the classroom, and designs/modifications for Activities to better fit pedagogical goals
** what tasks need to be completed? why are they important, how do they fit into the bigger picture?
* bug triagers: make sure that our users aren't left high and dry. we need to be able to track issues and to react to them, interact directly both with users and developers to make sure stuff is properly assigned
* packagers: must be able to react immediately to new releases, package them and push updates as needed, has a high responsability, has to interact with testers
* testers: *test* and file tickets on issues you encounter, add logs (link to Mel's guide)
* deployment: we need information from the field - deployments are what we're doing this for, so get started and become a part of it!
** how do they get started? what interface do we want to have with them (forum, chat, etc?) how do they get to those? what sort of timescale are they looking at? (weekly meetings? how quickly can they expect feedback?)
http://openhatch.org/+projects/Sugar on a Stick (<--- wooooo :) -- let's get something like help.sugaronastick.org ?
http://openhatch.org/+projects/sugar (<---somebody who wants to help!!!)