Patch Requirement

Patch requirement

In addition to the written proposal, we require every GSoC applicant to write a patch and get it pushed into our current master. To do this:

Clone and set up EvalAI. You will find detailed setup instructions in the ReadMe file of the repository.

Try to work on one of the open issues or send us a pull request fixing it. If you need inspiration, feel free to ask people on the Gitter channel. You could also play with the platform a bit and find something that needs fixing or that could be implemented, and do it.

Although documentation related patches are welcome, only patches that are code-related will be counted towards the application.

Publish your patch for peer review by creating a pull request on GitHub. You must submit a patch that is successfully reviewed and pushed in to be accepted. We do not consider applications without patches. This shows us that you know Python and that you are able to interact with the community. Furthermore, your patch must go through a GitHub pull request (as opposed to a patch file on an issue, for example), as this is not only the easiest way for us to review your code but is also what we expect from a student working on a GSoC project.

In your application, please provide a brief summary of your contributions to CloudCV so far, including unmerged work. At least one link to a merged pull request proving that you satisfied the patch requirement.

Note that because we may be slow to review the pull requests, you do not have to have your request merged by the application deadline (though you should try to do it if you can!). But you do need to at least have one submitted by then. We will give priority to reviewing requests that are needed to satisfy patch requirements. It is up to you to respond to our feedback in a timely enough manner so that your patch gets merged before the acceptance deadline.