Table of Contents

1. Community Bonding Period: April 23 – May 13
2. Coding Week 1: May 14–May 20
3. Coding Week 2: May 21–May 27
4. Coding Week 3: May 28–June 3
5. Coding Week 4: June 4–June 10
6. Coding Week 5: June 11–June 17 (evaluations: June 11-15)
7. Coding Week 6: June 18–June 24
8. Coding Week 7: June 25–July 1
9. Coding Week 8: July 2–July 8
10. Coding Week 9: July 9–July 15 (evaluations: July 9-13)
11. Coding Week 10: July 16–July 22
12. Coding Week 11: July 23–July 29
13. Coding Week 12: July 30–August 5
14. Coding Week 13: August 6–August 12 (evaluations: August 6-14)

Community Bonding Period: April 23 – May 13

● Understand the codebase.Learn more about swig-based bindings and about make dist error in xapian-letor.

Coding Week 1: May 14–May 20

● Create practical code examples that use core features and API,fix the issues with the incomplete PR of ayush_pandey. ● Add documentation of how to use the training API as well as the letor re-ranking API.

Coding Week 2: May 21–May 27

● Write test about various api's and unit test cases for features. Release PR's for this part and start the implementation-review-change cycle.

Coding Week 3: May 28–June 3

● Write test about various api's and unit test cases for features(continued). Fix other known issues in xapian-letor.

Coding Week 4: June 4–June 10

● Finish any work after changes suggested by mentors to make it ready to merge into master.

Coding Week 5: June 11–June 17 (evaluations: June 11-15)

● Fix the problem with make dist in xapian-letor and make xapian-letor officially releasable.

Coding Week 6: June 18–June 24

● Understand more about bindings and related code. Add binding support for various languages.

Coding Week 7: June 25–July 1

● Add binding support for various languages(continued). Start the implementation-review-change cycle.

Coding Week 8: July 2–July 8

● Add binding support for various languages(continued). Make it ready to get merged into the master. ● Write example code in python,java etc. Write Docuementation for example code.

Coding Week 9: July 9–July 15 (evaluations: July 9-13)

● Fix the issues discussed above and likely many more in xapian-evaluation module.

Coding Week 10: July 16–July 22

● Start discussing the implementation of adding support for the database backend. ● Fix the issues discussed above and likely many more in xapian-evaluation module(continued). Also fix other known issues or tickets.

Coding Week 11: July 23–July 29

● Add support for letor in xapian-evaluation and test the performance of xapian-letor against standard benchmark datasets. ● Buffer period for any remaining work in xapian-evaluation. Also carry the discussion of the implementation of adding support for the database backend

Coding Week 12: July 30–August 5

● Add support for database backend to track the length of the fields.

Coding Week 13: August 6–August 12 (evaluations: August 6-14)

● Add support for database backend to track the length of the fields(continued). ● Make sure the code get's merged. Buffer period for any remaining work.