Hi all,
i am new to Apache-airflow community. I am very much interested in
contributing to Apache-flow during GSOC . What should be my road map?
Please help me out.
My background : I am a 2nd year under graduate student. My Github handle is
yajna-pandith electronics and communications student with minor degree in
Computer Science with no prior open source experiance. .

Regards,
Yajna pandith.

On Wed, Jan 15, 2020 at 2:04 AM Jarek Potiuk <jarek.pot...@polidea.com>
wrote:

> Absolutely Pablo!
>
> I am very interested. I have great experience from GSoD and GSoC will be
> probably even more fun! I will find some issues that need some love and
> will apply the labels. Anyone else want to join me :) ?
>
> J.
>
> On Tue, Jan 14, 2020 at 7:43 PM Pablo Estrada <pabl...@google.com.invalid>
> wrote:
>
> > Hello everyone,
> >
> > As with every year, the Google Summer of Code has been announced[1], so
> if
> > there are any committers interested, they can start thinking / preparing
> > projects for students to develop over the summer. It's early in the
> process
> > for now, but it's good to prepare early : )
> >
> > I have done the GSOC as a student a few years back, and as a mentor for
> > Apache Beam last year. I am a big fan, so I figured I'd share with the
> > Airflow community.
> >
> > Here are the ASF mentor guidelines[2]. For now, the thing to do is to
> file
> > JIRA issues for your projects, and apply the labels "mentor", "gsoc",
> > "gsoc2020".
> >
> > When the time comes, the next steps are to join the
> > ment...@community.apache.org list, and request the PMC for approval of a
> > project.
> >
> > I'll try to keep the Airflow dev@ list updated with other steps of the
> > process.
> > Thanks!
> > -P.
> >
> > [1] https://summerofcode.withgoogle.com/
> > [2]
> > https://community.apache.org/gsoc.html#prospective-asf-mentors-read-this
> >
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> [image: Polidea] <https://www.polidea.com/>
>

Reply via email to