==Week 1 (May 23rd - May 30th)==
- Integration of Travis-CI testing bot to my personal repository at the moment for development. This bot will be used for continuous testing and integration of the app. Once we (I and the mentors) decide on the general repository to use for development, I will just transfer the Travis settings to the repo.
- Travis-CI is configured to do the following functions;
** Post messages (build related messages) to the Wikidata feed channel on Freenode (#wikidata-feed) so as to notify others on how the development is going (just for monitoring purpose)
** When the build fails or passes, an email is sent to me also for notification.
- Here is a link to the Travis file on Github: [[https://github.com/ch3nkula/ifttt/blob/master/.travis.yml | Travis Settings on Github]]
- I and the mentors have decided a repository that I will be pushing my codes to and it's the official Wikimedia IFTTT repository that can be found here: [[https://github.com/wikimedia/ifttt | Wikimedia IFTTT Github app]].
- Created a GSoC development branch that will be used to push my codes to on the official Wikimedia IFTTT repo. This will enable mentors to review, comment and merge my codes when its ready to the master branch.
** Main Wikimedia IFTTT repo [[https://github.com/wikimedia/ifttt | master branch]].
** My GSoC Wikimedia IFTTT [[https://github.com/wikimedia/ifttt/tree/gsoc | development branch]].
==Week 2 & Week 3 (30th May - June 12th)==
- Wrote unit test for Wikipedia Article of the Day trigger and ran a client test against the trigger and it was working correctly returning the correct result set.
- Wrote unit test for Wikipedia New Article trigger and ran a client test against the trigger and it was working correctly returning the correct result set.
- Wrote unit test for Wikipedia Word of the Day trigger and ran a client test against the trigger and it was working correctly returning the correct result set.
- Wrote unit test for Wikipedia Picture of the Day trigger and ran a client test against the trigger and it was working correctly returning the correct result set.
- At this juncture, 4 tests are working correctly (passing) out of the 6 non-database driven tests I have to write. But 2 tests are still failing. Working on these two test and also fixing some few bugs and doing code clean up.
- Wrote a Wikidata trigger with name "Item Revision" for which when a particular item in Wikidata is revised, for example(Q12345), the trigger fires and performs the respective actions.
- Developed an RSS View for Item Revisions trigger and an XML template for it for rendering of the data using the browser. The commit can be seen here on my Github account: The commit can be seen here on my Github account: [[https://github.com/ch3nkula/ifttt/commit/1bd3e5c086debb0c4e69a3903ca0878e05e59c78 | RSS View Commit]].
- Fixed bug that was causing the non-DB to fail and now all tests, including the test for my new Item Revision trigger is passing. Also, updated the read me file to contain news triggers that are being developed.
- Synchronized my online and local development Github branches with the official GSoC development branch in the Wikimedia IFTTT repo and re-committed the whole work I have done, this is because of conflicts that originated when I made a PR to the official Wikimedia IFTTT code base which was different (setup) from that of Stephen that I was using before. The working PR without any conflicts can be seen here: [[https://github.com/wikimedia/ifttt/pull/14/files | Pull Request ]]
==Week 4 (13th June - June 19th)==
- As instructed by the mentor, I started deploying me work on Wikimedia Tool Labs for integration testing with IFTTT. The mentor added me to a Wikipedia staging channel for me to do integration testing with IFTTT.
- The Wikimedia Tool Labs instance I am using is "ifttt-testing" and can be accessed by using this link: [[http://tools.wmflabs.org/ifttt-testing/ifttt/v1/rss-feeds | IFTTT Test Instance (RSS Feeds Example)]] and it has been configured to run my application for testing within the server and also in the Wikipedia staging channel.
** NOTE: Once in a while, we shall have a 404 - Not Found error while trying to access this link since its still unstable as I am working on the server on a daily basis, its a test instance.
- Deployed the application on Tool Labs and Integrated to IFTTT Wikipedia Staging to test the functionalities and also the trigger I have developed.
** Trigger was working properly when configured.
** All RSS Views where functioning properly
** All tests where passing on Tool Labs
- Fixed Links in the feeds.html file to point to the correct lab instance and no longer "localhost" as before and fixed all the codes to adapt to the configurations of my Lab Instance.
==Week 5 & 6 (19th June - July 8th)==
- Submission of Midterm evaluations by both mentors and students. Students evaluate mentors and organisations activities and mentors evaluate their students and both submit evaluations to Google.
- Midterm results announced by Google
- My midterm evaluations results: **Passed**
- Started my semester exams
- Wrote my semester exams for 2 weeks as on the time line.
==Week 7 (9th July - July 15th)==
- Built the RSS view for Database Driven trigger (New Hashtags), Since I have access to the DB now on Tool labs, I can retrieve data concerning this trigger directly from the Database. Here is an example of the RSS: [[http://tools.wmflabs.org/ifttt-testing/ifttt/v1/triggers/new_hashtag?lang=en&hashtag=test | New Hashtag for test hashtag]].
- Unit test for New Hashtag passes on Tool labs including other tests because of the presence of the DB but on localhost, this test fails and other database driven test because of the absence of the Wikidata database on my localhost.
- Fixed the Issue of RSS views working with GET request without checking channel key. The issue here was "if RSS views are working, the integration tests fails on IFTTT or if Integration tests are passing, the RSS views are not working due to the @app.before_request me that checks the channel key before any request". So I added a check to ignore all these on get request using `if flask.request.method == 'GET': # do something`. At this point, both RSS views and Integration Endpoint tests on IFTTT are working (but some regression occurs, needs to be looked at).
- Integration of newly developed trigger "New edit to Wikidata Item" into IFTTT and integration testing. So far, the trigger is working fine and fires when a particular item is edited.
- Added Style to the RSS views to improve on UI/UX of the RSS views of the App. For the bootstrap integration into the app, I used the flask.ext.bootstrap and specifically the Bootstrap Module.
==Week 8 (16th July - July 22nd)==
- Debugged IFTTT integration tests together with Stephen LaPorte and all was passing. Integration of Wikidata Edit Item trigger to IFTTT.
- Wrote code for GET request to handle parameters for triggers just as the POST request in the app. The commit can be found here: [[https://github.com/ch3nkula/ifttt/commit/751582134d105f5869918f7b32c7b39e290c3953 | Fixing Regression Commit]].
- Re-wrote and Improved on the Unit tests for all the triggers found in the `ifttt-testing.py` file. This improved on the efficiency and getting default trigger values from the `trigger.py` file and feeds directly into the tests fields. Here are the commits [[https://github.com/ch3nkula/ifttt/commit/9280f6bd57c605d05a8ae0930fa66cedae5a6e50 | Working Commit - Commit 1]] and [[https://github.com/ch3nkula/ifttt/commit/b0c25b4acdb9e3cd6796697ea3ed2023956b6ac6 | Efficient and Working commit - Commit 2]]
- After debugging IFTTT integration / endpoint tests with Stephen, this caused a bug in the unit tests which where all not returning data because app.debug was set to True. I debugged this and constrained app.debug to be True only in the context of the FlaskClient tests instance (app.test_client()) so that in the global context, it will be False and the test in the IFTTT integration will all pass. The result of this made both the unit tests and endpoint tests on IFTTT to pass. Here is the commit: [[https://github.com/ch3nkula/ifttt/commit/154a55d60792c4c699947327344c13d242115c24 | Commit]] ( Shocked :-) )
- Added RSS/XML for two last database driven triggers. New category member and Category member revisions, these triggers where challenging to build the RSS since we had to search on Wikipedia categories that are recently edited. It took me some time but finally got it with the help of my mentor (Slaporte). The category we used is 'All articles lacking sources'.
- This two triggers (as mentioned above) was failing the unit tests and had no RSS, but after these commits: [[https://github.com/ch3nkula/ifttt/commit/479b5cb136473221d0cd2ea0f565d7968c17a622 | Commit I]] and [[https://github.com/ch3nkula/ifttt/commit/c893640abb70e021ddb12ad54b73b89b58d3b2fb | Commit II]], the RSS was available and unit tests where passing (all unit tests in the app).
- A sample of the output of the RSS of the triggers can be seen here: [[http://tools.wmflabs.org/ifttt-testing/ifttt/v1/triggers/new_category_member?lang=en&category=All%20articles%20lacking%20sources | New category members]], [[http://tools.wmflabs.org/ifttt-testing/ifttt/v1/triggers/category_member_revisions?lang=en&category=All%20articles%20lacking%20sources | Category member revisions]]
- Item revisions trigger integration tests on IFTTT was failing because of a bug (configuration) that doesn't match the code in the IFTTT app, but together with Stephen on our weekly meeting (21st July, 2016), we debugged the integration tests and the Wikipedia Staging channel passed. Now all tests on IFTTT passes and also all Unit Tests on Tool Labs also pass. Hurrayyy!!! :)
==Week 9 (23rd July - July 29th)==
- Learning the Wikidata Query Services (WDQS) and SPARQL. Experimentation is done here: [[https://query.wikidata.org | Wikidata Query Service (WDQS)]].
- Created a Google doc as instructed by my mentors to draft a blog post for the project. The link to the Doc can be found here: [[https://docs.google.com/document/d/15TSm06z0r8jNml6uhUzM1IwPqY8xFeffwpSdNwbH3ow/edit?usp=sharing | Blog post draft]].
- Thinking and sampling trigger Ideas with the mentors to find the right one to implement for Wikidata using the WDQS and the flask app. So far, we have a list of these trigger ideas:
** Notify me whose birth days is today.
** Notify me when today is a public holiday (we can decide for particular countries) e.g. Notify me when today is a public holiday in the US
** Notify me when my favorite author releases a new book.
- Working on the blog post draft on Google docs and developed on the following sections;
** What is Google Summer of Code?
** Why did I apply for GSoC?
** Why the Wikimedia Foundation?
** How has the development of my project looked like?
** Request for help from community members on my project
** Appreciation and Thanks to my mentors and the Wikimedia Foundation
- More work on the blog post and addition of content to the various sections
** My recommendations for anyone to participate in GSoC/Wikimedia and Why?
** What I did not anticipate that will happen during GSoC?
==Week 10 (30th July - August 5th)==
* Studying of Wikidata Items (objects) and Wikidata properties to come up with trigger ideas.
* More trigger Ideas sent to mentors for evaluation, below are the trigger ideas
** Notify me about the number of new Wikidata items added today.
** Notify me about the number of new Wikidata item properties added today
** Notify me about how many people have birthdays today (could be a very huge number). But this one will be limited to the amount of data in Wikidata (definitely not the whole world).
* Worked on the "Experience gained through this project during GSoC" section of my GSoC blog post document and submitted for review to @Lydia_Pintscher.