Re: [Sugar-devel] Google Code-in 2019

[ANIKET MATHUR]

G'day everyone,

I wish to mentor GCI 2019 for Sugar Labs. I have a query about how to add
my name to the mentor list on the wiki page,
do I need a Sugar Labs wiki account for that?

Thanks!

On Wed, Oct 30, 2019 at 9:23 PM Euan Ong  wrote:

> Dear Walter,
>
> Great to see Sugar Labs has been accepted for GCI 2019 :) I'd definitely
> be interested in mentoring this year.
>
> Best regards,
> Euan
>
> On Thu, 10 Oct 2019 at 22:56, Walter Bender 
> wrote:
>
>> I've begun putting together our application to GCI 2019. And I have
>> created a page in the wiki with background information [2]
>>
>> If you are interested in mentoring, please let me know (and add your name
>> to the list at the bottom of the wiki page.). Please indicate what areas
>> you wish to help with (coding, design, research, documentation, and QA) and
>> relevant experience in the Sugar Labs community.
>>
>> Looking forward to GCI.
>>
>> regards.
>>
>> -walter
>>
>> [1] https://codein.withgoogle.com/
>> [2] https://wiki.sugarlabs.org/go/Google_Code_In_2019
>>
>> --
>> Walter Bender
>> Sugar Labs
>> http://www.sugarlabs.org
>> 
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Code-in 2019

[Euan Ong]

Dear Walter,

Great to see Sugar Labs has been accepted for GCI 2019 :) I'd definitely be
interested in mentoring this year.

Best regards,
Euan

On Thu, 10 Oct 2019 at 22:56, Walter Bender  wrote:

> I've begun putting together our application to GCI 2019. And I have
> created a page in the wiki with background information [2]
>
> If you are interested in mentoring, please let me know (and add your name
> to the list at the bottom of the wiki page.). Please indicate what areas
> you wish to help with (coding, design, research, documentation, and QA) and
> relevant experience in the Sugar Labs community.
>
> Looking forward to GCI.
>
> regards.
>
> -walter
>
> [1] https://codein.withgoogle.com/
> [2] https://wiki.sugarlabs.org/go/Google_Code_In_2019
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> 
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Code-in 2019

[Favour Kelvin]

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  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@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Code-in 2019

[James Cameron]

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@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Code-in 2019

[devil hacks]

Hi everyone,
I am Rupesh and am a full stack web developer and open source contributor.
I have contributed to some organisations like mifos, jboss etc.
Here is my github link- https://github.com/Rupeshiya.

I would love to mentor syudents in web dev related field.
Please let me know how I can get started contributing to GCI as a mentor in
this organisation.

Thanks
Rupesh


On Fri, 11 Oct 2019, 6:09 pm Deepak Kumar,  wrote:

> Hi,
> I am up for mentoring. As I am having my winter vacation during the GCI
> period so I would love to spend my time mentoring the students for the task
> and can be available for 2-3 hrs per day. Although, I am a new contributor
> to this project but am familiar with the work flow of open source as
> earlier I was contributing to KDE(Gcompris) project. I am skilled in
> Python, Javascript(novice). I can mentor students for research,
> documentation and code.
>
> Thanks
> Deepak Kumar
>
> On Fri, 11 Oct 2019, 3:26 am Walter Bender, 
> wrote:
>
>> I've begun putting together our application to GCI 2019. And I have
>> created a page in the wiki with background information [2]
>>
>> If you are interested in mentoring, please let me know (and add your name
>> to the list at the bottom of the wiki page.). Please indicate what areas
>> you wish to help with (coding, design, research, documentation, and QA) and
>> relevant experience in the Sugar Labs community.
>>
>> Looking forward to GCI.
>>
>> regards.
>>
>> -walter
>>
>> [1] https://codein.withgoogle.com/
>> [2] https://wiki.sugarlabs.org/go/Google_Code_In_2019
>>
>> --
>> Walter Bender
>> Sugar Labs
>> http://www.sugarlabs.org
>> 
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Google Code-in 2019

[Deepak Kumar]

Hi,
I am up for mentoring. As I am having my winter vacation during the GCI
period so I would love to spend my time mentoring the students for the task
and can be available for 2-3 hrs per day. Although, I am a new contributor
to this project but am familiar with the work flow of open source as
earlier I was contributing to KDE(Gcompris) project. I am skilled in
Python, Javascript(novice). I can mentor students for research,
documentation and code.

Thanks
Deepak Kumar

On Fri, 11 Oct 2019, 3:26 am Walter Bender,  wrote:

> I've begun putting together our application to GCI 2019. And I have
> created a page in the wiki with background information [2]
>
> If you are interested in mentoring, please let me know (and add your name
> to the list at the bottom of the wiki page.). Please indicate what areas
> you wish to help with (coding, design, research, documentation, and QA) and
> relevant experience in the Sugar Labs community.
>
> Looking forward to GCI.
>
> regards.
>
> -walter
>
> [1] https://codein.withgoogle.com/
> [2] https://wiki.sugarlabs.org/go/Google_Code_In_2019
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> 
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel