Does this mean that we can still propose subjects? I thought the
deadline was over, when is it the deadline?

On Mon, Feb 26, 2018 at 5:17 PM, Kenneth Knowles <k...@google.com> wrote:
> Hi Kai,
>
> Thanks for writing this! I would love to be a mentor for GSoC if it falls
> within my expertise.
>
> As a reminder to the whole community & PMC - it is *not* too late to propose
> new ideas. The initial phase of collecting ideas has resulting in the ASF
> being accepted as a mentoring organization. The next step is the student
> application and review.
>
> Personally, I would love to see work on SQL - GSoC scope could be trying to
> scale up some examples on different runners to do some optimization, or
> implementing new join algorithms and/or using Calcite's rule system to
> select the right one. I will see about writing these up more clearly.
>
> Kenn
>
> On Mon, Feb 26, 2018 at 3:05 AM, Kai Jiang <jiang...@gmail.com> wrote:
>>
>> Hi Beam Community,
>>
>> I am Kai Jiang, a master student majoring in CS from Portland State
>> University, highly interested in big data and distributed System. I have
>> contributed code to Apache Spark as a selected GSoC project in 2016.
>> Besides, I've been contributing to Beam codebase. Some my Pull Requests are
>> here.
>> https://github.com/apache/beam/pulls?q=is%3Apr+author%3Avectorijk+is%3Aclosed
>>
>> This year, I really want to extend my future contribution with Beam into a
>> GSoC project and look forward to contributing something meaningful and
>> impactful. So, I was wondering if there are some specific ideas, issues or
>> suggestions regarding SQL, Python/Go SDK, Kafka Stream Runner or others
>> could be gathered into a project. If community has other ideas, I am very
>> happy and willing to work on some issues before GSoC and get started with
>> something new during GSoC. After talking about ideas, I'd love to open
>> ticket on JIRA and write the proposal to apply for GSoC. I would appreciate
>> if any committer is interested in mentoring.
>>
>> Looking forward to hearing from you!
>>
>> Best,
>> Kai
>> github.com/vectorijk
>>
>>
>>
>> On Mon, Jan 22, 2018 at 12:40 AM, Jean-Baptiste Onofré <j...@nanthrax.net>
>> wrote:
>>>
>>> Hi Davor,
>>>
>>> you were faster than me: I was just preparing an e-mail about GSoC ;)
>>>
>>> +1
>>>
>>> Regards
>>> JB
>>>
>>> On 01/22/2018 08:37 AM, Davor Bonaci wrote:
>>> > This is a great way to grow the community. If you are interested in
>>> > mentoring
>>> > students contributing to Beam, please apply!
>>> >
>>> > ---------- Forwarded message ----------
>>> > From: *Ulrich Stärk* <u...@apache.org <mailto:u...@apache.org>>
>>> > Date: Sun, Jan 21, 2018 at 1:22 PM
>>> > Subject: Google Summer of Code 2018 is coming
>>> > To: ment...@community.apache.org <mailto:ment...@community.apache.org>
>>> >
>>> >
>>> > Hello PMCs (incubator Mentors, please forward this email to your
>>> > podlings),
>>> >
>>> > Google Summer of Code [1] is a program sponsored by Google allowing
>>> > students to
>>> > spend their summer
>>> > working on open source software. Students will receive stipends for
>>> > developing
>>> > open source software
>>> > full-time for three months. Projects will provide mentoring and project
>>> > ideas,
>>> > and in return have
>>> > the chance to get new code developed and - most importantly - to
>>> > identify and
>>> > bring in new committers.
>>> >
>>> > The ASF will apply as a participating organization meaning individual
>>> > projects
>>> > don't have to apply
>>> > separately.
>>> >
>>> > If you want to participate with your project we ask you to do the
>>> > following
>>> > things as soon as
>>> > possible but please no later than 2017-01-30:
>>> >
>>> > 1. understand what it means to be a mentor [2].
>>> >
>>> > 2. record your project ideas.
>>> >
>>> > Just create issues in JIRA, label them with gsoc2018, and they will
>>> > show up at
>>> > [3]. Please be as
>>> > specific as possible when describing your idea. Include the programming
>>> > language, the tools and
>>> > skills required, but try not to scare potential students away. They are
>>> > supposed
>>> > to learn what's
>>> > required before the program starts.
>>> >
>>> > Use labels, e.g. for the programming language (java, c, c++, erlang,
>>> > python,
>>> > brainfuck, ...) or
>>> > technology area (cloud, xml, web, foo, bar, ...) and record them at
>>> > [5].
>>> >
>>> > Please use the COMDEV JIRA project for recording your ideas if your
>>> > project
>>> > doesn't use JIRA (e.g.
>>> > httpd, ooo). Contact d...@community.apache.org
>>> > <mailto:d...@community.apache.org>
>>> > if you need assistance.
>>> >
>>> > [4] contains some additional information (will be updated for 2017
>>> > shortly).
>>> >
>>> > 3. subscribe to ment...@community.apache.org
>>> > <mailto:ment...@community.apache.org>; restricted to potential mentors,
>>> > meant to
>>> > be used as a
>>> > private list - general discussions on the public
>>> > d...@community.apache.org
>>> > <mailto:d...@community.apache.org> list as much as possible
>>> > please). Use a recognized address when subscribing (@apache.org
>>> > <http://apache.org> or one of your alias addresses on
>>> > record).
>>> >
>>> > Note that the ASF isn't accepted as a participating organization yet,
>>> > nevertheless you *have to*
>>> > start recording your ideas now or we will not get accepted.
>>> >
>>> > Over the years we were able to complete hundreds of projects
>>> > successfully. Some
>>> > of our prior
>>> > students are active contributors now! Let's make this year a success
>>> > again!
>>> >
>>> > Cheers,
>>> >
>>> > Uli
>>> >
>>> > [1] https://summerofcode.withgoogle.com/
>>> > <https://summerofcode.withgoogle.com/>
>>> > [2] http://community.apache.org/guide-to-being-a-mentor.html
>>> > <http://community.apache.org/guide-to-being-a-mentor.html>
>>> > [3] http://s.apache.org/gsoc2018ideas
>>> > <http://s.apache.org/gsoc2018ideas>
>>> > [4] http://community.apache.org/gsoc.html
>>> > <http://community.apache.org/gsoc.html>
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>
>>
>

Reply via email to