14:03:18 <balunasj> #startmeeting
14:03:19 <jbott> Meeting started Tue Mar 13 14:03:18 2012 UTC.  The chair is balunasj. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:03:19 <jbott> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:03:39 <balunasj> #chair kborchers qmx|away abstractj
14:03:39 <jbott> Current chairs: abstractj balunasj kborchers qmx|away
14:03:49 <balunasj> abstractj: have you used meetbot before?
14:04:01 <abstractj> balunasj: not really
14:04:04 <balunasj> #topic agenda
14:04:08 <balunasj> #link https://github.com/aerogear/collateral/blob/master/mtg-notes/20120313-team-mtg-agenda.md
14:04:41 <balunasj> abstractj: no worries - you can use #info to get something in the minutes, or #link to post of link, or #action to take or give an action etc...
14:04:58 <abstractj> cool
14:04:59 <balunasj> Then at the end meetbot spits out the minutes
14:05:18 <balunasj> we keep previous minutes here https://community.jboss.org/wiki/AeroGearTeamMeetingMinutes
14:05:19 <abstractj> I saw in the latest meeting
14:05:34 <balunasj> abstractj: ah thats right
14:05:47 <balunasj> #topic abstractj joins the team officially
14:05:54 <kborchers> \o/
14:05:57 <balunasj> :-)
14:05:59 <abstractj> yay!
14:06:49 <balunasj> abstractj: Glad to have you - hopefully you'll be more productive than that bum qmx|away ;-)
14:07:10 <abstractj> lol
14:07:10 * balunasj picks on people when their not here - jk
14:07:29 <balunasj> #topic M2c Reelase
14:07:46 <balunasj> #info remaining issues :
14:07:49 <balunasj> #link https://issues.jboss.org/browse/AEROGEAR/fixforversion/12319253
14:08:06 <balunasj> For the most part all that is left is release wrap up.
14:08:20 <balunasj> qmx|away: pushed the bits last night!
14:08:44 <balunasj> kborchers: is wrapping up jboss-as/quickstart sync
14:08:57 <balunasj> abstractj: ping me later if you want to discuss how these things fit together
14:08:57 <kborchers> https://github.com/kborchers/quickstart/commit/4d78bda3a78be6ce868fb9971b6108cef44eed7a
14:08:58 <jbossbot> git [quickstart] 4d78bda.. kborchers Merging 1.0.0.M2c from aerogear/as-quickstarts
14:09:13 <balunasj> kborchers: nice
14:09:32 <balunasj> I'm wrapping up the release blog
14:09:48 <balunasj> and abstractj is tackling the openshift update
14:10:16 <balunasj> kborchers: I may have you take a look at the wiki updates as well so I can get to the M3 forum stuff
14:10:29 <kborchers> balunasj: how many openshift specific changes are in the hosted repo?
14:10:43 <kborchers> analytics, table reset, etc.
14:10:48 <balunasj> kborchers: Not too many - google analytics, table reset
14:10:56 <balunasj> that is pretty much it
14:11:09 <kborchers> i wonder if it would be easier to just keep a list of what needs to change somewhere
14:11:21 <kborchers> then just branch the quickstart, make the changes and push to openshif
14:11:24 <kborchers> openshift*
14:11:31 <kborchers> rather than have a separate repo
14:11:41 <balunasj> kborchers: I'd like to keep it private though
14:11:47 <kborchers> right
14:11:57 <kborchers> you don't have to push the branch public
14:11:57 <balunasj> Here are all the changes https://github.com/aerogear/hosted-kitchensink/commits/master
14:12:02 <kborchers> just branch locally
14:12:12 <kborchers> push to openshift and then you can kill the branch
14:12:16 <kborchers> never goes public
14:12:40 <balunasj> kborchers: Wouldn't that make it hard to share those changes and keep in a central spot?
14:13:23 <kborchers> not sure what you mean
14:13:59 <balunasj> kborchers: Well, if we just keep the changes local, then there might be something that I change that you don't when I do it next time
14:14:09 <balunasj> so it is not really centralized
14:14:45 <balunasj> kborchers: I'm not against your idea, but would prefer to keep it in the hosted repo if we can get the workflow to be easier
14:15:14 <kborchers> right, that's why i said just keep a list of what needs to change somewhere that is up to date. just think it would be easier to make a couple of openshift specific changes rather than trying to merge all of our quickstart changes into the hosted repo.
14:15:21 <balunasj> kborchers: there are also some icon changes, but they should be in the quickstart proper as well.
14:15:29 * balunasj I think there is a jira already for that
14:16:35 <balunasj> kborchers: that could work out
14:16:58 <balunasj> abstractj: qmx|away: any thoughts on this?
14:17:07 <balunasj> I know abstractj was just thrown into the mix :-)
14:17:33 <abstractj> I have a question. Currently to have the latest release of quickstarts we always do it manually into hosted-kitchensink?
14:17:39 <kborchers> and this is qmx|away http://whatshouldwecallme.tumblr.com/post/18994691910/my-life
14:18:01 <balunasj> ROTFL!!!
14:18:30 * abstractj thinks that kborchers have the best pics ever
14:18:33 <balunasj> abstractj: yes, but to be fair this is the first time we've merged
14:18:51 <balunasj> when we did this for M1 it was the first release
14:19:20 <kborchers> balunasj: abstractj another option would be to add the quickstarts as a remote ...
14:19:23 <kborchers> then
14:19:37 <kborchers> create a branch in hosted
14:19:43 <abstractj> balunasj: got it. So we need to do it again in AEROGEAR-153? Right? Sync the private repo with latest changes...
14:19:44 <jbossbot> jira [AEROGEAR-153] Update Openshift with latest version of the quickstart [Open (Unresolved) Sub-task, Major, Bruno Oliveira] https://issues.jboss.org/browse/AEROGEAR-153
14:19:54 <kborchers> set that branch to the current tag of the remote
14:20:20 <kborchers> then manually do the openshift changes to that branch and push to openshift
14:20:25 <abstractj> I would like to do it automagically as kborchers said
14:20:35 <kborchers> then master has the original changes to reference
14:20:44 <balunasj> kborchers: abstractj: The requirements in my mind are that the hosted changes be private ( mostly just for the analytics), centralized change set, and easy workflow both for updating and pushing to openshift.
14:20:57 <kborchers> and the branch could be named after the tag and pushed to openshift so we know what is what
14:21:00 <balunasj> how we do this I don't feel strongly about.
14:21:19 <kborchers> balunasj: did you see that last string of thoughts
14:21:27 <balunasj> kborchers: reading now
14:21:53 <abstractj> balunasj: if we can't be public with analytics stuffs, I believe that's the best alternative
14:22:40 <balunasj> kborchers: So hosted repo would have as-quickstart as a remote - right
14:22:47 <kborchers> yes
14:23:01 <balunasj> abstractj: leaning that way as well
14:23:06 <kborchers> although
14:23:16 <balunasj> kborchers: the only gotcha that I can see is that the git root is different
14:23:19 <kborchers> we still have the issue of all of the other stuff in that repo
14:23:25 <kborchers> yep
14:23:33 <balunasj> openshift assumes git root == app root
14:23:36 <jfuerth> g'morning, AeroGear
14:23:37 <kborchers> yep
14:23:46 <balunasj> jfuerth: Hello!
14:23:52 <kborchers> morning jfuerth :)
14:23:55 <jfuerth> have you guys seen my CDI mobile deviceorientation demo yet?
14:23:56 <jfuerth> http://html5orientation-jfuerth.rhcloud.com/errai-cdi-mobile-demo-2.0-SNAPSHOT/
14:24:01 <abstractj> jfuerth: morning!
14:24:20 <balunasj> jfuerth: nope - can you post a link - we're in our team meeting right now.
14:24:30 <jfuerth> try it in chrome on mac or android ICS or iPhone/iPad2
14:24:34 <balunasj> jfuerth: or we discuss at the end of the meeting if that is ok?
14:24:48 <jfuerth> balunasj: oh, sorry didn't mean to interrups
14:24:51 <jfuerth> carry on :)
14:24:54 <balunasj> jfuerth: no worreis
14:25:30 <balunasj> abstractj: jfuerth is our resident gwt/errai expert and a good guy in general - but don't tell him - ok
14:25:44 <abstractj> lol jfuerth mp
14:25:45 <jfuerth> :P
14:26:41 <balunasj> kborchers: abstractj: perhaps something with git sub-tree's would work - but I don't anything about them, and want to keep this simple
14:26:41 <kborchers> balunasj: that's exactly what i was trying the other day for an hour and couldn't get it to work right
14:27:00 <kborchers> thus, these other crazy ideas i'm trying to come up with  :P
14:27:24 <abstractj> balunasj: kborchers my suggestion is move forward with simple, I'll try to figure out how to do the magic
14:27:49 <balunasj> abstractj: +1 was just going to suggest having a fresh set of eyes on it and we'll see what happens
14:29:02 <balunasj> So other than that - and the other smaller release items we're good for M2c
14:29:17 <abstractj> balunas: I believe that's a tricky magic, but will make us healthy
14:29:27 <balunasj> abstractj: :-)
14:29:30 * kborchers can finally see M3 in the distance
14:29:44 * kborchers knocks on wood
14:29:52 <balunasj> kborchers: qmx|away abstractj: agreed and something we've been pushing for!
14:30:06 <balunasj> lets shift to M3 then
14:30:08 <abstractj> kborchers: yay! I'm on this plane
14:30:25 <balunasj> #topic M3 Planning
14:30:51 <balunasj> #info M3 planning was delayed because M2b, M2c, travel, etc...
14:31:06 <balunasj> #info But it should be time to get back to it.
14:31:29 <balunasj> #info jira link
14:31:37 <balunasj> #link https://issues.jboss.org/browse/AEROGEAR/fixforversion/12318676
14:32:04 <balunasj> I've done some minor updates here, but the real task I need to do is get the M3 planning forum post up as promised
14:32:47 <balunasj> abstractj: M3 is where we should finally be past the intial "we just launched" crazies, and working to get quickstarts updated.
14:33:46 <balunasj> M3 is where we want to start focusing on things like more advanced examples, and things like hybrid applications with cordova.
14:34:24 <balunasj> This is also where some things like the security research and initial mvc investigation qmx|away has been working on comes in.
14:34:55 <abstractj> cool. Will we start to discuss about security and another modules to aerogear?
14:35:02 <balunasj> I'd like to plan for M3 to be 6 weeks from now.
14:35:23 <balunasj> abstractj: exactly, and how we can get project, and community feedback
14:35:30 <balunasj> etc...
14:36:03 <balunasj> abstractj: there will ofcoarse be some updates like bugs, site, wiki updates as well
14:36:17 <abstractj> cool. I was reading outh specs and I would like to share some ideas this week
14:36:52 <balunasj> abstractj: I would love to read your thoughts.
14:37:11 <balunasj> abstractj: For things like this I think the dev forums are critical to allow others to review and discuss.
14:37:35 <abstractj> balunasj: you're reading my mind!
14:37:39 <balunasj> Also there is some updated for the quickstart that kborchers is going to be working with marius on.
14:37:40 <abstractj> qmx: morning sunshine!
14:37:47 <balunasj> qmx: morning
14:38:00 <balunasj> need to share kborchers reference for qmx
14:38:01 <balunasj> http://whatshouldwecallme.tumblr.com/post/18994691910/my-life
14:38:08 <abstractj> ROFL
14:38:17 <kborchers> balunasj: so are we thinking 4/24 M3 or the fri before 4/20 or fri after 4/27 or mon 4/23?
14:38:18 <balunasj> :-)
14:38:31 <qmx> morning!
14:38:32 <aerobot> qmx: kborchers @ 14:03:34 GMT+0000 (UTC) said: http://whatshouldwecallme.tumblr.com/post/18994691910/my-life
14:38:43 <kborchers> thanks aerobot
14:38:53 <qmx> LOL
14:39:10 <balunasj> kborchers: this is where I need to make sure we are in sync with other expectations from WFK/Tools side.
14:39:16 <kborchers> ok
14:39:23 <qmx> balunasj: did the meeting start early? on my calendar I have 20 minutes for it to start :(
14:39:28 <balunasj> kborchers: I think we can plan for 6 wks and I'll get it confirmed.
14:39:34 <kborchers> TIME CHANGE!
14:39:43 <balunasj> qmx: I think with the time change it messed up for you
14:40:06 * balunasj screamming at congress for passing the stupid changes a few years back....
14:40:13 <kborchers> thank you pointless DST
14:40:42 <kborchers> sure glad all of us farmers have the extra time to get our crops planted/harvested
14:40:43 <abstractj> qmx: I'll keep you updated with the best news. Bruno joined the team officially!
14:41:14 <balunasj> qmx: you have not missed much - I updated them on M2c, and welcomed Bruno :-), and then discussed openshift hosted changes which abstractj are going to work on today.
14:41:29 <balunasj> qmx: we were just starting to talk about M3 planning
14:41:42 <balunasj> qmx: and here is the rough agenda for today https://github.com/aerogear/collateral/blob/master/mtg-notes/20120313-team-mtg-agenda.md
14:42:06 <balunasj> #action balunasj Complete the jira review for M3
14:42:22 <balunasj> #action balunasj Complete the M3 planning forum post - today
14:42:43 <balunasj> #action abstractj Post security ideas in dev forums
14:43:11 <balunasj> #action qmx Post MVC thoughts/updates in dev forums
14:43:32 <balunasj> #action kborchers Sync with marius on M3 quickstart
14:44:05 <kborchers> balunasj: marius is mbg in here (not here presently) right?
14:44:18 <balunasj> #action balunasj Email jboss-as group about limiting impact of quickstarts and perhaps on changing the requirments for M3 quickstart updates
14:44:31 * balunasj wow that was a vomit of actions....
14:44:35 <balunasj> kborchers: yup
14:44:40 <kborchers> thanks
14:44:44 * qmx just read the logs, tired
14:44:46 <qmx> :P
14:45:03 <qmx> abstractj: welcome to the team, MF!
14:45:17 <abstractj> qmx: thanks my friend!
14:45:18 <qmx> balunasj: and MF means my friend, of course :)
14:45:30 <balunasj> Figured :-)
14:45:44 <kborchers> i read it the other way and it still worked fine for me :P
14:45:59 <abstractj> qmx: depends on my mood!
14:46:12 <qmx> kborchers: that's the idea
14:46:14 <qmx> :)
14:46:17 <kborchers> lol
14:46:33 <balunasj> LOL
14:46:55 <balunasj> kborchers: The last action for me - may impact the work for M3 quickstart updates
14:48:02 * kborchers ignores balunasj's last action and pushes forward :P
14:48:09 <qmx> balunasj++ for splitting us from the jbossas quickstarts
14:48:09 <aerobot> balunasj leveled up! (Karma: 6)
14:48:34 <balunasj> qmx: Agreed and I told rodney yesterday about my concerns.
14:48:53 <balunasj> kborchers: keep looking that is fine, but don't push to far without checking back.
14:49:22 <kborchers> balunasj: it was more of a dream than an actual action ... don't like redoing work so i will hold back
14:49:23 <balunasj> I'd rather have us working on an AeroGear specific example than keep pushing the quickstart ( which may start to not be a quickstart)
14:49:39 <kborchers> #agreed
14:49:45 <qmx> #agreed
14:49:51 <abstractj> #agreed
14:50:46 <balunasj> so that is my main action - trying to get some separation.  There is some minimum
14:51:18 <balunasj> work we need to do, but I no longer think we should be pushing to be first at XYZ with the quickstart.  It burned us twice.
14:51:22 <balunasj> so good.
14:51:37 <balunasj> Anything else before we break the meeting
14:51:42 <balunasj> #topic Open
14:51:52 <balunasj> jfuerth: You had something right?
14:51:59 <balunasj> anyone else is open too
14:52:46 <balunasj> I'll end the meeting and we can take anyting else offline
14:52:48 <balunasj> #endmeeting