Init commit

README.md

+# GitLab GSoC 2016
+
+Welcome to GitLab Google Summer of Code 2016!
+
+Below are some useful links to get you started.
+
+- [Communication](communication.md) - There are more than one ways to communicate
+- [Guidelines](guidelines.md) - The steps to get you started with your
+  application
+- [Ideas Page](ideas.md) - The recommended ideas for GSoC 2016 and the
+  associated mentors
+- [GitLab Application template](gitlab-application-template.md) - A template
+  to use for your application
+- [Development workflow](workflow.md) - The workflow of GitLab's development

communication.md

+- [Guidelines](guidelines.md) - The steps to get you started with your
+  application
+- [Ideas Page](ideas.md) - The recommended ideas for GSoC 2016 and the
+  associated mentors
+- [GitLab Application template](gitlab-application-template.md) - A template
+  to use for your application
+- [Development workflow](workflow.md) - The workflow of GitLab's development
+
+---
+
+You can communicate with the rest of the GitLab community by one of the
+following ways:
+
+- Open a new topic in [our forum](https://forum.gitlab.com/c/gsoc/gsoc-2016)
+- Subscribe to [our mailing list](https://groups.google.com/forum/#!forum/gitlabhq)
+  and start a new discussion
+- Ask a question in [our IRC channel](https://webchat.freenode.net/?channels=gitlab)

gitlab-application-template.md

+Applications must be made in text format - you may use [GitLab flavored Markdown](/help/markdown/markdown.md).
+
+## Contact information
+
+* Your Name: {required}
+* Email Address: {required}
+* GitLab Username: {required}
+* GitHub Username: {required}
+* Twitter Username: {optional}
+* IM Address: {optional}
+* IRC Nickname: {optional}
+* Webpage/Blog: {optional}
+* College/University: {required}
+* Subject/Major: {required}
+
+## Project
+
+### Project Name
+
+{Your project's name}
+
+### Project Description
+
+{Your project's description}
+
+### Why did you choose this idea?
+
+{Your response}
+
+### Please describe an outline project architecture or an approach to it
+
+{Your response}
+
+### Give us details about the milestones for this project
+
+{Your response}
+
+### Why will your proposal benefit GitLab?
+
+{Your response}
+
+## Open Source
+
+### Please describe any previous Open Source development experience if any
+
+{Your response}
+
+### Why are you interested in Open Source?
+
+{Your response}
+
+## Availability
+
+### How long will the project take? When can you begin?
+
+{Your response}
+
+### How much time do you expect to dedicate to this project? (weekly)
+
+{Your response}
+
+### Where will you be based during the summer?
+
+{Your response}
+
+### What timezone will you be working in and what hours do you plan to work? (so we can best match mentors)
+
+{Your response}
+
+### Do you have any commitments for the summer? (holidays/work/summer courses)
+
+{Your response}
+
+## Other
+
+### Have you ever participated in a previous GSoC? If yes, describe your project.
+
+{Your response}
+
+### Have you applied for any other 2016 Summer of Code projects? If yes, which ones?
+
+{Your response}
+
+### Why did you apply for the Google Summer of Code ?
+
+{Your response}
+
+### Why did you choose GitLab as a mentoring organization?
+
+{Your response}
+
+### Why do you want to participate and why should GitLab choose you?
+
+{Your response}

guidelines.md

+- [Communication](communication.md) - Get in touch with the GitLab community
+- [Ideas Page](ideas.md) - The recommended ideas for GSoC 2016 and the
+  associated mentors
+- [GitLab Application template](gitlab-application-template.md) - A template
+  to use for your application
+- [Development workflow](workflow.md) - The workflow of GitLab's development
+
+---
+
+Students should at least complete the following steps on or before 25 March
+(1900 UTC) to get qualified (valid submission):
+
+1. Own a GitLab.com account
+1. Application is available in the `applications/` directory according to
+  [application guidelines](#gitlab-application-guidelines)
+1. Application is submitted to google-melange
+
+Missing one of the above will result in rejecting your application. Therefore
+please be extra careful.
+
+## Timeline
+
+Make sure to familiarize yourself with the [GSoC 2016 timeline]
+(https://developers.google.com/open-source/gsoc/timeline).
+
+The notable dates and deadlines are depicted in the following table.
+
+| Date | Event |
+| ---- | ----- |
+| 29 February - 13 March | Would-be student participants discuss application ideas with mentoring organizations. |
+| 14 March 19:00 UTC | Student application period opens. |
+| 25 March 19:00 UTC | Student application deadline. |
+
+## GitLab application guidelines
+
+1. [Create a GitLab.com account][acc] if you don't have one already.
+1. Login to GitLab.com and fork this repository.
+1. Clone your repository:
+
+    ```
+    git clone git@gitlab.com:<username>/gsoc2016
+    ```
+1. Set the upstream Git remote:
+
+    ```
+    git remote set ustream https://gitlab.com/gitlab-org/gsoc2016.git
+    ```
+
+1. Create a new branch to work on:
+
+    ```
+    git checkout -b username_application
+    ```
+
+    where `username` is your GitLab.com username.
+
+1. Copy the [application template](gitlab-application-template.md) to the
+   `applications/` directory renaming it using the following scheme:
+
+    ```
+    cp gitlab-application-template.md applications/<Name>_<Surname>_application.md
+    ```
+
+    where `<Name>` is your name and `<Surname>` is your surname.
+
+1. Edit your newly copied application and fill in the requested items by replacing
+   the curly braces (`{}`) with your response.
+
+1. Add and commit your changes:
+
+    ```
+    git add applications/<Name>_<Surname>_application.md
+    git commit
+    ```
+
+1. Push the branch to your fork:
+
+    ```
+    git push origin username_application
+    ```
+
+1. Submit a merge request by visiting https://gitlab.com/gitlab-org/gitlab-ce/merge_requests
+
+1. You can do any changes you want until the deadline.
+
+
+[acc]: https://gitlab.com/users/sign_up

ideas.md

+- [Communication](communication.md) - Get in touch with the GitLab community
+- [Guidelines](guidelines.md) - The steps to get you started with your
+  application
+- [GitLab Application template](gitlab-application-template.md) - A template
+  to use for your application
+- [Development workflow](workflow.md) - The workflow of GitLab's development
+
+**IMPORTANT:** It is crucial that you familiarize your self with the [GSoC timeline].
+
+---
+
+This page hosts the ideas GitLab proposes for Google Summer of Code 2016.
+
+You can discuss the ideas posted here or new ideas with others in our
+[forum](https://forum.gitlab.com/c/gsoc/gsoc-2016) (tip: you can login using
+your GitLab.com credentials).
+
+If you have an idea that is not in this page you can submit a merge request to
+this document. First make sure to search our wishlist in
+<https://about.gitlab.com/direction/> to see if your idea is already there.
+
+[GSoC timeline]: https://developers.google.com/open-source/gsoc/timeline
+
+Below are some ideas to get you started.
+
+## Internationalization / translations
+
+- **Relevant Issue:** https://gitlab.com/gitlab-org/gitlab-ce/issues/4012
+- **Mentor:** Pending
+- **Skills:** Rails
+
+## Mailing list functionality
+
+- **Relevant Issue:** https://gitlab.com/gitlab-org/gitlab-ce/issues/4272
+- **Mentor:** Pending
+- **Skills:** Rails, some theory behind how the various mail protocols work
+
+Right now, everyone that wants a mailing list for their project is required to
+use an external one like Google Groups.
+
+It would be nice if this could be done with GitLab. We already have the ability
+to read email for the [reply-to-email feature][inc-email]. Below are some rough
+points that would need to be implemented for this feature:
+
+1. Give each project a mailing list at `project/group@example.com`
+2. People joining the project are subscribed to this mailing list by default
+3. Only people with an account on the GitLab server can post
+4. Every email has a link that unsubscribes them without logging in
+
+[inc-email]: http://doc.gitlab.com/ce/incoming_email/README.html
+
+## Transactional merge request comments
+
+- **Relevant Issue:** https://gitlab.com/gitlab-org/gitlab-ce/issues/3364
+- **Mentor:** Pending
+- **Skills:** Rails
+
+The problem is that for each review or inline-code comment, a notification is
+sent out for each individual comment, which creates a lot of noise when
+receiving email notifications.
+
+One approach is to allow the review to create/draft many comments together and
+submit them all to be notified in batch (like Phabricator does it). The result
+is that only one notification/email gets sent out with all the comments and
+feedback contained within it. This mimics a review pass by the reviewer in that
+all feedback is captured by that one pass so that the individual can see the
+entire (holistic) feedback/comments instead of having them be itemized
+individually with no clear connection.
+
+## Cross-server (federated) merge requests
+
+- **Relevant Issue:** https://gitlab.com/gitlab-org/gitlab-ce/issues/4013
+- **Mentor:** Pending
+- **Skills:** Rails

workflow.md

+## Development workflow
+
+All development is done in GitLab's [public issue tracker][issues].
+
+Read more and get familiar with the [GitLab workflow](http://doc.gitlab.com/ce/workflow/README.html).
+
+[issues]: https://gitlab.com/gitlab-org/gitlab-ce/issues