<div dir="auto">Awesome looking forward to this, I would love to be a mentor this year<div dir="auto"> </div><div dir="auto">Regards</div></div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Oct 11, 2019, 11:56 PM James Cameron <<a href="mailto:quozl@laptop.org" target="_blank" rel="noreferrer">quozl@laptop.org</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Nice to have so many people wanting to be involved in mentoring, but you must be involved in Sugar Labs. Please use and test Music Blocks, Sugarizer, and Sugar. Please post about your tests; what worked well, what didn't work, and if you can use GitHub create issues. Where you have selected mentoring for coding, write some more code. Where you have selected mentoring for design, get involved in user experience research or user interface design and interaction. Where you have chosen mentoring for documentation, write some more documentation. You can't teach what you don't do. Google says this in <a href="https://developers.google.com/open-source/gci/faq#how_can_i_be_a_mentor_for_google_code-in" rel="noreferrer noreferrer noreferrer" target="_blank">https://developers.google.com/open-source/gci/faq#how_can_i_be_a_mentor_for_google_code-in</a> "You should already be a participant in the organization/open source project that you wish to be a mentor for." After past experiences I'm not interested in mentors who don't know what Sugar Labs software does or how it can be used. Such mentors are disruptive. They say things that are wrong. They make technical decisions in ignorance. In short, they misrepresent our community of designers, developers, and documenters. Mentors who don't even have time to try out our software can avoid this dissonance by; - passing on to others questions that are outside their knowledge, - asking public questions on behalf of a student, - when time is of the essence, approve a task and leave the details of how it is tidied up to the people who know best, When a student asks you a question in private you don't know the answer to, don't make something up yourself. Get them involved in community and communicating in the open; Google says this in <a href="https://developers.google.com/open-source/gci/help/responsibilities#to_your_students" rel="noreferrer noreferrer noreferrer" target="_blank">https://developers.google.com/open-source/gci/help/responsibilities#to_your_students</a> "Mentor Responsibilities ... to your Students ... Help and/or teach the student how to ... be a part of your community ... communicate more effectively and in the open". Hope that helps! -- James Cameron <a href="http://quozl.netrek.org/" rel="noreferrer noreferrer noreferrer" target="_blank">http://quozl.netrek.org/</a> _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org" rel="noreferrer noreferrer" target="_blank">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer noreferrer noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote></div>