Hi<div><br></div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I'd think the changes to SWIG would take a lot more time than adjusting<br>
the wrapped API.<br>
<br>
Maybe it is worth noting that you can plan to tackle things in whatever<br>
order seems most sensible. The changes to the existing wrapped API<br>
might serve as a more gentle start, but doing the larger part of the<br>
project first would mean you'd be more likely to have more actually<br>
completed if things take longer than expected.<br></blockquote><div> I will take you comment suggestion about timing in consideration. </div><div>What do you thing about this <span style>Schedule?</span></div><div style>
<ol><li style="margin-left:15px">April 30 – May 20 : Checking the Coding guidelines, Installing development environment, Reading and understanding deeply the source
<span style="font-family:arial;font-size:small"> SWIG </span> and
<span style="font-family:arial;font-size:small">wrapped API</span> , Discussing with mentors about the final details of the project</li><li style="margin-left:15px">May 21 – May 29: Defining the changes needed in
<span style="font-family:arial;font-size:small">SWIG</span></li><li style="margin-left:15px">May 28 - July 13: adding new function to <span style="font-family:arial;font-size:small">SWIG</span></li><li style="margin-left:15px">
JULY 13</li><li style="margin-left:15px">MID TERM EVALUATION Dead line</li><li style="margin-left:15px">July 13 –July 22: adding new function to SWIG, Testing SWIG,
Writing the documentation for SWIG</li><li style="margin-left:15px">July 23 – August 15: Improving the xapian php api</li><li style="margin-left:15px">August 16-August 20: Testing the new version of the xapian api, Writing the documentation for it</li>
</ol></div><div>For the mid term evaluation do I need to make a deliverable?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> - Do you think it would be better to redesign the hole php xapian api?<br>
<br>
I don't think so - change without a good reason will just annoy existing<br>
users of the PHP API.<br></blockquote><div>Ok, I will not do that. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> - who will be mentoring this project?<br>
<br>
We're intending to use a similar "group mentoring" approach as we did<br>
last year, so you'll be expected to discuss issues and ask questions in<br>
the IRC channel or on the mailing list, which is better for you as it<br>
means you don't have to wait for your mentor to be able to respond, and<br>
better for us as it makes it easier to keep track of how everyone's<br>
doing. Public communication is also the way open source projects<br>
usually work, and GSoC is meant to give you experience of working in<br>
an open source project.<br></blockquote><div>I like the idea of group mentoring. Its seems more flexible.</div><div><br></div><div>Just last question, was xapian accepted before to GSoC, and if it was, how many projects were accepted?</div>
<div><br></div><div>Thank you for you time.</div><div><br></div></div>Yours sincerely</div><div>Riadh</div>