Dimuthu, Bhargav... You probably noticed that as of 17th Jun (so I'm a bit late here myself) we entered the official GSOC2013 coding period.
Thank you both for your contributions on the JIRA ISIS-421 [1] for the RO viewer TCK tests ; there's clearly lots more to be done there, but hopefully in tackling some of those tests you've got a better handle on the RO spec. Now, though we've entered the official period of coding [2], [3], so it's time for you to start focusing on your actual projects. That also means that Google, and we, expect you to be putting in something like 40 hours a week on the project (rather than the 2~3 hours a week thus far). I'd like you both to follow a scrum-like approach, with weekly sprints running from Mon to Sun. That'll give me time each Sunday to check on progress etc. You probably know this already, but just in case... in Scrum, you need to maintain two lists of work items (stories). One is the product backlog - items identified but not in the current sprint. The second is the sprint backlog - items which you are working on in the current sprint. The sprint backlog should be fixed for the sprint/week; the completion of those items represents a project milestone. The product backlog will change over time though; in any given sprint you will likely find that new product backlog items are uncovered; you might also find that items on the product backlog get descoped, or removed as not needed. At the end of each sprint you should identify the next sprint's backlog ... Identify all the items still not done (either unfinished items from the previous sprint, or the product backlog), and prioritize them. Of the most important, determine which you think you can complete in the next sprint. Typically any items not completed in the previous sprint will carry over to the next sprint; but not always. What I would now like you to do is to *convert your original plans* (as documented in your respective wiki pages [4], [5]) into a *formal product backlog*. Don't put these into Isis' JIRA though - it's liable to flood it with items, some of which will never be implemented. As a lighter-weight alternative, could you create a google doc spreadsheet: if you search for "google docs product backlog template", there are plenty of examples that you could use as a starting point, if you want. For this forthcoming sprint* (w/c 24th Jun)*, I also want you to create a separate google doc *sprint backlog spreadsheet* for this forthcoming sprint, identifying your objectives for this coming week; in other words, the sprint's goal constitutes a project milestone. Again, you'll find a number of google doc templates to start from, if you want. At the end of the GSOC programme we should have 12 or so of these sprint spreadsheets, along with the (much updated by then) product backlog spreadsheet. If you have any vacation/holiday scheduled, then identify that on the sprint's backlog spreadsheet also. I'm not so bothered myself about sprint burndown charts or product burnup charts, but if you want to use a google doc template that generates these things, well, that'd be cool. For these google docs, please *share them with me and with Maurizio and Jeroen*. Also, as you create them, please link to them from your respective wiki pages [4], [5]. As well as updating your milestones, what I'd also like you is to update your wiki pages on a daily basis, with a *short daily status report*describing what you accomplished that day. Although we would never expect open source developers to do this, for you guys this is also paid work. (In fact, as you'll have realized, some of my own work on Isis is chargeable to a client, and I have to account for the time I charge on a daily basis also. So I think it's reasonable for me to ask you to do the same). And, could you also please also use your wiki page to *document any questions* or issues outstanding. Do also ask these questions on the dev@list, as well, of course. Dimuthu... I know you raised some questions already; I'll reply on that by separate email. Finally, until such time as the Isis PMC votes you in as committers (when we'll bring your code "in-house") can I ask that you make sure all work is in a *public github project*? Dimuthu: I know your code is on github already. Bhargav: where is the code you've written to date? Any questions or concerns, please reply on dev@. Otherwise, thanks guys, looking forward to seeing your projects come to fruition! Cheers Dan [1] https://issues.apache.org/jira/browse/ISIS-421 [2] http://community.apache.org/gsoc.html [3] http://www.google-melange.com/gsoc/events/google/gsoc2013 [4] https://cwiki.apache.org/confluence/display/ISIS/A+generic+%28Naked+Objects%29+Android+app%2C+to+run+against+Isis%27+Restful+Objects+interface [5] https://cwiki.apache.org/confluence/display/ISIS/Generic+Naked+Objects+app+in+JavaScript+for+Apache+ISIS
