List view
- Due by August 20, 2023
- Due by August 13, 2023
Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done
Due by May 14, 2017Milestone 0 (GSoC 2017) - All issues to be completed by 7 May 2017. Instructions: * Create issues to work on * Assign the issue to the milestone * Assign the issue to a user (yourself) * Tag a release * Deploy on a server * Completed Milestone: Create a blog post describing what has been done
Due by May 7, 2017GSOC 2016 Milestone 15 - All issues to be completed by 29th August 2016. Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user. Completed Milestone: 1. Create a blog post describing what has been done. 2. Tag a release. 3. Deploy on a server.
Due by August 29, 2016•40/40 issues closedGSOC 2016 Milestone 14 - All issues to be completed by 21st August 2016. Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user. Completed Milestone: 1. Create a blog post describing what has been done. 2. Tag a release. 3. Deploy on a server.
Due by August 22, 2016•40/40 issues closedGSOC 2016 Milestone 13 - All issues to be completed by 14th August 2016. Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user. Completed Milestone: 1. Create a blog post describing what has been done. 2. Tag a release. 3. Deploy on a server.
Due by August 13, 2016•29/29 issues closedGSOC 2016 Milestone 12 - All issues to be completed by 7th August 2016. Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user. Completed Milestone: 1. Create a blog post describing what has been done. 2. Tag a release. 3. Deploy on a server.
Due by August 6, 2016•26/26 issues closedGSOC 2016 Milestone 11 - All issues to be completed by 31st July 2016. Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user. Completed Milestone: 1. Create a blog post describing what has been done. 2. Tag a release. 3. Deploy on a server.
Due by July 30, 2016•17/17 issues closedGSOC 2016 Milestone 10 - All issues to be completed by 24th July 2016. Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user. Completed Milestone: 1. Create a blog post describing what has been done. 2. Tag a release. 3. Deploy on a server.
Due by July 23, 2016•12/12 issues closedGSOC 2016 Milestone 9 - All issues to be completed by 17th July 2016. Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user. Completed Milestone: 1. Create a blog post describing what has been done. 2. Tag a release. 3. Deploy on a server.
Due by July 16, 2016•25/25 issues closedGSOC 2016 Milestone 8 - All issues to be completed by 10th July 2016. Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user. Completed Milestone: 1. Create a blog post describing what has been done. 2. Tag a release. 3. Deploy on a server.
Due by July 9, 2016•29/29 issues closedGSOC 2016 Milestone 7 - All issues to be completed by 3rd July 2016. Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user. Completed Milestone: 1. Create a blog post describing what has been done. 2. Tag a release. 3. Deploy on a server.
Due by July 2, 2016•34/34 issues closedGSOC 2016 Milestone 6 - All issues to be completed by 26th June 2016. Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user. Completed Milestone: 1. Create a blog post describing what has been done. 2. Tag a release. 3. Deploy on a server.
Due by June 25, 2016•56/56 issues closedGSOC 2016 Milestone 5 - All issues to be completed by 19th June 2016. Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user. Completed Milestone: 1. Create a blog post describing what has been done. 2. Tag a release. 3. Deploy on a server.
Due by June 18, 2016•36/36 issues closedGSOC 2016 Milestone 4 - All issues to be completed by 12th June 2016. Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user. Completed Milestone: 1. Create a blog post describing what has been done. 2. Tag a release. 3. Deploy on a server.
Due by June 11, 2016•39/39 issues closedGSOC 2016 Milestone 3 - All issues to be completed by 5th June 2016. Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user. Completed Milestone: 1. Create a blog post describing what has been done. 2. Tag a release. 3. Deploy on a server.
Due by June 4, 2016•16/16 issues closedGSOC 2016 Milestone 2 - All issues to be completed by 29nd May 2016. Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user. Completed Milestone: 1. Create a blog post describing what has been done. 2. Tag a release. 3. Deploy on a server.
Due by May 28, 2016•7/7 issues closedGSOC 2016 Milestone 1 - All issues to be completed by 22nd May 2016. Instructions: 1. Create issues to work on. 2. Assign the issue to the milestone. 3. Assign the issue to a user. Completed Milestone: 1. Create a blog post describing what has been done. 2. Tag a release. 3. Deploy on a server.
Due by May 21, 2016•7/7 issues closedClean up code base to set up for upcoming milestone 6 development. TODO: - bring down all lint issues to a minimal (< 100 issues) - update all dependencies and fix any breaks - create tests to achieve > 90% code coverage
Due by April 21, 2016•5/5 issues closed- Due by September 9, 2015•2/2 issues closed
- Due by August 20, 2015•8/8 issues closed
- Due by July 24, 2015•11/11 issues closed
- Due by June 9, 2015•8/8 issues closed
- Due by June 25, 2015•12/12 issues closed