Roundtable | Summer of CodeWeek 1 (May 21th - May 28th) |
Planning Session
Date: May 22th, 2017
Attendees: Kaushik, Yash, Georges
(Also available in GNOME Etherpad)
Goals Of The Week
Goal |
Deliverable |
Achieved |
Rohit Kaushik |
||
Finish the Todo.txt work |
Patches implementing the rearchitecture of the provider. |
Success |
Create a Todoist plugin skeleton |
Patches adding the stub files and preferences panel. |
Failed |
Learn about GOA codebase |
Class diagram of the GNOME Online Accounts codebase. |
Failed |
Yash Singh |
||
Write 2 posts |
A blog post introducing the project, and another one about 'has-recurrence' |
Success |
Add a new modify/remove recurrent events dialog |
Patches adding the new dialog, and modifying GcalManager. |
Failed |
Plan
Yash
- I have to add the necessary functions to support the 3 options listed above, that'd require more digging into the Evolution API
a) GcalEditDialog b) GcalEvent, possibly create a new dialog - GcalRecurrenceDialog or something
Kaushik
Implement the rearchitectured GtdProviderTodoTxt
- Add all the necessary files in plugins/todoist/*, edit src/Makefile.am and etc
Create a GtdPluginTodoist class
Create a GtdTodoistPreferences class
- Create a basic outline for preferences panel and then we can improve upon them
Write a class diagram & documentation about GOA classes
Challenges & Obstacles
Yash:
- I have to understand the link between recurrent events. This basically means that If an event is repeating 10 times, how are these 10 instances connected to each other
- We may also have to see how these 10 recurring events' links are different from other recurrent events (like 5 instances of some other event)
- All the work relies upon the friendly functions present in the Evo API. By friendly functions I mean, those functions that will allow me to implement these 'targeted changes' (subsequent events etc.)
Kaushik:
- I don't think I will face difficulty in Todo.txt work
- GOA makes use of DBus which I am very new to