Hi Gary, Caroline <div class="gmail_quote">On Wed, Jan 21, 2009 at 11:31 AM, Gary C Martin <<a href="mailto:gary@garycmartin.com">gary@garycmartin.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi Caroline,<div class="Ih2E3d"> On 21 Jan 2009, at 15:06, Caroline Meeks wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> How about combining Developer, Web Developer and Administrator into one and adding "Educator" </blockquote> </div> Hmmm, developer and web-developer are pretty different skills/tasks to fold into a role, I was actually in mind that really the developer role should be split into core-developer and activity-developer as the skill/knowledge sets can be so different (a teacher is unlikely to be a core-developer, but hopefully very likely to be an activity-developer).</blockquote> <div> I agree with the content of what you are saying. However my goal for *this* page is to encourage people to click to the next page without having to think deeply. On the follow up pages we can go into more details. For technical people we can talk to them about core-development vs activity-development vs web work. But if we show teachers a page that makes them think about whether they are a Core Developer or a Web Developer they are going to just click the back button. This first page needs to be a no brainer. It needs to be a simple choice where you look and you immediately know which 1, 2 or 3 buttons you want to click and you pretty much immediately know which one you want to click first. I think anyone brand new to the project *even a developer* would have to think about whether they are a core or activity developer.  Not that thinking is bad, but I am suggesting that all thinking should be done on the next page, where we can write more targeted content.   </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I agree that an educator role is an obvious add, but in reality I'd want to put just about every other role skill under educator as I think we need educators working in all roles! Anyway, perhaps having educator skills/knowledge pushing all roles is enough; here's a quick stab at a possible Educator role text (please do make some edits!!)</blockquote> <div> Most of the teams need a mix of people, our job on the next page is to describe to them how someone with that skillset can contribute to the different teams. ex: Deployment teams need writer people to write and distribute press releases.   </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Description of this role: Focus on Sugar's educational needs. Skills you possess or want to learn: Explaining complex ideas well, people skills, teaching through digital objects, understanding of educational theories and obstacles, paedagogy, ability to communicate with and influence develkopers. Teams associated with this role: EducationTeam, ActivityTeam, DeploymentTeam Tasks typical in this role: Lesson plans, teacher guides, text book templates/samples, articles, leverage Sugar as an ideal platform for learning, provide guidance and feedback to those working on technical aspects of Sugar, setting educational goals.</blockquote> <div> looks like a good start to me. Thanks! </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> For the record, from feedback so far (and my own opinion) leans me in the direction of adding 3 new roles; an educator role, a testing-QA role, and splitting out a separate activity-developer role from the core-developer role. Anymore for anymore? :-) --Gary<div><div></div><div class="Wj3C7c"> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I think technical people are more clueful about what their skills are and will click through to the next page where we can spell out specific skills and specific tasks. I think we need to be explicitly welcoming to Educators. I think a teacher looking at the current page would not know where to click. Caroline On Sat, Jan 17, 2009 at 9:22 PM, Bernie Innocenti <<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a>> wrote: Gary, your work on <a href="http://sugarlabs.org/go/Sugar_Labs/GettingInvolved" target="_blank">http://sugarlabs.org/go/Sugar_Labs/GettingInvolved</a> is TOTALLY AWESOME! Thank you very much for taking care of it. --  // Bernie Innocenti - <a href="http://www.codewiz.org/" target="_blank">http://www.codewiz.org/</a>  \X/  Sugar Labs       - <a href="http://www.sugarlabs.org/" target="_blank">http://www.sugarlabs.org/</a> _______________________________________________ IAEP -- It's An Education Project (not a laptop project!) <a href="mailto:IAEP@lists.sugarlabs.org" target="_blank">IAEP@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a> -- Caroline Meeks Solution Grove Caroline@SolutionGrove.com 617-500-3488 - Office 505-213-3268 - Fax </blockquote> </div></div></blockquote></div> -- Caroline Meeks Solution Grove Caroline@SolutionGrove.com 617-500-3488 - Office 505-213-3268 - Fax