Regarding GSOC-16.

[Martijn Pieters]

Please send emails like these directly to the mercurial development list; I don't decide (alone) who is awarded a project. This depends on what proposals we receive and how many slots we have available.

> On 19 Feb 2016, at 23:36, Pulkit Goyal <7895pulkit at gmail.com> wrote:
> 
> Hello Sir,
> 
> I am a sophomore in Computer Science and I want to work with Mercurial as a part of GSOC-16. I want to work on the project which involves moving towards Python 3. I saw you listed as a potential mentor and than your patches in the mailing list.
> 
> Though I have started working on it, the first to do was to fixings the imports to use absolute_import across the code base and also fixing some cyclic imports. I am on it.
> 
> 
> So I would really like to start the work now if there are no more applicants at this stage. This project involves a lot of work and if I start early I can get acquainted easily.
> 
> Hope to hear from your sir.
> 
> Regards
> Pulkit Goyal

You are *always* welcome to work on Mercurial, of course! Do read the https://www.mercurial-scm.org/wiki/DeveloperInfo <https://www.mercurial-scm.org/wiki/DeveloperInfo> wiki pages to make sure your patches meet our standards. Then start sending patches early, so you get feedback early. I see that you already sent your first email. The wiki outlines how to send your patches.

Martijn Pieters
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20160223/a8a402ea/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20160223/a8a402ea/attachment.sig>