User:Miriya52/PythonLibrary serialize Wikimedia Quiz format

Project Phabricator task: T89761

Proposal T148072

Internship blog

Community Bonding Period

 * [X] Work done (environment setup, links to patches merged etc.)
 * Lessons learnt
 * Problems faced and solutions found
 * Any changes to the original plan
 * [X] Minimum Viable Product for the project decided
 * [X] Communication plan with mentor decided. Gitter, because it has a mobile platform


 * [X] Detailed plan agreed with your mentors.
 * [X] Request creation of Phabricator project (instructions).
 * [X] Meetings with mentors started.
 * [] Bonding period report published.


 * [X] Becoming familiar with the community practices and processes. (This often involves a mix of observation and participation.)
 * [X] Participating on Mailing Lists / IRC / etc. (Not just lurking.)
 * [X] Setting up development environment.
 * [X] Small (or large) patches/bug fixes. (These do not need to be directly related to the Outreachy project.)
 * Working with their mentor and other org members on refining their project plan. This might include finalizing deadlines and milestones, adding more detail, figuring out potential issues, etc.
 * Reading (and updating!) documentation they will need to understand to complete their project.
 * Reporting or replicating bugs.

Preparation Tasks

 * [Oct 2016] Investigation of Pyslet package for Standards in Learning Education and Training (LET). It implements a number of LET-specific standards, including IMS QTI, Content Packaging and Basic LTI. It also includes support for some general standards, including the data access standard OData (see http://www.odata.org).
 * [Oct 27 2016] Submitted a pull request in the pyslet project to fix remaining PEP8 errors.
 * [Nov 16 2016 - ??] Running   in pyslet, and create a wiki page on your fork describing the various problems it finds. That wil, help us determine if swl10/pyslet#38 is feasible. Also does pyslet have good unit tests for the functionality we are interested in? If not, adding some unit tests will improve your knowledge about that library.

Bonding Period Report (before Dec 6)
MVP is "bi-directional support. Tools need to be able to parse and update Quiz data on Wikiversity.  Almost every other embedded content in wikitext is in a format that has parsers and python libraries - this one doesn't." Retain style/token information so round-trip conversion has very few dirty diffs.

Use cases include:
 * Importing quizzes from other systems in Wikiversity, to back up materials for mooc/quiz systems going offline or being upgraded.
 * Generate custom/personalized quiz (in Python) and push to Wikiversity user page
 * Gamification of Wikimedia, using Python webapps deployed on the tool labs.
 * (See comments in original phabricator task: https://phabricator.wikimedia.org/T89761)

Communication on Gitter (https://gitter.im/WM-quiz-serialize/Lobby). Gitter has a mobile app.

My development environment will primarily be a cloud Ubuntu 16.04 server and sublime text on MacOS for syntax highlighting, which was useful for fixing PEP8 errors.

My medium blog posts [Nov 17, Dec 1] discussed the preparation tasks I worked on before official internship start date of December 6, 2016.

Additional comments

 * I will be using my travel allowance to attend Wikimedia Developer Summit. I reviewed the proposal topics and provided feedback on my topics of interest.
 * I have also looked into packaging a Python library (Packaging a Python Library (PyCon 2016), Hitchhiker's Guide to Python - Structuring Your Project)

Week 1: December 6 - 9

 * 1) point 1
 * 2) point 2

week 1 report

Week 2: December 12 - 16

 * 1) point 1
 * 2) point 2

Week 3: December 19 - 23

 * 1) point 1
 * 2) point 2

Week 4: December 26 - 30

 * 1) point 1
 * 2) point 2

Week 5: January 2 - 6

 * 1) point 1
 * 2) point 2

Week 6: Wikimedia Developer Summit, January 9 - 13
Wikimedia Developer Summit (Jan 9-11, 2017) Trip Report What did I learn or accomplish? How did it improve my ability to contribute to free and open source software?

Week 7: Mid Term Report, January 16 - 20
Weekly reports up to date. Patches published and accepted (or equivalent for non-coding projects). Regular meetings with mentors. If there is a delay in expected deliveries, plan updated accordingly. Full-time routine established

Week 8: January 23 - 27

 * 1) point 1
 * 2) point 2

Week 9: January 30 - February 3

 * 1) point 1
 * 2) point 2

Week 10: February 6 - 10

 * 1) point 1
 * 2) point 2

Week 11: February 13 - 17

 * 1) point 1
 * 2) point 2

Week 12: February 20 - 24

 * 1) point 1
 * 2) point 2

Week 13: February 27 - March 3

 * 1) point 1
 * 2) point 2

Final Evaluation (March 6, 2017)
Weekly reports up to date. In sync with mentors. Full-time routine. Project completed, or at least a functional prototype. Tasks created for known bugs, missing features, and suggested improvements. Documentation for users and contributors. Wrap-up report. Summary in Past projects page