<div dir="ltr"><div class="gmail_extra">Hi Yash!</div><div class="gmail_extra"><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div class="gmail_extra"><br></div></blockquote><div class="gmail_extra">I just reviewed <a href="https://developers.google.com/open-source/gsoc/help/work-product">https://developers.google.com/open-source/gsoc/help/work-product</a> for the pass criteria, which says:</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_extra">Requirements</div></div></div><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_extra"><br></div></div></div><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_extra">It must be easy to identify the work you have done. (i.e. the changes you made or new code.)</div></div></div><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_extra">When someone goes to the provided URL it should be crystal clear what work you did without requiring them to do signifcant additional digging.</div></div></div><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_extra">It should be in a stable location. It cannot be changed after submission.</div><div class="gmail_extra"><br></div></div></div></blockquote>I think <a href="https://github.com/sugarlabs/edit-fonts-activity/commits?author=YashAgarwal">https://github.com/sugarlabs/edit-fonts-activity/commits?author=YashAgarwal</a> is pretty good for this :) <br><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_extra"><br>Someone else should be able to use the content at (or referenced from) the target of the link to extend your work.</div></div></div></blockquote><div><br></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_extra">If your work is 100% complete, they should be able to use it.</div></div></div><div class="gmail_extra"><div class="gmail_extra"><div class="gmail_extra"><br>If your work is not 100% complete, it should be clear what's left to do.</div></div></div></blockquote><div class="gmail_extra"><div class="gmail_extra"><br></div><div class="gmail_extra">I am looking forward to the next .xo package, but it seems to me that the work will not be 100% complete, meaning that it will not be possible for a user to walk through the last user story we discussed on this list. </div><div class="gmail_extra"><br></div><div class="gmail_extra">The page also says for mentors: </div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div class="gmail_extra"><div class="gmail_extra"><br><div class="gmail_extra">Please help your student do a proper code submission. It's important to do this before the evaluation period.</div><div class="gmail_extra"><br></div>Check that…</div></div><div class="gmail_extra"><div class="gmail_extra"><br>* The submission meets the requirements above.</div></div><div class="gmail_extra"><div class="gmail_extra"><br>* The code compiles.</div></div><div class="gmail_extra"><div class="gmail_extra"><br>* There's documentation of what and why.</div></div><div class="gmail_extra"><div class="gmail_extra"><br>The idea of GSoC isn't that students churn out code -- it's important that the code be potentially useful to the hosting Open Source project.</div><div class="gmail_extra"><br></div></div></blockquote><div class="gmail_extra">Therefore I'd like to call a stop for coding after tomorrow's IRC meeting, and for you to focus 100% on code and project documentation for the final days of the GSOC job, so that it is clear what is left to do, and how the code you have written works. </div><div class="gmail_extra"><br></div></div><div class="gmail_extra">Cheers</div><div class="gmail_extra">Dave</div></div>