Hi Daniel, According to your comments I rewrite again schedule. Time I can spend on the project: May 1 - June 28 – 20h, June 29 - end of GSoC – 40h (a full time worker). Smaller amount of hours in May and June is connected with my university duties.
Schedule: Week 1 (May 1st - May 9th). Preparations (20h/week) - read documentation - write simple tests cases - construct a preliminary design of the tests/framework - getting ready - other? Week 2 - 7 (May 10th - June 20th). Creation of tests cases that stress the most important parts of the system (20h/week, 120h total) Week 2: PTmender tests cases - selection of images - creation of scripts - creation of reference output images - I had some experience with PTmender while I was doing vetting exercise, so I put this tool at the beginning Week 3: PTroller and PTtiff2psd tests cases - selection of images - creation of scripts - creation of reference output images - PTroller and PTtiff2psd seem to be a good start to learn more about the tools (May 24 - Students begin coding for their GSoC projects) Week 4: PTmasker, PTcrop and PTuncrop tests cases - selection of images - creation of scripts - creation of reference output images Week 5: PToptimizer tests cases - selection of images - creation of scripts - creation of reference output images - PToptimizer is one of the main tool in the library, so I put it in the ending of the list - at that moment I will have much more experience with the tools than at the beginning Week 6: PTBatcher tests cases - selection of *.pro files - creation of scripts - creation of reference - PTBatcher is almost at the end, because it combines tools listed above Week 7: Tests cases improvements - improving of tests cases - creation of documentation - creation of new test cases if necessary After each week of this phase I will deliver a new or improved set of tests and scripts I made for running those tests. At the end of week 7 I will deliver also a documentation. I'm not sure if this time order is right. Week 8 - 10 (June 21 - July 11). Creation of the framework (20h/week till June 28, 40h/week after June 29; 100h total). Week 8: Creation of the tool for the automatic testing based on the tests created, integrate with scripts created during last phase (creation of tests cases) - additionally still improving of tests cases - at the end of this week I will deliver a new tool for the framework Week 9: Adding new functionality for the framework - tool that simplifies the creation of new tests - improving of tests cases, again - at the end of this week I will deliver a new tool for the framework Week 10: Finalization of this sub-project - creation of documentation - improving of the framework code - checking, improving and adding test cases - submit mid-term evaluation (July 12 - Mentors and students can begin submitting mid-term evaluations) Function level testing framework - not ready, planning still in progress Week 12 (July 12 - July 18). Determine what functionality (what functions) need to be tested in function level testing framework (40h/ week). (July 16 - Mid-term evaluations deadline) Week 13 - Week 15 (July 19th - August 8th). Make framework for testing the main functionality of libpano as used by hugin (function level) (August 9 - Suggested 'pencils down' date. Take a week to scrub code, write tests, improve documentation, etc) Week 16 (August 9th - August 15th). Code improvements, tests, documentation,... (August 16 - Firm 'pencils down' date. Mentors, students and organization administrators can begin submitting final evaluations to Google) (August 20 - Final evaluation deadline) Best regards, Tom -- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
