Re: [Bug-wget] GSoC 2015 participation

[Darshit Shah]

Hi Ander,

Responding inline to your email.

On 03/02, Ander Juaristi Alamos wrote:
> Hi all,
>
> I'm writing this message regarding your participation in GSoC 2015. I know you 
> guys are busy, so I'll try to keep it short.
>
> I'm a university student on my last year in a CS degree. Ideas 2 and 3 fit me 
> like a glove, so I didn't hesitate to send you my offer for participation. I 
> hold an EC-Council CEH certification, which means I have security knowledge, 
> and yes, that includes HSTS. What's more, I currently work full-time for a 
> research center developing and maintaining several web crawlers in the cloud 
> (my work is part of my end-of-degree project, so no class attendance anymore). 
> I'm even the lead developer of one of those. Therefore, I have extensive 
> knowledge of the HTTP protocol, including conditional requests such as 
> If-Modified-Since, which we use a lot in order to keep the footprint as low as 
> possible on the websites we crawl. I'm proficient in the C language, specially 
> in network programming under UNIX-based environments, and I've spent the last 
> years studying the TCP/IP stack. I feel comfortable reading RFCs. Finally, I 
> have a exposure to open source software development, including coding 
> conventions, patching best practices/conventions, how to post on mailing lists, 
> etc.
>
> Unfortunately, although I can understand Python code, I don't know Python yet. 
> That's why I'm only interested in ideas 2 and 3, and not 1. Of course, I'm 
> willing to learn if necessary.

That's alright. Learning is what GSoC is all about.
> Given my great interest in joining this project, I'm approaching you so that we 
> can start to get to know each other, and discuss further steps to take prior to 
> submitting a formal proposal. I'm not familiarized with the Wget code, but I'll 
> dive in it soon. Apart from that, is there anything else you expect me to do? 
> Anything you'd like to ask? I'm all ears.
It's great that you've decided to start early. At this stage, I'd suggest that 
you start taking a closer look at the ideas that we have listed and try to 
understand them. When you write your proposal, you will be required to jot down 
specifics about how you will implement the project and the timeline for the 
same. To be able to do this, you will also need to be familiar with Wget's 
source. Once of the best ways to do so is to take a dive and start hacking on 
it. You can take a look at the bug tracker and see if some open issue interests 
you. Even basic triaging can be very useful in understanding the code base.

We do expect you to have contributed atleast one patch to Wget, since it allows 
us to see how well you have understood the code base and saves a lot of time 
later.

> By the way, I can provide references if needed, just ask for them.

The only references we need are the ones that come from your work for Wget and 
your interaction with the rest of the community. :)
>  
> Regards,
>
> - AJ

--
Thanking You,
Darshit Shah

pgpG85QlVW8Eh.pgp
Description: PGP signature