Rails Girls Summer of Code (RGSoc)

This will contain a detailed explanation of each of the tasks assigned for RGSoC.

Please do not send code over mail. It is not a good practice. Fork the repo. Create a branch and start making changes there.
Always discuss the changes before making it. This will avoid rework.
Contributing to the repo does not mean that you are accepted for this project for RGSoC. The decision is made by the community.
To be fair to other students, have your queries or doubts on the github issue link itself.

Read the task carefully and if you think you know what is to be done, go ahead. If not, drop a comment asking for details. You will get a reply soon.
To start, Fork the repository and clone it locally. Connect your local to the original ‘upstream’ repository by adding it as a remote. Pull in changes from ‘upstream’ often so that you stay up to date so that when you submit your pull request, merge conflicts will be less likely. See more detailed instructions here.
Create a branch for your edits.
Be clear about the steps you took to make your changes.
Run your changes against any existing tests if they exist and create new ones when needed.
Include screenshots of the before and after if your changes include differences in HTML/CSS. Drag and drop the images into the body of your pull request.
Contribute in the style of the project to the best of your abilities. This may mean using indents, semi colons or comments differently than you would in your own repository, but makes it easier for the maintainer to merge, others to understand and maintain in the future.
Once done, send a pull request. A discussion will start around your proposed changes. You may be asked to make some changes to your pull request, if so, add more commits to your branch and push them – they’ll automatically go into the existing pull request.
Document the changes on the wiki

Provide feedback