hi,

On Mon, Apr 27, 2015 at 6:47 PM, Valentin V. Bartenev <vbart@nginx.com>
wrote:

> On Saturday 25 April 2015 15:08:24 Yuva wrote:
> > hi,
> > I would like to contribute by coding. For a start, this is what im
> > thinking:
> > - get familiar with nginx spdy source code (since spdy is close to
> http/2)
>
> Well, this may take all your time and effort, especially if you're not
> familiar
> with nginx internals.
>
>
> > - understand source code written to support http/2, if any.
> > - start with implementing small features, and fixing bugs.
>
> There's a couple of open tickets about SPDY: http://trac.nginx.org
> You can start by trying to fix them.
>

actually there are no outstanding tickets abouty SPDY, or atleast i
couldn't find them.
thanks for letting me know that understanding nginx internals is time
consuming.


> wbr, Valentin V. Bartenev
>
> _______________________________________________
> nginx-devel mailing list
> nginx-devel@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
>



--
Yuva (@iffyuva)
Co-founder at Codemancers Tech Pvt Ltd
http://codemancers.com
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel