User:Miriya52/PythonLibrary serialize Wikimedia Quiz format

Project Phabricator task: T89761

Proposal T148072

Community Bonding Period

 * 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
 * Communication plan with mentor decided


 * [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.)
 * [ ] Participating on Mailing Lists / IRC / etc. (Not just lurking.)
 * [ ] Setting up their development environment.
 * [X] Small (or large) patches/bug fixes. (These do not need to be directly related to the Outreachy project.)
 * [ ] Participating in code reviews for others. (Even someone who isn't familiar with the project can contribute by pointing out potential inefficiencies, bad error handling, etc.)
 * [ ] 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.
 * [ ] If the intern is already familiar with the organization, they could be helping others get involved in the community.
 * [ ] 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.

Week 1: December 6 - December 9

 * 1) point 1
 * 2) point 2

Mid Term
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

Final Evaluation
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