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 <[email protected]>:

> 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 <[email protected]>
> 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 <[email protected]>
>> 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 <
>> [email protected]> 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
>>> <[email protected]> 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, <[email protected]> wrote:
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> Envoyé de mon iPhone
>>> >> Le 20 janv. 2017 à 22:21, Yuriy Tymchuk <[email protected]> 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 <[email protected]>
>>> >> 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 [email protected]. 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/
>>>
>>>
>>
>>
>

Reply via email to