List view
- Due by August 20, 2023•2/2 issues closed
- Due by August 13, 2023•7/7 issues closed
- Due by August 5, 2023•6/6 issues closed
- Due by July 29, 2023•10/10 issues closed
- Due by July 22, 2023•4/4 issues closed
- Due by July 1, 2023•2/2 issues closed
- Due by June 24, 2023
- Due by June 18, 2023
- Due by May 31, 2023•1/1 issues closed
https://github.com/fossasia/open-event-frontend/milestone/42
No due datehttps://github.com/fossasia/open-event-frontend/milestone/40
No due date•1/1 issues closed- No due date•1/1 issues closed
- Due by September 15, 2019
- Due by September 8, 2019•2/2 issues closed
- Due by September 1, 2019•6/6 issues closed
- Due by August 25, 2019•7/7 issues closed
- Due by August 18, 2019•14/14 issues closed
- Due by August 11, 2019•17/17 issues closed
- Due by August 4, 2019•12/12 issues closed
- Due by July 28, 2019•4/4 issues closed
- Due by July 21, 2019•7/7 issues closed
- Due by July 14, 2019•1/1 issues closed
- Due by July 7, 2019•7/7 issues closed
- Due by June 30, 2019•3/3 issues closed
- Due by June 23, 2019•10/10 issues closed
Ironing out bugs and moving forward with new features
Due by June 16, 2019•7/7 issues closedFinalize fixes and features for stable version.
Due by June 9, 2019•3/3 issues closed- Due by September 5, 2017•3/3 issues closed
- Due by August 29, 2017•1/1 issues closed
- Due by August 27, 2017•15/15 issues closed
- Due by August 20, 2017•31/31 issues closed
- Due by August 13, 2017•30/30 issues closed
Milestone 0 (GSoC 2017) - All issues to be completed by 7 May 2017. Milestone 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, 2017- Due by August 6, 2017•28/28 issues closed
- Due by July 30, 2017•18/18 issues closed
- Due by July 23, 2017•32/32 issues closed
- Due by July 16, 2017•28/28 issues closed
- Due by July 9, 2017•25/25 issues closed
- Due by July 2, 2017•21/21 issues closed
- Due by June 25, 2017•19/19 issues closed
- Due by June 18, 2017•11/11 issues closed
- Due by June 11, 2017•18/18 issues closed
- Due by June 4, 2017•19/19 issues closed
- Due by May 28, 2017•18/18 issues closed
- Due by May 21, 2017•17/17 issues closed
- Due by May 14, 2017•1/1 issues closed
GSOC 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•81/81 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 21, 2016•123/123 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•119/119 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•110/110 issues closed