<div>Ahoy-hoy, about controller I'll review it with Daniel and security must to be revisited.
</div><div><br></div><div>Thank you! </div>
<div><div><br></div><div><br></div><div><div>-- </div><div>"The measure of a man is what he does with power" - Plato</div><div>-</div><div>@abstractj</div><div>-</div><div>Volenti Nihil Difficile</div></div></div>
<p style="color: #A0A0A8;">On Tuesday, October 9, 2012 at 8:40 AM, Matthias Wessendorf wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>Hi,</div><div><br></div><div>I did a review of some roadmaps before. here are some comments about</div><div>those that I have not yet reviewed:</div><div><br></div><div>* Connectivity:</div><div>zero content: I filed AEROGEAR-524 (see [1]) and assigned it myself,</div><div>to start defining it. (IMO this needs to be done immediately, after M6</div><div>is out).</div><div><br></div><div>* Controller:</div><div>The controller roadmap lists some requirements (taken from Doug's</div><div>blog) and a few use-cases. Currently it is not listing individual</div><div>milestones and/or CRs.</div><div>See <a href="http://aerogear.org/docs/planning/1.0.0/AeroGearController/">http://aerogear.org/docs/planning/1.0.0/AeroGearController/</a></div><div><br></div><div>* Persistence:</div><div>Similar to 'Connectivity' this is something that effects other</div><div>libraries. I like that it is structured into 'client' and 'server'</div><div>(same will apply to the 'Connectivity' roadmap), but it also does not</div><div>list individual milestones/CRs etc. Also some of the items (e.g. REST)</div><div>are already implemented in several AeroGear libraries. Other (e.g.</div><div>client validation) is mentioned in out roadmaps (e.g. the JS roadmap</div><div>has this item listed)</div><div><br></div><div>Question/Suggestion: Perhaps we spend a bit time about this roadmap in</div><div>today's meeting?</div><div><br></div><div>For details see <a href="http://aerogear.org/docs/planning/1.0.0/AeroGearPersistence/">http://aerogear.org/docs/planning/1.0.0/AeroGearPersistence/</a></div><div><br></div><div>* Security</div><div>Looks good, almost:</div><div>- iOS =>I need to define iOS specific things (see [2])</div><div>- android: lists OAuth - still right ?</div><div><br></div><div>Ah... one more thing: It talks about 'beta'. AFAIK these are</div><div>milestone(s), followed by CR, right ?</div><div><br></div><div><br></div><div>* UMBRELLA roadmap:</div><div>I guess this item is for Jay => <a href="https://issues.jboss.org/browse/AEROGEAR-521">https://issues.jboss.org/browse/AEROGEAR-521</a></div><div><br></div><div><br></div><div>Greetings,</div><div>Matthias</div><div><br></div><div><br></div><div>[1] <a href="https://issues.jboss.org/browse/AEROGEAR-524">https://issues.jboss.org/browse/AEROGEAR-524</a></div><div>[2] <a href="https://issues.jboss.org/browse/AEROGEAR-525">https://issues.jboss.org/browse/AEROGEAR-525</a></div><div><br></div><div>-- </div><div>Matthias Wessendorf</div><div><br></div><div>blog: <a href="http://matthiaswessendorf.wordpress.com">http://matthiaswessendorf.wordpress.com</a>/</div><div>sessions: <a href="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</a></div><div>twitter: <a href="http://twitter.com/mwessendorf">http://twitter.com/mwessendorf</a></div><div>_______________________________________________</div><div>aerogear-dev mailing list</div><div><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a></div><div><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>