[IAEP] [Sugar-devel] Google Code-in 2019

Oluebube Oti oluebubeoti at gmail.com
Sun Oct 13 03:22:56 EDT 2019

Hello everyone my name is Oluebube Oti, am a product designer from Nigeria.
I have been following Sugarlabs for a while now, love what the organization
is doing with open source and education. am familiar with sugarizer and i
have alos done some translation as a volunteer contributor on the
translate.sugarlabs.org platform. Please I would love to mentor as a design
mentor for Google code-in 2019, how can i apply? Thanks.

On Sat, 12 Oct 2019, 5:30 AM Favour Kelvin, <favourkelvin17 at gmail.com>

> Awesome looking forward to this, I would love to be a mentor this year
> Regards
> On Fri, Oct 11, 2019, 11:56 PM James Cameron <quozl at laptop.org> wrote:
>> 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
>> https://developers.google.com/open-source/gci/faq#how_can_i_be_a_mentor_for_google_code-in
>> "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
>> https://developers.google.com/open-source/gci/help/responsibilities#to_your_students
>> "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
>> http://quozl.netrek.org/
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
> _______________________________________________
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/iaep/attachments/20191013/a840cff1/attachment.html>

More information about the IAEP mailing list