[GSoC] 3P project reporting

[Bertrand Delacretaz <bd...@apache.org>]

Hi Petr,

On Wednesday, May 27, 2015, Petr Shypila <ik...@gmail.com> wrote:
> ...Just want to notify that I have updated my previous report..

Thanks very much, I have reviewed [1] now.

The idea with the 3P reports is a bit different: I'd like you to provide a
new report (Progress, Problems, Perspectives) every week, as a timeline of
what you did, and you don't modify them once they are entered. That creates
a useful trace of what you did, and can help other GSoC students or Sling
contributors see how you found your way into our codebase. It basically
writes the high-level history of your project.

You can either add those at the end of [1], or create a subpage for the
reports if you prefer.

For now I have reformatted your report there to reflect what I'd like to
see, and removed some parts that I felt were too detailed - the details
should be in the jira tickets as needed. But we aim for minimal, useful
reporting, let's not create more process than strictly needed.

Feel free to tweak/move it as appropriate of course in this phase of
defining how you're going to report.

In the problems section I see mostly technical questions, those should come
here, one thread per question. The 3P "problems" section is more for
high-level things like "the cat ate my router and I had no Internet for 2
days" or other big issues that prevent you from progressing.

Thanks very much for your work so far!
-Bertrand


[1]
https://cwiki.apache.org/confluence/display/SLING/GSoC+2015.+%5BSLING-1437%5D+Unit+and+Integration+tests