Hi All, 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. https://issues.jboss.org/browse/LIVEOAK-91 https://issues.jboss.org/browse/LIVEOAK-80 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).

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. Thoughts? Thanks, -Jay [1] https://github.com/hbons/aerogear-design/blob/master/ups-new-ux/applicati... _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

On Fri, Mar 28, 2014 at 5:11 PM, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: > Hello, > > > On Fri, Mar 28, 2014 at 4:40 PM, Jay Balunas <jbalunas(a)redhat.com&gt; wrote: > >> Hi All, >> >> 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. >> >> https://issues.jboss.org/browse/LIVEOAK-91 >> https://issues.jboss.org/browse/LIVEOAK-80 >> >> 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). >> > > > for the 'overall' work on doing the actual overhaul of the AdminUI for > the UnifiedPush Server, I created this JIRA/Epic already: > > https://issues.jboss.org/browse/AGPUSH-573 > > Not sure, but perhaps we can make the following tickets become epics as > well: > https://issues.jboss.org/browse/AGPUSH-575 > https://issues.jboss.org/browse/AGPUSH-576 > > where they have a bunch of sub-tasks. One sub-task per page. That would > give as an exact list of steps > +1 let's break that into smaller sub-tasks like : Application Screen / Variant Screen / Installation Screen / KC / Login Integration.

> > >> >> 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. >> >> Thoughts? >> > For sure, we have to be efficient here and reuse all what is possible. We must also keep a close eye on this project https://github.com/patternfly/angular-patternfly which will help us a lot to align with LO (since these angular directive will be the one extracted from the LO project)). > >> Thanks, >> -Jay >> >> [1] >> https://github.com/hbons/aerogear-design/blob/master/ups-new-ux/applicati... >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev