<div dir="ltr">Hello,<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 28, 2014 at 4:40 PM, Jay Balunas <span dir="ltr"><<a href="mailto:jbalunas@redhat.com" target="_blank">jbalunas@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word">Hi All,<div><br></div><div>
After talking with Thomas about how liveoak has been working I think their approach to tracking there work there is a good approach. Take a look at these jira's for an example. </div><div><br></div><div><div><a href="https://issues.jboss.org/browse/LIVEOAK-91" target="_blank">https://issues.jboss.org/browse/LIVEOAK-91</a></div>
<div><a href="https://issues.jboss.org/browse/LIVEOAK-80" target="_blank">https://issues.jboss.org/browse/LIVEOAK-80</a></div></div><div><br></div><div>Is this something we could do for our upcoming console and tech migration efforts? This will also make it a lot easier for us to judge where we are, and what work is left. Especially when we have assistance from others (such as some on the LiveOak team). </div>
</div></blockquote><div><br></div><div><br></div><div>for the 'overall' work on doing the actual overhaul of the AdminUI for the UnifiedPush Server, I created this JIRA/Epic already:</div><div><br></div><div><a href="https://issues.jboss.org/browse/AGPUSH-573">https://issues.jboss.org/browse/AGPUSH-573</a><br>
</div><div><br></div><div>Not sure, but perhaps we can make the following tickets become epics as well:</div><div><a href="https://issues.jboss.org/browse/AGPUSH-575">https://issues.jboss.org/browse/AGPUSH-575</a></div><div>
<a href="https://issues.jboss.org/browse/AGPUSH-576">https://issues.jboss.org/browse/AGPUSH-576</a></div><div><br></div><div>where they have a bunch of sub-tasks. One sub-task per page. That would give as an exact list of steps</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word">
<div><br></div><div>Another area that Thomas and I talked about was the UX/HTML/CSS reviews and reuse. The updated mockups from Hylke [1] are obviously quite similar to LiveOak's console. There should be quite a bit of overlap with core HTML and CSS that should make it easier for Hylke to produce what we need. Any help that Gabriel will be able to assist, advise, and review which should help a lot.</div>
<div><br></div><div>Thoughts?</div><div><br></div><div>Thanks,</div><div>-Jay</div><div><br></div><div>[1] <a href="https://github.com/hbons/aerogear-design/blob/master/ups-new-ux/application-details-blue.png" target="_blank">https://github.com/hbons/aerogear-design/blob/master/ups-new-ux/application-details-blue.png</a></div>
</div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>