[Pharo-dev] Google Summer of Code 2018 with Pharo Consortium

[Jigyasa Grover]

Hello Pharo-ers ! 

On behalf of the community, I would like to thank each one of you for their
significant contribution in the previously concluded *Google Summer of Code
2017* with *Pharo Consortium*. We aspire to take-off on a long flight after
this successful stint by applying to participate in the upcoming *Google
Summer of Code 2018*.

As many of you might know, Google Summer of Code is a global program focused
on bringing more student developers into open source software development.
Students work with an open source organization on a 3 month programming
project during their break from school. Read more about the program here:
https://summerofcode.withgoogle.com/

The deadline for organisations to apply is January 23, 2018 which is fast
approaching. As an open source evangelist and a Pharo developer, I would
like to invite all the experienced members to be a part of the "GSoC 2018
with Pharo Consortium" Team and mentor students. Propose fresh ideas for
projects which shall help improve Pharo or volunteer to mentor any of the
existing one (Listed here: http://gsoc.pharo.org/). To add your own project
idea to the list, visit http://gsoc.pharo.org/#adding-a-proposal

Looking forward to an appreciable representation from the Pharo community. 

Best regards 
Jigyasa Grover 
Pharo Consortium Org Admin, Google Summer of Code 2017 [hidden email]





--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] Google Summer of Code - New Trait Implementation

[teso...@gmail.com]

Thank you, I have submitted.

Cheers,
Pablo

On Fri, Mar 31, 2017 at 3:29 PM, Jigyasa Grover 
wrote:

> Hey Pablo
>
> Great idea !
>
> Submit your proposal ASAP at summerofcode.withgoogle.com for review and
> feedback.
>
> Good luck :)
>
> Best
> Jigyasa Grover
> GSoC 2017 Org Admin, Pharo Consortium
>
>
>
> On Fri, Mar 31, 2017 at 6:26 PM, Stephane Ducasse  > wrote:
>
>> go
>> go go go
>>
>> On Fri, Mar 31, 2017 at 2:14 PM, teso...@gmail.com 
>> wrote:
>>
>>> Hello,
>>>
>>> I am planning in working in a new Traits implementation, the idea is to
>>> have an implementation that can work as a loadable module. So you can use
>>> it or not as another library.
>>>
>>> Also the idea is improve the support of all the tools by improving the
>>> polymorphism between traits and classes. Clean up a little the API and add
>>> support to have stateful traits.
>>>
>>> I would like to know if you have any suggestion or have a problem that I
>>> could try to solve. I have been talking with some people in the community
>>> to get ideas, but always having more opinions is better.
>>>
>>> Thanks in advance.
>>> Pablo
>>>
>>>
>>> --
>>> Pablo Tesone.
>>> teso...@gmail.com
>>>
>>
>>
>


-- 
Pablo Tesone.
teso...@gmail.com

Re: [Pharo-dev] Google Summer of Code - New Trait Implementation

[Jigyasa Grover]

Hey Pablo

Great idea !

Submit your proposal ASAP at summerofcode.withgoogle.com for review and
feedback.

Good luck :)

Best
Jigyasa Grover
GSoC 2017 Org Admin, Pharo Consortium



On Fri, Mar 31, 2017 at 6:26 PM, Stephane Ducasse 
wrote:

> go
> go go go
>
> On Fri, Mar 31, 2017 at 2:14 PM, teso...@gmail.com 
> wrote:
>
>> Hello,
>>
>> I am planning in working in a new Traits implementation, the idea is to
>> have an implementation that can work as a loadable module. So you can use
>> it or not as another library.
>>
>> Also the idea is improve the support of all the tools by improving the
>> polymorphism between traits and classes. Clean up a little the API and add
>> support to have stateful traits.
>>
>> I would like to know if you have any suggestion or have a problem that I
>> could try to solve. I have been talking with some people in the community
>> to get ideas, but always having more opinions is better.
>>
>> Thanks in advance.
>> Pablo
>>
>>
>> --
>> Pablo Tesone.
>> teso...@gmail.com
>>
>
>

Re: [Pharo-dev] Google Summer of Code - New Trait Implementation

[Stephane Ducasse]

go
go go go

On Fri, Mar 31, 2017 at 2:14 PM, teso...@gmail.com 
wrote:

> Hello,
>
> I am planning in working in a new Traits implementation, the idea is to
> have an implementation that can work as a loadable module. So you can use
> it or not as another library.
>
> Also the idea is improve the support of all the tools by improving the
> polymorphism between traits and classes. Clean up a little the API and add
> support to have stateful traits.
>
> I would like to know if you have any suggestion or have a problem that I
> could try to solve. I have been talking with some people in the community
> to get ideas, but always having more opinions is better.
>
> Thanks in advance.
> Pablo
>
>
> --
> Pablo Tesone.
> teso...@gmail.com
>

[Pharo-dev] Google Summer of Code - New Trait Implementation

[teso...@gmail.com]

Hello,

I am planning in working in a new Traits implementation, the idea is to
have an implementation that can work as a loadable module. So you can use
it or not as another library.

Also the idea is improve the support of all the tools by improving the
polymorphism between traits and classes. Clean up a little the API and add
support to have stateful traits.

I would like to know if you have any suggestion or have a problem that I
could try to solve. I have been talking with some people in the community
to get ideas, but always having more opinions is better.

Thanks in advance.
Pablo


-- 
Pablo Tesone.
teso...@gmail.com

Re: [Pharo-dev] Google Summer of Code 2017: Call for mentors for Pharo Consortium

[Serge Stinckwich]

Dear all,

we have 10 mentors + 4 admin at the moment. We are looking for me !
Please join the #gsoc-planning Slack channel.
Thank you.

On Wed, Mar 1, 2017 at 1:45 PM, Serge Stinckwich
 wrote:
> Heartiest Congratulations !
>
> Pharo Consortium has been selected as a mentor organisation for Google
> Summer of Code 2017.
>
> Google Summer of Code is a global program focused on introducing
> students to open source software development.
>
> Students work on a 3 month programming project with an open source
> organisation during their break from university. Read more at
> https://summerofcode.withgoogle.com/
>
> How the program works ?
>
> Organizations:
> Open source projects apply to be mentor organizations. Once accepted,
> organizations discuss possible ideas with students and then decide on
> the proposals they wish to mentor for the summer. They provide mentors
> to help guide each student through the program.
>
> Mentors:
> Existing contributors with the organizations can choose to mentor a
> student project. Mentors and students work together to determine
> appropriate milestones and requirements for the summer. Mentor
> interaction is a vital part of the program. A mentor may propose or
> endorse a project  and each project has to be about Pharo or its
> ecosystem (e.g., a library). Projects will be mentored by one or more
> mentors and executed by one student.
>
> Students:
> Students contact the mentor organizations they want to work with and
> write up a project proposal for the summer. If accepted, students
> spend a month integrating with their organizations prior to the start
> of coding. Students then have three months to code, meeting the
> deadlines agreed upon with their mentors. Student coding period: May
> 30 - Aug 29 (Entire timeline can be viewed at:
> https://summerofcode.withgoogle.com/how-it-works/#timeline). Student
> stipend: https://developers.google.com/open-source/gsoc/help/student-stipends
>
> We are currently at the phase of identifying mentors and projects. The
> next phases will be about students selecting projects, and the
> community selecting the projects with their associated mentors and
> students which will be sponsored by the GSOC program.
>
> How to register ?
> Simply by replying to this email and joining the Slack channel... to
> have more discussion about what project the mentor will take up, what
> she/he wants at the end of the coding period and then we can invite
> them to the GSoC org dashboard).
>
> Hence, we invite regular & enthusiastic Pharo contributors to be a
> mentor with Pharo Consortium for GSoC 2017:
>
> 1. Kindly respond on this thread if you'd like to be a mentor, or wish
> to propose a project.
>
> An existing list of projects is already available here:
> http://gsoc.pharo.org/ and we already have a handful of projects and
> mentors chosen. Feel free to collaborate with existing mentors as
> well.
>
> 2. Join dedicated channels, #gsoc-students for general interactions
> with students & #gsoc-planning channel only for GSOC admins and
> mentors on Pharo slack. In order to get an invitation for
> pharoproject.slack.com visit the URL here:
> http://slackinvites.pharo.org/
>
> 3. Please open relevant issues and make a roadmap of the projects
> being mentored by you so that students can start contributing to them
> already. If you want to mentor a project and there is no open-source
> repository at the moment, please built one ASAP.
>
> 4. If you know any students that might be interested to work on Pharo
> during the summer and be a part of GSoC as well, please ask him/her to
> start contributing to the Pharo projects, discuss their proposal,
> follow instructions that shall be posted soon in this mailing thread
> and submit their application by April 3, 2017.
> We don't know the number of slots attributed by Google to Pharo org,
> but the more students proposal we will receive, the more slots will be
> attributed to us.
>
> We remind you about the mentor responsibilities:
>
> ... to your Org Admins
>
> - Communicate availability and interaction expectations
> - Inform when mentoring capacity will be reduced, as early as possible
> (e.g., family, health, vacation)
> - Inform when there is an issue with a student
>- Lacking communication, activity, visibility (MIA), or progress
>- Participant Agreement violations (e.g., plagiarism, harassment, fraud)
>- Bad fit or stepping down
> - Formally evaluate student participation.
>- Communicate with admin and student before failing
>
> ... to your Students
>
> - Help and/or teach the student
>- how to be a part of your community
>- communicate more effectively and in the open
>- work with your org’s preferred communication channel (IRC, Slack, etc)
>- use your org’s version control system
>- ask good questions and get answers to their questions
>- provide convincing technical argument and constructive discussion
>- be independently 

Re: [Pharo-dev] Google Summer of Code 2017: Call for mentors for Pharo Consortium

[Max Leske]

It seems that I can’t. It’s not in the list of channels, I guess I have to be 
invited.

> On 1 Mar 2017, at 20:19, Serge Stinckwich  wrote:
> 
> Please join the #gsoc-planning channel on Slack !
> 
> On Wed, Mar 1, 2017 at 8:16 PM, Max Leske  wrote:
>> Good stuff!
>> 
>> I’m up for mentoring.
>> 
>>> On 1 Mar 2017, at 13:45, Serge Stinckwich  
>>> wrote:
>>> 
>>> Heartiest Congratulations !
>>> 
>>> Pharo Consortium has been selected as a mentor organisation for Google
>>> Summer of Code 2017.
>>> 
>>> Google Summer of Code is a global program focused on introducing
>>> students to open source software development.
>>> 
>>> Students work on a 3 month programming project with an open source
>>> organisation during their break from university. Read more at
>>> https://summerofcode.withgoogle.com/
>>> 
>>> How the program works ?
>>> 
>>> Organizations:
>>> Open source projects apply to be mentor organizations. Once accepted,
>>> organizations discuss possible ideas with students and then decide on
>>> the proposals they wish to mentor for the summer. They provide mentors
>>> to help guide each student through the program.
>>> 
>>> Mentors:
>>> Existing contributors with the organizations can choose to mentor a
>>> student project. Mentors and students work together to determine
>>> appropriate milestones and requirements for the summer. Mentor
>>> interaction is a vital part of the program. A mentor may propose or
>>> endorse a project  and each project has to be about Pharo or its
>>> ecosystem (e.g., a library). Projects will be mentored by one or more
>>> mentors and executed by one student.
>>> 
>>> Students:
>>> Students contact the mentor organizations they want to work with and
>>> write up a project proposal for the summer. If accepted, students
>>> spend a month integrating with their organizations prior to the start
>>> of coding. Students then have three months to code, meeting the
>>> deadlines agreed upon with their mentors. Student coding period: May
>>> 30 - Aug 29 (Entire timeline can be viewed at:
>>> https://summerofcode.withgoogle.com/how-it-works/#timeline). Student
>>> stipend: 
>>> https://developers.google.com/open-source/gsoc/help/student-stipends
>>> 
>>> We are currently at the phase of identifying mentors and projects. The
>>> next phases will be about students selecting projects, and the
>>> community selecting the projects with their associated mentors and
>>> students which will be sponsored by the GSOC program.
>>> 
>>> How to register ?
>>> Simply by replying to this email and joining the Slack channel... to
>>> have more discussion about what project the mentor will take up, what
>>> she/he wants at the end of the coding period and then we can invite
>>> them to the GSoC org dashboard).
>>> 
>>> Hence, we invite regular & enthusiastic Pharo contributors to be a
>>> mentor with Pharo Consortium for GSoC 2017:
>>> 
>>> 1. Kindly respond on this thread if you'd like to be a mentor, or wish
>>> to propose a project.
>>> 
>>> An existing list of projects is already available here:
>>> http://gsoc.pharo.org/ and we already have a handful of projects and
>>> mentors chosen. Feel free to collaborate with existing mentors as
>>> well.
>>> 
>>> 2. Join dedicated channels, #gsoc-students for general interactions
>>> with students & #gsoc-planning channel only for GSOC admins and
>>> mentors on Pharo slack. In order to get an invitation for
>>> pharoproject.slack.com visit the URL here:
>>> http://slackinvites.pharo.org/
>>> 
>>> 3. Please open relevant issues and make a roadmap of the projects
>>> being mentored by you so that students can start contributing to them
>>> already. If you want to mentor a project and there is no open-source
>>> repository at the moment, please built one ASAP.
>>> 
>>> 4. If you know any students that might be interested to work on Pharo
>>> during the summer and be a part of GSoC as well, please ask him/her to
>>> start contributing to the Pharo projects, discuss their proposal,
>>> follow instructions that shall be posted soon in this mailing thread
>>> and submit their application by April 3, 2017.
>>> We don't know the number of slots attributed by Google to Pharo org,
>>> but the more students proposal we will receive, the more slots will be
>>> attributed to us.
>>> 
>>> We remind you about the mentor responsibilities:
>>> 
>>> ... to your Org Admins
>>> 
>>> - Communicate availability and interaction expectations
>>> - Inform when mentoring capacity will be reduced, as early as possible
>>> (e.g., family, health, vacation)
>>> - Inform when there is an issue with a student
>>>  - Lacking communication, activity, visibility (MIA), or progress
>>>  - Participant Agreement violations (e.g., plagiarism, harassment, fraud)
>>>  - Bad fit or stepping down
>>> - Formally evaluate student participation.
>>>  - Communicate with admin and student before failing
>>> 
>>> ... to your 

Re: [Pharo-dev] Google Summer of Code 2017: Call for mentors for Pharo Consortium

[Serge Stinckwich]

Please join the #gsoc-planning channel on Slack !

On Wed, Mar 1, 2017 at 8:16 PM, Max Leske  wrote:
> Good stuff!
>
> I’m up for mentoring.
>
>> On 1 Mar 2017, at 13:45, Serge Stinckwich  wrote:
>>
>> Heartiest Congratulations !
>>
>> Pharo Consortium has been selected as a mentor organisation for Google
>> Summer of Code 2017.
>>
>> Google Summer of Code is a global program focused on introducing
>> students to open source software development.
>>
>> Students work on a 3 month programming project with an open source
>> organisation during their break from university. Read more at
>> https://summerofcode.withgoogle.com/
>>
>> How the program works ?
>>
>> Organizations:
>> Open source projects apply to be mentor organizations. Once accepted,
>> organizations discuss possible ideas with students and then decide on
>> the proposals they wish to mentor for the summer. They provide mentors
>> to help guide each student through the program.
>>
>> Mentors:
>> Existing contributors with the organizations can choose to mentor a
>> student project. Mentors and students work together to determine
>> appropriate milestones and requirements for the summer. Mentor
>> interaction is a vital part of the program. A mentor may propose or
>> endorse a project  and each project has to be about Pharo or its
>> ecosystem (e.g., a library). Projects will be mentored by one or more
>> mentors and executed by one student.
>>
>> Students:
>> Students contact the mentor organizations they want to work with and
>> write up a project proposal for the summer. If accepted, students
>> spend a month integrating with their organizations prior to the start
>> of coding. Students then have three months to code, meeting the
>> deadlines agreed upon with their mentors. Student coding period: May
>> 30 - Aug 29 (Entire timeline can be viewed at:
>> https://summerofcode.withgoogle.com/how-it-works/#timeline). Student
>> stipend: https://developers.google.com/open-source/gsoc/help/student-stipends
>>
>> We are currently at the phase of identifying mentors and projects. The
>> next phases will be about students selecting projects, and the
>> community selecting the projects with their associated mentors and
>> students which will be sponsored by the GSOC program.
>>
>> How to register ?
>> Simply by replying to this email and joining the Slack channel... to
>> have more discussion about what project the mentor will take up, what
>> she/he wants at the end of the coding period and then we can invite
>> them to the GSoC org dashboard).
>>
>> Hence, we invite regular & enthusiastic Pharo contributors to be a
>> mentor with Pharo Consortium for GSoC 2017:
>>
>> 1. Kindly respond on this thread if you'd like to be a mentor, or wish
>> to propose a project.
>>
>> An existing list of projects is already available here:
>> http://gsoc.pharo.org/ and we already have a handful of projects and
>> mentors chosen. Feel free to collaborate with existing mentors as
>> well.
>>
>> 2. Join dedicated channels, #gsoc-students for general interactions
>> with students & #gsoc-planning channel only for GSOC admins and
>> mentors on Pharo slack. In order to get an invitation for
>> pharoproject.slack.com visit the URL here:
>> http://slackinvites.pharo.org/
>>
>> 3. Please open relevant issues and make a roadmap of the projects
>> being mentored by you so that students can start contributing to them
>> already. If you want to mentor a project and there is no open-source
>> repository at the moment, please built one ASAP.
>>
>> 4. If you know any students that might be interested to work on Pharo
>> during the summer and be a part of GSoC as well, please ask him/her to
>> start contributing to the Pharo projects, discuss their proposal,
>> follow instructions that shall be posted soon in this mailing thread
>> and submit their application by April 3, 2017.
>> We don't know the number of slots attributed by Google to Pharo org,
>> but the more students proposal we will receive, the more slots will be
>> attributed to us.
>>
>> We remind you about the mentor responsibilities:
>>
>> ... to your Org Admins
>>
>> - Communicate availability and interaction expectations
>> - Inform when mentoring capacity will be reduced, as early as possible
>> (e.g., family, health, vacation)
>> - Inform when there is an issue with a student
>>   - Lacking communication, activity, visibility (MIA), or progress
>>   - Participant Agreement violations (e.g., plagiarism, harassment, fraud)
>>   - Bad fit or stepping down
>> - Formally evaluate student participation.
>>   - Communicate with admin and student before failing
>>
>> ... to your Students
>>
>> - Help and/or teach the student
>>   - how to be a part of your community
>>   - communicate more effectively and in the open
>>   - work with your org’s preferred communication channel (IRC, Slack, etc)
>>   - use your org’s version control system
>>   - ask good questions and get answers to 

Re: [Pharo-dev] Google Summer of Code 2017: Call for mentors for Pharo Consortium

[Max Leske]

Good stuff!

I’m up for mentoring.

> On 1 Mar 2017, at 13:45, Serge Stinckwich  wrote:
> 
> Heartiest Congratulations !
> 
> Pharo Consortium has been selected as a mentor organisation for Google
> Summer of Code 2017.
> 
> Google Summer of Code is a global program focused on introducing
> students to open source software development.
> 
> Students work on a 3 month programming project with an open source
> organisation during their break from university. Read more at
> https://summerofcode.withgoogle.com/
> 
> How the program works ?
> 
> Organizations:
> Open source projects apply to be mentor organizations. Once accepted,
> organizations discuss possible ideas with students and then decide on
> the proposals they wish to mentor for the summer. They provide mentors
> to help guide each student through the program.
> 
> Mentors:
> Existing contributors with the organizations can choose to mentor a
> student project. Mentors and students work together to determine
> appropriate milestones and requirements for the summer. Mentor
> interaction is a vital part of the program. A mentor may propose or
> endorse a project  and each project has to be about Pharo or its
> ecosystem (e.g., a library). Projects will be mentored by one or more
> mentors and executed by one student.
> 
> Students:
> Students contact the mentor organizations they want to work with and
> write up a project proposal for the summer. If accepted, students
> spend a month integrating with their organizations prior to the start
> of coding. Students then have three months to code, meeting the
> deadlines agreed upon with their mentors. Student coding period: May
> 30 - Aug 29 (Entire timeline can be viewed at:
> https://summerofcode.withgoogle.com/how-it-works/#timeline). Student
> stipend: https://developers.google.com/open-source/gsoc/help/student-stipends
> 
> We are currently at the phase of identifying mentors and projects. The
> next phases will be about students selecting projects, and the
> community selecting the projects with their associated mentors and
> students which will be sponsored by the GSOC program.
> 
> How to register ?
> Simply by replying to this email and joining the Slack channel... to
> have more discussion about what project the mentor will take up, what
> she/he wants at the end of the coding period and then we can invite
> them to the GSoC org dashboard).
> 
> Hence, we invite regular & enthusiastic Pharo contributors to be a
> mentor with Pharo Consortium for GSoC 2017:
> 
> 1. Kindly respond on this thread if you'd like to be a mentor, or wish
> to propose a project.
> 
> An existing list of projects is already available here:
> http://gsoc.pharo.org/ and we already have a handful of projects and
> mentors chosen. Feel free to collaborate with existing mentors as
> well.
> 
> 2. Join dedicated channels, #gsoc-students for general interactions
> with students & #gsoc-planning channel only for GSOC admins and
> mentors on Pharo slack. In order to get an invitation for
> pharoproject.slack.com visit the URL here:
> http://slackinvites.pharo.org/
> 
> 3. Please open relevant issues and make a roadmap of the projects
> being mentored by you so that students can start contributing to them
> already. If you want to mentor a project and there is no open-source
> repository at the moment, please built one ASAP.
> 
> 4. If you know any students that might be interested to work on Pharo
> during the summer and be a part of GSoC as well, please ask him/her to
> start contributing to the Pharo projects, discuss their proposal,
> follow instructions that shall be posted soon in this mailing thread
> and submit their application by April 3, 2017.
> We don't know the number of slots attributed by Google to Pharo org,
> but the more students proposal we will receive, the more slots will be
> attributed to us.
> 
> We remind you about the mentor responsibilities:
> 
> ... to your Org Admins
> 
> - Communicate availability and interaction expectations
> - Inform when mentoring capacity will be reduced, as early as possible
> (e.g., family, health, vacation)
> - Inform when there is an issue with a student
>   - Lacking communication, activity, visibility (MIA), or progress
>   - Participant Agreement violations (e.g., plagiarism, harassment, fraud)
>   - Bad fit or stepping down
> - Formally evaluate student participation.
>   - Communicate with admin and student before failing
> 
> ... to your Students
> 
> - Help and/or teach the student
>   - how to be a part of your community
>   - communicate more effectively and in the open
>   - work with your org’s preferred communication channel (IRC, Slack, etc)
>   - use your org’s version control system
>   - ask good questions and get answers to their questions
>   - provide convincing technical argument and constructive discussion
>   - be independently motivated and productive
>   - solve difficult technical problems
> - Keep track of their progress, 

Re: [Pharo-dev] Google Summer of Code 2017: Call for mentors for Pharo Consortium

[p...@highoctane.be]

Ok for helping someone :-)

Phil

On Wed, Mar 1, 2017 at 1:45 PM, Serge Stinckwich  wrote:

> Heartiest Congratulations !
>
> Pharo Consortium has been selected as a mentor organisation for Google
> Summer of Code 2017.
>
> Google Summer of Code is a global program focused on introducing
> students to open source software development.
>
> Students work on a 3 month programming project with an open source
> organisation during their break from university. Read more at
> https://summerofcode.withgoogle.com/
>
> How the program works ?
>
> Organizations:
> Open source projects apply to be mentor organizations. Once accepted,
> organizations discuss possible ideas with students and then decide on
> the proposals they wish to mentor for the summer. They provide mentors
> to help guide each student through the program.
>
> Mentors:
> Existing contributors with the organizations can choose to mentor a
> student project. Mentors and students work together to determine
> appropriate milestones and requirements for the summer. Mentor
> interaction is a vital part of the program. A mentor may propose or
> endorse a project  and each project has to be about Pharo or its
> ecosystem (e.g., a library). Projects will be mentored by one or more
> mentors and executed by one student.
>
> Students:
> Students contact the mentor organizations they want to work with and
> write up a project proposal for the summer. If accepted, students
> spend a month integrating with their organizations prior to the start
> of coding. Students then have three months to code, meeting the
> deadlines agreed upon with their mentors. Student coding period: May
> 30 - Aug 29 (Entire timeline can be viewed at:
> https://summerofcode.withgoogle.com/how-it-works/#timeline). Student
> stipend: https://developers.google.com/open-source/gsoc/help/student-
> stipends
>
> We are currently at the phase of identifying mentors and projects. The
> next phases will be about students selecting projects, and the
> community selecting the projects with their associated mentors and
> students which will be sponsored by the GSOC program.
>
> How to register ?
> Simply by replying to this email and joining the Slack channel... to
> have more discussion about what project the mentor will take up, what
> she/he wants at the end of the coding period and then we can invite
> them to the GSoC org dashboard).
>
> Hence, we invite regular & enthusiastic Pharo contributors to be a
> mentor with Pharo Consortium for GSoC 2017:
>
> 1. Kindly respond on this thread if you'd like to be a mentor, or wish
> to propose a project.
>
> An existing list of projects is already available here:
> http://gsoc.pharo.org/ and we already have a handful of projects and
> mentors chosen. Feel free to collaborate with existing mentors as
> well.
>
> 2. Join dedicated channels, #gsoc-students for general interactions
> with students & #gsoc-planning channel only for GSOC admins and
> mentors on Pharo slack. In order to get an invitation for
> pharoproject.slack.com visit the URL here:
> http://slackinvites.pharo.org/
>
> 3. Please open relevant issues and make a roadmap of the projects
> being mentored by you so that students can start contributing to them
> already. If you want to mentor a project and there is no open-source
> repository at the moment, please built one ASAP.
>
> 4. If you know any students that might be interested to work on Pharo
> during the summer and be a part of GSoC as well, please ask him/her to
> start contributing to the Pharo projects, discuss their proposal,
> follow instructions that shall be posted soon in this mailing thread
> and submit their application by April 3, 2017.
> We don't know the number of slots attributed by Google to Pharo org,
> but the more students proposal we will receive, the more slots will be
> attributed to us.
>
> We remind you about the mentor responsibilities:
>
> ... to your Org Admins
>
> - Communicate availability and interaction expectations
> - Inform when mentoring capacity will be reduced, as early as possible
> (e.g., family, health, vacation)
> - Inform when there is an issue with a student
>- Lacking communication, activity, visibility (MIA), or progress
>- Participant Agreement violations (e.g., plagiarism, harassment, fraud)
>- Bad fit or stepping down
> - Formally evaluate student participation.
>- Communicate with admin and student before failing
>
> ... to your Students
>
> - Help and/or teach the student
>- how to be a part of your community
>- communicate more effectively and in the open
>- work with your org’s preferred communication channel (IRC, Slack, etc)
>- use your org’s version control system
>- ask good questions and get answers to their questions
>- provide convincing technical argument and constructive discussion
>- be independently motivated and productive
>- solve difficult technical problems
> - Keep track of their progress, 

[Pharo-dev] Google Summer of Code 2017: Call for mentors for Pharo Consortium

[Serge Stinckwich]

Heartiest Congratulations !

Pharo Consortium has been selected as a mentor organisation for Google
Summer of Code 2017.

Google Summer of Code is a global program focused on introducing
students to open source software development.

Students work on a 3 month programming project with an open source
organisation during their break from university. Read more at
https://summerofcode.withgoogle.com/

How the program works ?

Organizations:
Open source projects apply to be mentor organizations. Once accepted,
organizations discuss possible ideas with students and then decide on
the proposals they wish to mentor for the summer. They provide mentors
to help guide each student through the program.

Mentors:
Existing contributors with the organizations can choose to mentor a
student project. Mentors and students work together to determine
appropriate milestones and requirements for the summer. Mentor
interaction is a vital part of the program. A mentor may propose or
endorse a project  and each project has to be about Pharo or its
ecosystem (e.g., a library). Projects will be mentored by one or more
mentors and executed by one student.

Students:
Students contact the mentor organizations they want to work with and
write up a project proposal for the summer. If accepted, students
spend a month integrating with their organizations prior to the start
of coding. Students then have three months to code, meeting the
deadlines agreed upon with their mentors. Student coding period: May
30 - Aug 29 (Entire timeline can be viewed at:
https://summerofcode.withgoogle.com/how-it-works/#timeline). Student
stipend: https://developers.google.com/open-source/gsoc/help/student-stipends

We are currently at the phase of identifying mentors and projects. The
next phases will be about students selecting projects, and the
community selecting the projects with their associated mentors and
students which will be sponsored by the GSOC program.

How to register ?
Simply by replying to this email and joining the Slack channel... to
have more discussion about what project the mentor will take up, what
she/he wants at the end of the coding period and then we can invite
them to the GSoC org dashboard).

Hence, we invite regular & enthusiastic Pharo contributors to be a
mentor with Pharo Consortium for GSoC 2017:

1. Kindly respond on this thread if you'd like to be a mentor, or wish
to propose a project.

An existing list of projects is already available here:
http://gsoc.pharo.org/ and we already have a handful of projects and
mentors chosen. Feel free to collaborate with existing mentors as
well.

2. Join dedicated channels, #gsoc-students for general interactions
with students & #gsoc-planning channel only for GSOC admins and
mentors on Pharo slack. In order to get an invitation for
pharoproject.slack.com visit the URL here:
http://slackinvites.pharo.org/

3. Please open relevant issues and make a roadmap of the projects
being mentored by you so that students can start contributing to them
already. If you want to mentor a project and there is no open-source
repository at the moment, please built one ASAP.

4. If you know any students that might be interested to work on Pharo
during the summer and be a part of GSoC as well, please ask him/her to
start contributing to the Pharo projects, discuss their proposal,
follow instructions that shall be posted soon in this mailing thread
and submit their application by April 3, 2017.
We don't know the number of slots attributed by Google to Pharo org,
but the more students proposal we will receive, the more slots will be
attributed to us.

We remind you about the mentor responsibilities:

... to your Org Admins

- Communicate availability and interaction expectations
- Inform when mentoring capacity will be reduced, as early as possible
(e.g., family, health, vacation)
- Inform when there is an issue with a student
   - Lacking communication, activity, visibility (MIA), or progress
   - Participant Agreement violations (e.g., plagiarism, harassment, fraud)
   - Bad fit or stepping down
- Formally evaluate student participation.
   - Communicate with admin and student before failing

... to your Students

- Help and/or teach the student
   - how to be a part of your community
   - communicate more effectively and in the open
   - work with your org’s preferred communication channel (IRC, Slack, etc)
   - use your org’s version control system
   - ask good questions and get answers to their questions
   - provide convincing technical argument and constructive discussion
   - be independently motivated and productive
   - solve difficult technical problems
- Keep track of their progress, keep student informed as to their status
- Communicate on a regular basis, once a week or better (for GSoC)
   - Give constructive feedback, be patient, and be respectful
   - Respond to questions within 24 hours (occasionally under 36 hours is ok)
- Establish realistic work objectives and timeline expectations
- 

Re: [Pharo-dev] Google summer of code

[Ben Coman]

On Wed, Jan 25, 2017 at 4:44 PM, Thierry Goubier 
wrote:

> Hi guys,
>
> what I noted from the last attempts is that the Pharo proposal goes like
> that:
>
> - here is a nice list of project ideas
>
> - newcomers just have to use our current set of tools for interacting and
> producing code (that is
>  slack / mailing list / smalltalkhub / github / fogbugz / medium / etc...)
>
> Maybe preparing something (or planning to) a bit centralized and dedicated
> to GSoC for the last point could be nice, just to explain that we're paying
> attention to GSoC participants.
>


In the past, the GSoC participants seemed to have done their work in
isolation away from the main community.  I often felt the community didn't
hear much from most participants.
I think this is a bit adverse to the state goals of GSoC...

 * Help open source projects identify and bring in new developers. [1]
 * Help students integrate with their development community and so
encourage them to become lifetime contributors [1]
 * During the bonding period, students are expected to get to know their
project communities and participate in project discussion [1]
 * Get students engaged socially in the project. [2]
 * This is about building the STUDENT’S experience. Getting code in your
project is a nice side effect. [3]

Perhaps those are worth some focus in the application and project
selection.

[1] http://write.flossmanuals.net/gsoc-mentoring/what-is-gsoc/
[2] http://write.flossmanuals.net/gsoc-mentoring/mind-the-gap/
[3] http://write.flossmanuals.net/gsoc-mentoring/notes-for-
first-year-organizations/

cheers -ben


> Regards,
>
> Thierry
>
> 2017-01-25 9:21 GMT+01:00 Stephane Ducasse :
>
>> Yuriy I cleaned many of the proposal
>> could you do a pass on yours and keep max 4-5 of them?
>>
>> On Mon, Jan 23, 2017 at 5:15 PM, Yuriy Tymchuk 
>> wrote:
>>
>>> I can also update my projects and help with the application if needed (I
>>> was a part of the application team for the last two years I think)
>>>
>>> Uko
>>>
>>> On 22 Jan 2017, at 16:33, Jigyasa Grover 
>>> wrote:
>>>
>>> Also, a good application is equally important as the list of clearly
>>> defined projects.
>>>
>>> - J
>>>
>>> On Sun, Jan 22, 2017 at 4:30 PM, Serge Stinckwich <
>>> serge.stinckw...@gmail.com> wrote:
>>>
 The list of previous projects is here:
 https://github.com/pharo-project/pharo-project-proposals

 On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover
  wrote:
 > Dear Prof Serge
 >
 > Thanks for the introduction.
 >
 > Dear Alexandre
 > I have been a past Google Summer of Code student and also mentor
 budding
 > developers in Google Code-In.
 > This time, I was hoping to plug-in the loopholes which might have been
 > present in last year's organisation application.
 > Kindly let me know how can we collaborate further on this.
 > Looking forward to your response.
 > Thanks and Regards
 > Jigyasa
 >
 >
 > On Sat, Jan 21, 2017 at 9:06 AM,  wrote:
 >>
 >>
 >>
 >>
 >>
 >> Envoyé de mon iPhone
 >> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk  a
 écrit :
 >>
 >> What do we do?
 >>
 >>
 >>
 >> We have to apply ! ;-)
 >>
 >> We talk with Jigyasa Grover who is doing an internship in my lab at
 the
 >> moment and she is willing to help. Jigyasa was a student in a former
 Google
 >> Summer of code and is involved in several open-source initiative
 like Women
 >> who Code and FOSSASIA. She is a mentor of GoogleCodeIn.
 >>
 >> You can find a small presentation during last FOSSASIA : "
 >>
 >> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA
 >> 2016"
 >>
 >> https://m.youtube.com/watch?v=uLIzylxvIz4
 >>
 >> She has done a streaming video this morning also:
 http://goo.gl/UyclKP
 >> http://youtube.com/watch?v=2iRG_jpOL54
 >>
 >> Anyone to help her setup a small team for Pharo proposal to Google
 Summer
 >> of Code this year ?
 >>
 >>
 >> On 20 Jan 2017, at 20:38, Alexandre Bergel 
 >> wrote:
 >>
 >> Hi everyone-
 >>
 >> Google Summer of Code 2017 has officially begun! Organization
 applications
 >> open today, Thursday January 19 and are open through Thursday,
 February 9th.
 >> Please see our program site, official timeline and FAQ for more
 details.
 >>
 >> What makes a good organization application? Take a look at our
 manuals for
 >> tips and best practices.
 >>
 >> We look forward to seeing each of your applications and kicking off
 >> another great year of GSoC. If you have any questions, don’t
 hesitate to
 >> reach out to gsoc-supp...@google.com. 

Re: [Pharo-dev] Google summer of code

[Serge Stinckwich]

On Wed, Jan 25, 2017 at 7:38 AM, Stephan Eggermont  wrote:
> On 24/01/17 10:11, Guillermo Polito wrote:
>>
>> Besides, I'm interested in knowing the official reasons for why we were
>> rejected last years :P.
>
>
> That's the always the same: we get many more applications than we can
> sponsor, and we have to make a choice.

+1
yes we receive this answer last year.

One option to enhance the situation this year is maybe to have less
projects proposed by Pharo community (10-12 ?) but with more detailed
explanations. Apparently this is something important to be accepted as
an organisation by Google.

There is a small team with Jigyasa, Yuriy, Alexandre who is working on that.
If you have ideas and want to help, you can join #gsoc-planning on Slack.

Thank you.
Regards,

-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Google summer of code

[Thierry Goubier]

Hi guys,

what I noted from the last attempts is that the Pharo proposal goes like
that:

- here is a nice list of project ideas

- newcomers just have to use our current set of tools for interacting and
producing code (that is
 slack / mailing list / smalltalkhub / github / fogbugz / medium / etc...)

Maybe preparing something (or planning to) a bit centralized and dedicated
to GSoC for the last point could be nice, just to explain that we're paying
attention to GSoC participants.

Regards,

Thierry

2017-01-25 9:21 GMT+01:00 Stephane Ducasse :

> Yuriy I cleaned many of the proposal
> could you do a pass on yours and keep max 4-5 of them?
>
> On Mon, Jan 23, 2017 at 5:15 PM, Yuriy Tymchuk 
> wrote:
>
>> I can also update my projects and help with the application if needed (I
>> was a part of the application team for the last two years I think)
>>
>> Uko
>>
>> On 22 Jan 2017, at 16:33, Jigyasa Grover 
>> wrote:
>>
>> Also, a good application is equally important as the list of clearly
>> defined projects.
>>
>> - J
>>
>> On Sun, Jan 22, 2017 at 4:30 PM, Serge Stinckwich <
>> serge.stinckw...@gmail.com> wrote:
>>
>>> The list of previous projects is here:
>>> https://github.com/pharo-project/pharo-project-proposals
>>>
>>> On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover
>>>  wrote:
>>> > Dear Prof Serge
>>> >
>>> > Thanks for the introduction.
>>> >
>>> > Dear Alexandre
>>> > I have been a past Google Summer of Code student and also mentor
>>> budding
>>> > developers in Google Code-In.
>>> > This time, I was hoping to plug-in the loopholes which might have been
>>> > present in last year's organisation application.
>>> > Kindly let me know how can we collaborate further on this.
>>> > Looking forward to your response.
>>> > Thanks and Regards
>>> > Jigyasa
>>> >
>>> >
>>> > On Sat, Jan 21, 2017 at 9:06 AM,  wrote:
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> Envoyé de mon iPhone
>>> >> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk  a
>>> écrit :
>>> >>
>>> >> What do we do?
>>> >>
>>> >>
>>> >>
>>> >> We have to apply ! ;-)
>>> >>
>>> >> We talk with Jigyasa Grover who is doing an internship in my lab at
>>> the
>>> >> moment and she is willing to help. Jigyasa was a student in a former
>>> Google
>>> >> Summer of code and is involved in several open-source initiative like
>>> Women
>>> >> who Code and FOSSASIA. She is a mentor of GoogleCodeIn.
>>> >>
>>> >> You can find a small presentation during last FOSSASIA : "
>>> >>
>>> >> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA
>>> >> 2016"
>>> >>
>>> >> https://m.youtube.com/watch?v=uLIzylxvIz4
>>> >>
>>> >> She has done a streaming video this morning also:
>>> http://goo.gl/UyclKP
>>> >> http://youtube.com/watch?v=2iRG_jpOL54
>>> >>
>>> >> Anyone to help her setup a small team for Pharo proposal to Google
>>> Summer
>>> >> of Code this year ?
>>> >>
>>> >>
>>> >> On 20 Jan 2017, at 20:38, Alexandre Bergel 
>>> >> wrote:
>>> >>
>>> >> Hi everyone-
>>> >>
>>> >> Google Summer of Code 2017 has officially begun! Organization
>>> applications
>>> >> open today, Thursday January 19 and are open through Thursday,
>>> February 9th.
>>> >> Please see our program site, official timeline and FAQ for more
>>> details.
>>> >>
>>> >> What makes a good organization application? Take a look at our
>>> manuals for
>>> >> tips and best practices.
>>> >>
>>> >> We look forward to seeing each of your applications and kicking off
>>> >> another great year of GSoC. If you have any questions, don’t hesitate
>>> to
>>> >> reach out to gsoc-supp...@google.com. We’re here to help!
>>> >>
>>> >> Google Open Source Programs Office
>>> >> --
>>> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> >> Alexandre Bergel  http://www.bergel.eu
>>> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>> >>
>>> >>
>>> >>
>>> >>
>>> >
>>>
>>>
>>>
>>> --
>>> Serge Stinckwich
>>> UCBN & UMI UMMISCO 209 (IRD/UPMC)
>>> Every DSL ends up being Smalltalk
>>> http://www.doesnotunderstand.org/
>>>
>>>
>>
>>
>

Re: [Pharo-dev] Google summer of code

[Stephane Ducasse]

Yuriy I cleaned many of the proposal
could you do a pass on yours and keep max 4-5 of them?

On Mon, Jan 23, 2017 at 5:15 PM, Yuriy Tymchuk  wrote:

> I can also update my projects and help with the application if needed (I
> was a part of the application team for the last two years I think)
>
> Uko
>
> On 22 Jan 2017, at 16:33, Jigyasa Grover 
> wrote:
>
> Also, a good application is equally important as the list of clearly
> defined projects.
>
> - J
>
> On Sun, Jan 22, 2017 at 4:30 PM, Serge Stinckwich <
> serge.stinckw...@gmail.com> wrote:
>
>> The list of previous projects is here:
>> https://github.com/pharo-project/pharo-project-proposals
>>
>> On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover
>>  wrote:
>> > Dear Prof Serge
>> >
>> > Thanks for the introduction.
>> >
>> > Dear Alexandre
>> > I have been a past Google Summer of Code student and also mentor budding
>> > developers in Google Code-In.
>> > This time, I was hoping to plug-in the loopholes which might have been
>> > present in last year's organisation application.
>> > Kindly let me know how can we collaborate further on this.
>> > Looking forward to your response.
>> > Thanks and Regards
>> > Jigyasa
>> >
>> >
>> > On Sat, Jan 21, 2017 at 9:06 AM,  wrote:
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> Envoyé de mon iPhone
>> >> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk  a
>> écrit :
>> >>
>> >> What do we do?
>> >>
>> >>
>> >>
>> >> We have to apply ! ;-)
>> >>
>> >> We talk with Jigyasa Grover who is doing an internship in my lab at the
>> >> moment and she is willing to help. Jigyasa was a student in a former
>> Google
>> >> Summer of code and is involved in several open-source initiative like
>> Women
>> >> who Code and FOSSASIA. She is a mentor of GoogleCodeIn.
>> >>
>> >> You can find a small presentation during last FOSSASIA : "
>> >>
>> >> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA
>> >> 2016"
>> >>
>> >> https://m.youtube.com/watch?v=uLIzylxvIz4
>> >>
>> >> She has done a streaming video this morning also: http://goo.gl/UyclKP
>> >> http://youtube.com/watch?v=2iRG_jpOL54
>> >>
>> >> Anyone to help her setup a small team for Pharo proposal to Google
>> Summer
>> >> of Code this year ?
>> >>
>> >>
>> >> On 20 Jan 2017, at 20:38, Alexandre Bergel 
>> >> wrote:
>> >>
>> >> Hi everyone-
>> >>
>> >> Google Summer of Code 2017 has officially begun! Organization
>> applications
>> >> open today, Thursday January 19 and are open through Thursday,
>> February 9th.
>> >> Please see our program site, official timeline and FAQ for more
>> details.
>> >>
>> >> What makes a good organization application? Take a look at our manuals
>> for
>> >> tips and best practices.
>> >>
>> >> We look forward to seeing each of your applications and kicking off
>> >> another great year of GSoC. If you have any questions, don’t hesitate
>> to
>> >> reach out to gsoc-supp...@google.com. We’re here to help!
>> >>
>> >> Google Open Source Programs Office
>> >> --
>> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> >> Alexandre Bergel  http://www.bergel.eu
>> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> >>
>> >>
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Serge Stinckwich
>> UCBN & UMI UMMISCO 209 (IRD/UPMC)
>> Every DSL ends up being Smalltalk
>> http://www.doesnotunderstand.org/
>>
>>
>
>

Re: [Pharo-dev] Google summer of code

[Stephane Ducasse]

Yes please.
I can do a pass also.
I started on some private projects.
I would like to propose to build a make based on a graph library. they have
a nice lib in Python and this way we would avoid to rely on make for pillar
and others

On Tue, Jan 24, 2017 at 10:11 AM, Guillermo Polito <
guillermopol...@gmail.com> wrote:

> Hi,
>
> I would like to help in cleaning, composing and enhancing the ideas page.
> I already see some old projects whose mentors either left the community or
> may not be 100% available for mentoring (like Camille Teruel).
> We should clean that page.
>
> Besides, I'm interested in knowing the official reasons for why we were
> rejected last years :P.
>
> Guille
>
> On Mon, Jan 23, 2017 at 7:02 PM, Serge Stinckwich <
> serge.stinckw...@gmail.com> wrote:
>
>> Thank you Uko to join the team :-)
>>
>> On Mon, Jan 23, 2017 at 5:15 PM, Yuriy Tymchuk 
>> wrote:
>> > I can also update my projects and help with the application if needed
>> (I was
>> > a part of the application team for the last two years I think)
>> >
>> > Uko
>> >
>> > On 22 Jan 2017, at 16:33, Jigyasa Grover 
>> wrote:
>> >
>> > Also, a good application is equally important as the list of clearly
>> defined
>> > projects.
>> >
>> > - J
>> >
>> > On Sun, Jan 22, 2017 at 4:30 PM, Serge Stinckwich
>> >  wrote:
>> >>
>> >> The list of previous projects is here:
>> >> https://github.com/pharo-project/pharo-project-proposals
>> >>
>> >> On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover
>> >>  wrote:
>> >> > Dear Prof Serge
>> >> >
>> >> > Thanks for the introduction.
>> >> >
>> >> > Dear Alexandre
>> >> > I have been a past Google Summer of Code student and also mentor
>> budding
>> >> > developers in Google Code-In.
>> >> > This time, I was hoping to plug-in the loopholes which might have
>> been
>> >> > present in last year's organisation application.
>> >> > Kindly let me know how can we collaborate further on this.
>> >> > Looking forward to your response.
>> >> > Thanks and Regards
>> >> > Jigyasa
>> >> >
>> >> >
>> >> > On Sat, Jan 21, 2017 at 9:06 AM,  wrote:
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Envoyé de mon iPhone
>> >> >> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk  a
>> écrit
>> >> >> :
>> >> >>
>> >> >> What do we do?
>> >> >>
>> >> >>
>> >> >>
>> >> >> We have to apply ! ;-)
>> >> >>
>> >> >> We talk with Jigyasa Grover who is doing an internship in my lab at
>> the
>> >> >> moment and she is willing to help. Jigyasa was a student in a former
>> >> >> Google
>> >> >> Summer of code and is involved in several open-source initiative
>> like
>> >> >> Women
>> >> >> who Code and FOSSASIA. She is a mentor of GoogleCodeIn.
>> >> >>
>> >> >> You can find a small presentation during last FOSSASIA : "
>> >> >>
>> >> >> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover -
>> FOSSASIA
>> >> >> 2016"
>> >> >>
>> >> >> https://m.youtube.com/watch?v=uLIzylxvIz4
>> >> >>
>> >> >> She has done a streaming video this morning also:
>> http://goo.gl/UyclKP
>> >> >> http://youtube.com/watch?v=2iRG_jpOL54
>> >> >>
>> >> >> Anyone to help her setup a small team for Pharo proposal to Google
>> >> >> Summer
>> >> >> of Code this year ?
>> >> >>
>> >> >>
>> >> >> On 20 Jan 2017, at 20:38, Alexandre Bergel > >
>> >> >> wrote:
>> >> >>
>> >> >> Hi everyone-
>> >> >>
>> >> >> Google Summer of Code 2017 has officially begun! Organization
>> >> >> applications
>> >> >> open today, Thursday January 19 and are open through Thursday,
>> February
>> >> >> 9th.
>> >> >> Please see our program site, official timeline and FAQ for more
>> >> >> details.
>> >> >>
>> >> >> What makes a good organization application? Take a look at our
>> manuals
>> >> >> for
>> >> >> tips and best practices.
>> >> >>
>> >> >> We look forward to seeing each of your applications and kicking off
>> >> >> another great year of GSoC. If you have any questions, don’t
>> hesitate
>> >> >> to
>> >> >> reach out to gsoc-supp...@google.com. We’re here to help!
>> >> >>
>> >> >> Google Open Source Programs Office
>> >> >> --
>> >> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> >> >> Alexandre Bergel  http://www.bergel.eu
>> >> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Serge Stinckwich
>> >> UCBN & UMI UMMISCO 209 (IRD/UPMC)
>> >> Every DSL ends up being Smalltalk
>> >> http://www.doesnotunderstand.org/
>> >>
>> >
>> >
>>
>>
>>
>> --
>> Serge Stinckwich
>> UCBN & UMI UMMISCO 209 (IRD/UPMC)
>> Every DSL ends up being Smalltalk
>> http://www.doesnotunderstand.org/
>>
>>
>

Re: [Pharo-dev] Google summer of code

[Stephan Eggermont]

On 24/01/17 10:11, Guillermo Polito wrote:

Besides, I'm interested in knowing the official reasons for why we were
rejected last years :P.


That's the always the same: we get many more applications than we can 
sponsor, and we have to make a choice.


Stephan

Re: [Pharo-dev] Google summer of code

[Jigyasa Grover]

Hi Guillermo

Scrubbing the ideas page is an important task this time.
It shall be great to have your help.

Thanks !

- J



--
View this message in context: 
http://forum.world.st/Google-summer-of-code-tp4930150p4930634.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] Google summer of code

[Guillermo Polito]

Hi,

I would like to help in cleaning, composing and enhancing the ideas page. I
already see some old projects whose mentors either left the community or
may not be 100% available for mentoring (like Camille Teruel).
We should clean that page.

Besides, I'm interested in knowing the official reasons for why we were
rejected last years :P.

Guille

On Mon, Jan 23, 2017 at 7:02 PM, Serge Stinckwich <
serge.stinckw...@gmail.com> wrote:

> Thank you Uko to join the team :-)
>
> On Mon, Jan 23, 2017 at 5:15 PM, Yuriy Tymchuk 
> wrote:
> > I can also update my projects and help with the application if needed (I
> was
> > a part of the application team for the last two years I think)
> >
> > Uko
> >
> > On 22 Jan 2017, at 16:33, Jigyasa Grover 
> wrote:
> >
> > Also, a good application is equally important as the list of clearly
> defined
> > projects.
> >
> > - J
> >
> > On Sun, Jan 22, 2017 at 4:30 PM, Serge Stinckwich
> >  wrote:
> >>
> >> The list of previous projects is here:
> >> https://github.com/pharo-project/pharo-project-proposals
> >>
> >> On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover
> >>  wrote:
> >> > Dear Prof Serge
> >> >
> >> > Thanks for the introduction.
> >> >
> >> > Dear Alexandre
> >> > I have been a past Google Summer of Code student and also mentor
> budding
> >> > developers in Google Code-In.
> >> > This time, I was hoping to plug-in the loopholes which might have been
> >> > present in last year's organisation application.
> >> > Kindly let me know how can we collaborate further on this.
> >> > Looking forward to your response.
> >> > Thanks and Regards
> >> > Jigyasa
> >> >
> >> >
> >> > On Sat, Jan 21, 2017 at 9:06 AM,  wrote:
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> Envoyé de mon iPhone
> >> >> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk  a
> écrit
> >> >> :
> >> >>
> >> >> What do we do?
> >> >>
> >> >>
> >> >>
> >> >> We have to apply ! ;-)
> >> >>
> >> >> We talk with Jigyasa Grover who is doing an internship in my lab at
> the
> >> >> moment and she is willing to help. Jigyasa was a student in a former
> >> >> Google
> >> >> Summer of code and is involved in several open-source initiative like
> >> >> Women
> >> >> who Code and FOSSASIA. She is a mentor of GoogleCodeIn.
> >> >>
> >> >> You can find a small presentation during last FOSSASIA : "
> >> >>
> >> >> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA
> >> >> 2016"
> >> >>
> >> >> https://m.youtube.com/watch?v=uLIzylxvIz4
> >> >>
> >> >> She has done a streaming video this morning also:
> http://goo.gl/UyclKP
> >> >> http://youtube.com/watch?v=2iRG_jpOL54
> >> >>
> >> >> Anyone to help her setup a small team for Pharo proposal to Google
> >> >> Summer
> >> >> of Code this year ?
> >> >>
> >> >>
> >> >> On 20 Jan 2017, at 20:38, Alexandre Bergel 
> >> >> wrote:
> >> >>
> >> >> Hi everyone-
> >> >>
> >> >> Google Summer of Code 2017 has officially begun! Organization
> >> >> applications
> >> >> open today, Thursday January 19 and are open through Thursday,
> February
> >> >> 9th.
> >> >> Please see our program site, official timeline and FAQ for more
> >> >> details.
> >> >>
> >> >> What makes a good organization application? Take a look at our
> manuals
> >> >> for
> >> >> tips and best practices.
> >> >>
> >> >> We look forward to seeing each of your applications and kicking off
> >> >> another great year of GSoC. If you have any questions, don’t hesitate
> >> >> to
> >> >> reach out to gsoc-supp...@google.com. We’re here to help!
> >> >>
> >> >> Google Open Source Programs Office
> >> >> --
> >> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> >> >> Alexandre Bergel  http://www.bergel.eu
> >> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >
> >>
> >>
> >>
> >> --
> >> Serge Stinckwich
> >> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> >> Every DSL ends up being Smalltalk
> >> http://www.doesnotunderstand.org/
> >>
> >
> >
>
>
>
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://www.doesnotunderstand.org/
>
>

Re: [Pharo-dev] Google summer of code

[Serge Stinckwich]

Thank you Uko to join the team :-)

On Mon, Jan 23, 2017 at 5:15 PM, Yuriy Tymchuk  wrote:
> I can also update my projects and help with the application if needed (I was
> a part of the application team for the last two years I think)
>
> Uko
>
> On 22 Jan 2017, at 16:33, Jigyasa Grover  wrote:
>
> Also, a good application is equally important as the list of clearly defined
> projects.
>
> - J
>
> On Sun, Jan 22, 2017 at 4:30 PM, Serge Stinckwich
>  wrote:
>>
>> The list of previous projects is here:
>> https://github.com/pharo-project/pharo-project-proposals
>>
>> On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover
>>  wrote:
>> > Dear Prof Serge
>> >
>> > Thanks for the introduction.
>> >
>> > Dear Alexandre
>> > I have been a past Google Summer of Code student and also mentor budding
>> > developers in Google Code-In.
>> > This time, I was hoping to plug-in the loopholes which might have been
>> > present in last year's organisation application.
>> > Kindly let me know how can we collaborate further on this.
>> > Looking forward to your response.
>> > Thanks and Regards
>> > Jigyasa
>> >
>> >
>> > On Sat, Jan 21, 2017 at 9:06 AM,  wrote:
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> Envoyé de mon iPhone
>> >> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk  a écrit
>> >> :
>> >>
>> >> What do we do?
>> >>
>> >>
>> >>
>> >> We have to apply ! ;-)
>> >>
>> >> We talk with Jigyasa Grover who is doing an internship in my lab at the
>> >> moment and she is willing to help. Jigyasa was a student in a former
>> >> Google
>> >> Summer of code and is involved in several open-source initiative like
>> >> Women
>> >> who Code and FOSSASIA. She is a mentor of GoogleCodeIn.
>> >>
>> >> You can find a small presentation during last FOSSASIA : "
>> >>
>> >> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA
>> >> 2016"
>> >>
>> >> https://m.youtube.com/watch?v=uLIzylxvIz4
>> >>
>> >> She has done a streaming video this morning also: http://goo.gl/UyclKP
>> >> http://youtube.com/watch?v=2iRG_jpOL54
>> >>
>> >> Anyone to help her setup a small team for Pharo proposal to Google
>> >> Summer
>> >> of Code this year ?
>> >>
>> >>
>> >> On 20 Jan 2017, at 20:38, Alexandre Bergel 
>> >> wrote:
>> >>
>> >> Hi everyone-
>> >>
>> >> Google Summer of Code 2017 has officially begun! Organization
>> >> applications
>> >> open today, Thursday January 19 and are open through Thursday, February
>> >> 9th.
>> >> Please see our program site, official timeline and FAQ for more
>> >> details.
>> >>
>> >> What makes a good organization application? Take a look at our manuals
>> >> for
>> >> tips and best practices.
>> >>
>> >> We look forward to seeing each of your applications and kicking off
>> >> another great year of GSoC. If you have any questions, don’t hesitate
>> >> to
>> >> reach out to gsoc-supp...@google.com. We’re here to help!
>> >>
>> >> Google Open Source Programs Office
>> >> --
>> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> >> Alexandre Bergel  http://www.bergel.eu
>> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> >>
>> >>
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Serge Stinckwich
>> UCBN & UMI UMMISCO 209 (IRD/UPMC)
>> Every DSL ends up being Smalltalk
>> http://www.doesnotunderstand.org/
>>
>
>



-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Google summer of code

[Yuriy Tymchuk]

I can also update my projects and help with the application if needed (I was a 
part of the application team for the last two years I think)

Uko

> On 22 Jan 2017, at 16:33, Jigyasa Grover  wrote:
> 
> Also, a good application is equally important as the list of clearly defined 
> projects.
> 
> - J
> 
> On Sun, Jan 22, 2017 at 4:30 PM, Serge Stinckwich  > wrote:
> The list of previous projects is here:
> https://github.com/pharo-project/pharo-project-proposals 
> 
> 
> On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover
> > wrote:
> > Dear Prof Serge
> >
> > Thanks for the introduction.
> >
> > Dear Alexandre
> > I have been a past Google Summer of Code student and also mentor budding
> > developers in Google Code-In.
> > This time, I was hoping to plug-in the loopholes which might have been
> > present in last year's organisation application.
> > Kindly let me know how can we collaborate further on this.
> > Looking forward to your response.
> > Thanks and Regards
> > Jigyasa
> >
> >
> > On Sat, Jan 21, 2017 at 9:06 AM,  > > wrote:
> >>
> >>
> >>
> >>
> >>
> >> Envoyé de mon iPhone
> >> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk  >> > a écrit :
> >>
> >> What do we do?
> >>
> >>
> >>
> >> We have to apply ! ;-)
> >>
> >> We talk with Jigyasa Grover who is doing an internship in my lab at the
> >> moment and she is willing to help. Jigyasa was a student in a former Google
> >> Summer of code and is involved in several open-source initiative like Women
> >> who Code and FOSSASIA. She is a mentor of GoogleCodeIn.
> >>
> >> You can find a small presentation during last FOSSASIA : "
> >>
> >> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA
> >> 2016"
> >>
> >> https://m.youtube.com/watch?v=uLIzylxvIz4 
> >> 
> >>
> >> She has done a streaming video this morning also: http://goo.gl/UyclKP 
> >> 
> >> http://youtube.com/watch?v=2iRG_jpOL54 
> >> 
> >>
> >> Anyone to help her setup a small team for Pharo proposal to Google Summer
> >> of Code this year ?
> >>
> >>
> >> On 20 Jan 2017, at 20:38, Alexandre Bergel  >> >
> >> wrote:
> >>
> >> Hi everyone-
> >>
> >> Google Summer of Code 2017 has officially begun! Organization applications
> >> open today, Thursday January 19 and are open through Thursday, February 
> >> 9th.
> >> Please see our program site, official timeline and FAQ for more details.
> >>
> >> What makes a good organization application? Take a look at our manuals for
> >> tips and best practices.
> >>
> >> We look forward to seeing each of your applications and kicking off
> >> another great year of GSoC. If you have any questions, don’t hesitate to
> >> reach out to gsoc-supp...@google.com . 
> >> We’re here to help!
> >>
> >> Google Open Source Programs Office
> >> --
> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> >> Alexandre Bergel  http://www.bergel.eu 
> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >>
> >>
> >>
> >>
> >
> 
> 
> 
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://www.doesnotunderstand.org/ 
> 
> 

Re: [Pharo-dev] Google summer of code

[Jigyasa Grover]

Also, a good application is equally important as the list of clearly
defined projects.

- J

On Sun, Jan 22, 2017 at 4:30 PM, Serge Stinckwich <
serge.stinckw...@gmail.com> wrote:

> The list of previous projects is here:
> https://github.com/pharo-project/pharo-project-proposals
>
> On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover
>  wrote:
> > Dear Prof Serge
> >
> > Thanks for the introduction.
> >
> > Dear Alexandre
> > I have been a past Google Summer of Code student and also mentor budding
> > developers in Google Code-In.
> > This time, I was hoping to plug-in the loopholes which might have been
> > present in last year's organisation application.
> > Kindly let me know how can we collaborate further on this.
> > Looking forward to your response.
> > Thanks and Regards
> > Jigyasa
> >
> >
> > On Sat, Jan 21, 2017 at 9:06 AM,  wrote:
> >>
> >>
> >>
> >>
> >>
> >> Envoyé de mon iPhone
> >> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk  a écrit
> :
> >>
> >> What do we do?
> >>
> >>
> >>
> >> We have to apply ! ;-)
> >>
> >> We talk with Jigyasa Grover who is doing an internship in my lab at the
> >> moment and she is willing to help. Jigyasa was a student in a former
> Google
> >> Summer of code and is involved in several open-source initiative like
> Women
> >> who Code and FOSSASIA. She is a mentor of GoogleCodeIn.
> >>
> >> You can find a small presentation during last FOSSASIA : "
> >>
> >> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA
> >> 2016"
> >>
> >> https://m.youtube.com/watch?v=uLIzylxvIz4
> >>
> >> She has done a streaming video this morning also: http://goo.gl/UyclKP
> >> http://youtube.com/watch?v=2iRG_jpOL54
> >>
> >> Anyone to help her setup a small team for Pharo proposal to Google
> Summer
> >> of Code this year ?
> >>
> >>
> >> On 20 Jan 2017, at 20:38, Alexandre Bergel 
> >> wrote:
> >>
> >> Hi everyone-
> >>
> >> Google Summer of Code 2017 has officially begun! Organization
> applications
> >> open today, Thursday January 19 and are open through Thursday, February
> 9th.
> >> Please see our program site, official timeline and FAQ for more details.
> >>
> >> What makes a good organization application? Take a look at our manuals
> for
> >> tips and best practices.
> >>
> >> We look forward to seeing each of your applications and kicking off
> >> another great year of GSoC. If you have any questions, don’t hesitate to
> >> reach out to gsoc-supp...@google.com. We’re here to help!
> >>
> >> Google Open Source Programs Office
> >> --
> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> >> Alexandre Bergel  http://www.bergel.eu
> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >>
> >>
> >>
> >>
> >
>
>
>
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://www.doesnotunderstand.org/
>
>

Re: [Pharo-dev] Google summer of code

[Serge Stinckwich]

The list of previous projects is here:
https://github.com/pharo-project/pharo-project-proposals

On Sat, Jan 21, 2017 at 10:06 AM, Jigyasa Grover
 wrote:
> Dear Prof Serge
>
> Thanks for the introduction.
>
> Dear Alexandre
> I have been a past Google Summer of Code student and also mentor budding
> developers in Google Code-In.
> This time, I was hoping to plug-in the loopholes which might have been
> present in last year's organisation application.
> Kindly let me know how can we collaborate further on this.
> Looking forward to your response.
> Thanks and Regards
> Jigyasa
>
>
> On Sat, Jan 21, 2017 at 9:06 AM,  wrote:
>>
>>
>>
>>
>>
>> Envoyé de mon iPhone
>> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk  a écrit :
>>
>> What do we do?
>>
>>
>>
>> We have to apply ! ;-)
>>
>> We talk with Jigyasa Grover who is doing an internship in my lab at the
>> moment and she is willing to help. Jigyasa was a student in a former Google
>> Summer of code and is involved in several open-source initiative like Women
>> who Code and FOSSASIA. She is a mentor of GoogleCodeIn.
>>
>> You can find a small presentation during last FOSSASIA : "
>>
>> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA
>> 2016"
>>
>> https://m.youtube.com/watch?v=uLIzylxvIz4
>>
>> She has done a streaming video this morning also: http://goo.gl/UyclKP
>> http://youtube.com/watch?v=2iRG_jpOL54
>>
>> Anyone to help her setup a small team for Pharo proposal to Google Summer
>> of Code this year ?
>>
>>
>> On 20 Jan 2017, at 20:38, Alexandre Bergel 
>> wrote:
>>
>> Hi everyone-
>>
>> Google Summer of Code 2017 has officially begun! Organization applications
>> open today, Thursday January 19 and are open through Thursday, February 9th.
>> Please see our program site, official timeline and FAQ for more details.
>>
>> What makes a good organization application? Take a look at our manuals for
>> tips and best practices.
>>
>> We look forward to seeing each of your applications and kicking off
>> another great year of GSoC. If you have any questions, don’t hesitate to
>> reach out to gsoc-supp...@google.com. We’re here to help!
>>
>> Google Open Source Programs Office
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>



-- 
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-dev] Google summer of code

[stepharong]

We should apply.
I have a new list of topics.
Now we should not have topics with clearly identified mentors.

Stef









Envoyé de mon iPhone
Le 20 janv. 2017 à 22:21, Yuriy Tymchuk  a écrit :


What do we do?



We have to apply ! ;-)

We talk with Jigyasa Grover who is doing an internship in my lab at the  
moment and she is willing to help. Jigyasa was a student in a former  
Google Summer of code and is involved in several >open-source initiative  
like Women who Code and FOSSASIA. She is a mentor of GoogleCodeIn.


You can find a small presentation during last FOSSASIA : "
My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA  
2016"

https://m.youtube.com/watch?v=uLIzylxvIz4

She has done a streaming video this morning also: http://goo.gl/UyclKP
http://youtube.com/watch?v=2iRG_jpOL54

Anyone to help her setup a small team for Pharo proposal to Google  
Summer of Code this year ?




On 20 Jan 2017, at 20:38, Alexandre Bergel   
wrote:


Hi everyone-
Google Summer of Code 2017 has officially begun! Organization  
applications open today, Thursday January 19 and are open through  
Thursday, >>>February 9th. Please see our program site, official  
timeline and FAQ for more details.


What makes a good organization application? Take a look at our manuals  
for tips and best practices.
We look forward to seeing each of your applications and kicking off  
another great year of GSoC. If you have any questions, don’t hesitate  
to reach out >>>to gsoc-supp...@google.com. We’re here to help!



Google Open Source Programs Office

--_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.









--
Using Opera's mail client: http://www.opera.com/mail/

Re: [Pharo-dev] Google summer of code

[Jigyasa Grover]

Dear Prof Serge

Thanks for the introduction.

Dear Alexandre
I have been a past Google Summer of Code student and also mentor budding
developers in Google Code-In.
This time, I was hoping to plug-in the loopholes which might have been
present in last year's organisation application.
Kindly let me know how can we collaborate further on this.
Looking forward to your response.
Thanks and Regards
Jigyasa


On Sat, Jan 21, 2017 at 9:06 AM,  wrote:

>
>
>
>
> Envoyé de mon iPhone
> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk  a écrit :
>
> What do we do?
>
>
>
> We have to apply ! ;-)
>
> We talk with Jigyasa Grover who is doing an internship in my lab at the
> moment and she is willing to help. Jigyasa was a student in a former Google
> Summer of code and is involved in several open-source initiative like Women
> who Code and FOSSASIA. She is a mentor of GoogleCodeIn.
>
> You can find a small presentation during last FOSSASIA : "
> My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA 2016"
> https://m.youtube.com/watch?v=uLIzylxvIz4
>
> She has done a streaming video this morning also: http://goo.gl/UyclKP
> http://youtube.com/watch?v=2iRG_jpOL54
>
> Anyone to help her setup a small team for Pharo proposal to Google Summer
> of Code this year ?
>
>
> On 20 Jan 2017, at 20:38, Alexandre Bergel 
> wrote:
>
> Hi everyone-
>
> Google Summer of Code 2017 has officially begun! Organization applications
> open today, Thursday January 19 and are open through Thursday, February
> 9th. Please see our program site,  official timeline
>  and FAQ
>  for more details.
>
> What makes a good organization application? Take a look at our manuals
>  for
> tips and best practices.
>
> We look forward to seeing each of your applications and kicking off
> another great year of GSoC. If you have any questions, don’t hesitate to
> reach out to gsoc-supp...@google.com. We’re here to help!
>
> Google Open Source Programs Office
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>

Re: [Pharo-dev] Google summer of code

[serge . stinckwich]

Envoyé de mon iPhone
> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk  a écrit :
> 
> What do we do?


We have to apply ! ;-)

We talk with Jigyasa Grover who is doing an internship in my lab at the moment 
and she is willing to help. Jigyasa was a student in a former Google Summer of 
code and is involved in several open-source initiative like Women who Code and 
FOSSASIA. She is a mentor of GoogleCodeIn.

You can find a small presentation during last FOSSASIA : "
My journey in FOSS with Pharo & FOSSASIA by Jigyasa Grover - FOSSASIA 2016"
https://m.youtube.com/watch?v=uLIzylxvIz4

She has done a streaming video this morning also: http://goo.gl/UyclKP
http://youtube.com/watch?v=2iRG_jpOL54

Anyone to help her setup a small team for Pharo proposal to Google Summer of 
Code this year ?

> 
>> On 20 Jan 2017, at 20:38, Alexandre Bergel  wrote:
>> 
>> Hi everyone- 
>> 
>> Google Summer of Code 2017 has officially begun! Organization applications 
>> open today, Thursday January 19 and are open through Thursday, February 9th. 
>> Please see our program site, official timeline and FAQ for more details.
>> 
>> What makes a good organization application? Take a look at our manuals for 
>> tips and best practices. 
>> 
>> We look forward to seeing each of your applications and kicking off another 
>> great year of GSoC. If you have any questions, don’t hesitate to reach out 
>> to gsoc-supp...@google.com. We’re here to help!
>> 
>> Google Open Source Programs Office
>> -- 
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> 
>> 
>> 
> 

Re: [Pharo-dev] Google summer of code

[Yuriy Tymchuk]

What do we do?

> On 20 Jan 2017, at 20:38, Alexandre Bergel  wrote:
> 
> Hi everyone- 
> 
> Google Summer of Code 2017 has officially begun! Organization applications 
> open today, Thursday January 19 and are open through Thursday, February 9th. 
> Please see our program site,  official timeline 
>  and FAQ 
>  for more details.
> 
> What makes a good organization application? Take a look at our manuals 
>  for tips 
> and best practices. 
> 
> We look forward to seeing each of your applications and kicking off another 
> great year of GSoC. If you have any questions, don’t hesitate to reach out to 
> gsoc-supp...@google.com . We’re here to help!
> 
> Google Open Source Programs Office
> -- 
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu 
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> 
> 
> 

[Pharo-dev] Google summer of code

[Alexandre Bergel]

Hi everyone- 

Google Summer of Code 2017 has officially begun! Organization applications open 
today, Thursday January 19 and are open through Thursday, February 9th. Please 
see our program site,  official timeline 
 and FAQ 
 for more details.

What makes a good organization application? Take a look at our manuals 
 for tips and 
best practices. 

We look forward to seeing each of your applications and kicking off another 
great year of GSoC. If you have any questions, don’t hesitate to reach out to 
gsoc-supp...@google.com . We’re here to help!

Google Open Source Programs Office
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

[Pharo-dev] Google Summer of Code is here, your ideas please!

[Janko Mivšek]

Dear Smalltalkers,

Tenth GSoC is here and application deadline is earlier this year,
already next Friday!

Time therefore for your cool project ideas on this year Smalltalk GSoC
Hurry up!

For now just express any idea you have here on the mailing list. Later
we will together develop it to be in complete format together with two
mentors needed. To see how fully developed ideas look like please look
at 2012 ones at:http://gsoc2013.esug.org/ideas.

Ideally (but not necessary right now) you should prepare an idea
following this template:

---

Title:

Level: (beginner, intermediate, advanced)

Possible mentor: (can be assigned later)

Possible second mentor: (can be assigned later)

Description

Technical Details

Benefits to the Student

Benefits to the Community

-

Note also that students yourselves can propose a GSoC project. So if you
like to be a student on this year GSoC and have a nice idea, don't be
shy and propose it here! The community will listen you and guide to the
really nicely proposed project.

For the community, start looking around for students. Think about how to
approach the universities near by you, do you know who to contact
there, etc.

Our special website is in preparation and will be online in few days.
Official Google GSoC site is here:

   http://www.google-melange.com/gsoc/homepage/google/gsoc2014.

Specially read carefully the FAQ:
http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2014/help_page

Mentors of all past GSoCs please rejoin the mentors mailing list where
we discuss all details about this year GSoC:

   http://groups.google.com/group/smalltalk-gsoc-mentors

While students interested on GSoC please join a special Smalltalk GSoC
mailing list for you:

   http://groups.google.com/group/smalltalk-gsoc-students

Best regards
Janko

-- 
Janko Mivšek
Smalltalk GSoC Admin Team