falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pallavi Rao <pallavi....@inmobi.com>
Subject Re: FW: Google Summer of Code 2016 is coming
Date Thu, 18 Feb 2016 07:14:45 GMT
Thanks Srikanth! Have filed FALCON-1833 and FALCON-1834 for GSoC.

Peeyush, Venkat,
I feel FALCON-1763 is also a candidate. If you agree and the timelines of
GSoC and your plan match, please mark the JIRA accordingly.

Thanks,
Pallavi

On Mon, Feb 15, 2016 at 10:20 AM, Srikanth Sundarrajan <sriksun@hotmail.com>
wrote:

> Would we be interested in participating ? This would be a good way to
> welcome additional contributors to the project.
>
> Regards
> Srikanth Sundarrajan
>
> > From: uli@apache.org
> > Subject: Google Summer of Code 2016 is coming
> > To: mentors@community.apache.org
> > Date: Wed, 10 Feb 2016 21:16:52 +0100
> >
> > 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 by no later than 2016-02-19:
> >
> > 1. understand what it means to be a mentor [2].
> >
> > 2. record your project ideas.
> >
> > Just create issues in JIRA, label them with gsoc2016, 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 dev@community.apache.org if you need assistance.
> >
> > [4] contains some additional information (will be updated for 2016
> shortly).
> >
> > 3. subscribe to mentors@community.apache.org; restricted to potential
> mentors, meant to be used as a
> > private list - general discussions on the public
> dev@community.apache.org list as much as possible
> > please). Use a recognized address when subscribing (@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
> >
> > P.S.: Except for the private parts (label spreadsheet mostly), this
> email is free to be shared
> > publicly if you want to.
> >
> > [1] https://summerofcode.withgoogle.com/
> > [2] http://community.apache.org/guide-to-being-a-mentor.html
> > [3] http://s.apache.org/gsoc2016ideas
> > [4] http://community.apache.org/gsoc.html
> > [5] http://s.apache.org/gsoclabels
> >
>

-- 
_____________________________________________________________
The information contained in this communication is intended solely for the 
use of the individual or entity to whom it is addressed and others 
authorized to receive it. It may contain confidential or legally privileged 
information. If you are not the intended recipient you are hereby notified 
that any disclosure, copying, distribution or taking any action in reliance 
on the contents of this information is strictly prohibited and may be 
unlawful. If you have received this communication in error, please notify 
us immediately by responding to this email and then delete it from your 
system. The firm is neither liable for the proper and complete transmission 
of the information contained in this communication nor for any delay in its 
receipt.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message