15:13:26 <mojavelinux> #startmeeting
15:13:38 <lightguard_jp> First item
15:13:39 <mojavelinux> #chair lightguard_jp
15:13:47 <lightguard_jp> #topic Follow-up with AI from last meeting
15:13:59 <lightguard_jp> First one up is for Brian
15:14:20 <lightguard_jp> Asking Jay about datatable integration
15:14:27 <lightguard_jp> bleathem: Any status?
15:14:32 <bleathem> no update
15:14:41 <lightguard_jp> Okay, we'll keep that for next week in that case
15:14:42 <bleathem> postpone till next week?
15:15:02 <lightguard_jp> #action bleathem Will talk to Jay about datatable export integration 
15:15:04 <lightguard_jp> Yep
15:15:11 <lightguard_jp> Next is for mojavelinux 
15:15:23 <lightguard_jp> definitions for Community integrator and forum moderator
15:15:47 <mojavelinux> Here's a draft of the community integrator and forum moderator definitions. Feel free to make changes. Once we get it settled, I'll throw them up on the wiki.
15:15:56 * bleathem *oh noes* minutes make us accountable!
15:16:06 <mojavelinux> Community Integrator
15:16:07 <mojavelinux> This volunteer role is bestowed upon a leading member of the Seam community outside of the core team (preferably not a Red Hat employee either). The person in this position has the authority to merge in pull requests at the direction of the module lead, which may also include reviewing and providing feedback on the patch. There are two reasons for having this role. The first is to keep the project moving during times when the core team is
15:16:07 <mojavelinux> best of the community, the community integrator has the option to drive inclusion the feature.
15:16:20 <lightguard_jp> bleathem: It does on my watch ;)
15:16:27 <bleathem> :D
15:16:36 <lightguard_jp> mojavelinux: Put those as #inf
15:16:40 <lightguard_jp> #info
15:16:42 <mojavelinux> oops
15:16:48 <mojavelinux> #info Community Integrator definition
15:16:53 <kenfinnigan> did we lose some of the end of that?
15:17:06 <mojavelinux> #info This volunteer role is bestowed upon a leading member of the Seam community outside of the core team (preferably not a Red Hat employee either). The person in this position has the authority to merge in pull requests at the direction of the module lead, which may also include reviewing and providing feedback on the patch.
15:17:09 <lightguard_jp> We don't have the bot so we're going to fake it
15:17:19 <mojavelinux> #info There are two reasons for having this role. The first is to keep the project moving during times when the core team is pulled away to work on urgent assignments, for instance to focus on productization or to participate in a conference.
15:17:26 <lightguard_jp> jose_freitas: Said he'd go through and parse them out :)
15:17:34 <mojavelinux> #info The second reason is to serve as an independent voice to represent the community perspective, providing a balance of power. In the event that the core team blocks a feature that is in the best of the community, the community integrator has the option to drive inclusion the feature.
15:17:42 <mojavelinux> I think that all came through
15:17:56 <lightguard_jp> Looks like it
15:18:25 <mojavelinux> I believe very much in that last sentence, and I think that's the most important part of keeping Seam strong
15:18:50 <mojavelinux> oops, except there is a grammar problem :)
15:18:52 <bleathem> agreed
15:18:59 <mojavelinux> missing "of"
15:19:08 <kenfinnigan> I like the definition, just a clarification on what is meant by "merge in pull requests at the direction of the module lead"?
15:19:19 <kenfinnigan> does it mean the lead needs to ok the integrator doing the merge?
15:19:51 <kenfinnigan> or is it the lead saying I'm going to be unable for a week, please merge any requests?
15:20:19 <jose_freitas> <o> lightguard_jp got my joke wrong! but I guess it won't be a big problem parsing it.
15:20:20 <lightguard_jp> requests will need to be reviewed by the lead, but if they can't get it, they'll let the integrator know
15:20:25 <mojavelinux> I can clarify it, but basically it means the module lead is ultimately the decision maker on a module; but can inform the integrator that the pull request is good to go, just logistics
15:20:36 <lightguard_jp> jose_freitas: Doh, sorry.
15:20:43 <kenfinnigan> ok
15:20:52 <mojavelinux> yeah, and the lead can also say, "I trust you to review any of them, even though I haven't reviewed them"
15:21:03 <jose_freitas> np, it wasnt a good joke anyway
15:21:20 <kenfinnigan> that makes sense, would create bottleneck with lead otherwise
15:21:23 <bleathem> I'd also think the integrator can infer from relevant jira issues if certain pull requests make sense
15:21:26 <mojavelinux> basically, the integrator can't just run away with the module
15:21:53 <mojavelinux> yeah, a quick e-mail to the lead should yield a +1 most likely
15:21:53 <jose_freitas> so, the community integrator should be aware of all seam code?
15:22:02 <jose_freitas> to evaluate pull requests/
15:22:16 <kenfinnigan> or develop that knowledge over time
15:22:23 <mojavelinux> right, what ken said
15:22:23 <jbossbot> git [core] push master 3380b3d.. Lincoln Baxter, III Help I'm stuck in a Git repository.
15:22:23 <jbossbot> git [core] push master URL: http://github.com/forge/core/compare/cc30e3d...3380b3d
15:22:32 <bleathem> lol
15:22:33 <kenfinnigan> I would imagine bleathem will go down as the holder of that role for the shortest period ever!
15:22:37 <mojavelinux> oh geez, there goes the vanity commit
15:22:44 <jose_freitas> hahaha
15:23:02 <bleathem> kenfinnigan: with zero pull requests evaluated (outside of faces)
15:23:24 <lightguard_jp> #info once the definitions are good we'll create a Doodle vote for the integrator and forum moderator
15:23:34 <mojavelinux> hahaha, well, that's the motivation for being good at your job, you only have to tolerate it for a short time :)
15:23:37 <mojavelinux> hehehe
15:23:44 <mojavelinux> okay, forum moderator
15:23:47 <bleathem> lightguard_jp: you missed the kenfinnigan nomination in the minutes posted from last week
15:23:58 <mojavelinux> #info Forum Moderator definition
15:24:09 <mojavelinux> #info This volunteer role is granted to an active participant in the Seam forums. The job is not intended to be time consuming, but it's certainly an important one. The person in this position monitors the forums on a regular basis (several times a week) to identify forum misconduct, recurring complaints and any other "disruption in the force".
15:24:20 <mojavelinux> #info The moderator has the authority to issue warnings to users that are abusing the forum policy. In the case of a widespread complaint, they should notify someone on the core team and, in the case there is a solution, point those users to that information. The moderator is not expected to respond to every post or be a general problem solver. Rather, this person is making sure that the forum is in good health.
15:24:24 <mojavelinux> again, last sentence most important
15:24:50 <kenfinnigan> like the term "disr+
15:24:52 <kenfinnigan> 96.08.+3
15:25:03 <kenfinnigan> sorry, 2yr old incident!
15:25:08 <lightguard_jp> bleathem: I remember
15:25:21 <bleathem> lightguard_jp: ok cool, jsut checking
15:25:33 <kenfinnigan> like the term "disruption in the force".  should we call them the "Forum Jedi"?
15:25:40 <bleathem> kenfinnigan: my 18 month old managed to eke out a tweet last week!
15:25:40 <mojavelinux> hahah, yes!
15:25:47 <lightguard_jp> brb
15:26:05 <mojavelinux> just wait until cats start tweeting
15:26:10 <mojavelinux> then we will really be in trouble :)
15:26:23 <kenfinnigan> you mean they haven't?! bit slow on the uptake
15:26:26 <mojavelinux> of course, the good thing about kids, when you say something that gets you in legal trouble
15:26:32 <mojavelinux> you just say "oh, that was my 2 year old"
15:26:41 <mojavelinux> yes, he knows that the JCP is corrupt :)
15:26:42 <mojavelinux> hahaha
15:26:46 <jose_freitas> ahhaha
15:26:52 <bleathem> I'm dropping Seam in favor of Spring
15:26:58 <bleathem> sorry, that was my two year old!!
15:27:02 <mojavelinux> hahaha
15:27:14 <lincolnthree> "YOU'RE NOT MY SON!"
15:27:19 <bleathem> lol
15:27:44 <mojavelinux> I often wonder if I would have like a no .NET policy if I had kids
15:27:46 <mojavelinux> I think I would
15:27:57 <mojavelinux> I already have a no Windows mandate in my marriage
15:27:59 <bleathem> like the jazoon video?
15:28:00 <kenfinnigan> definitely
15:28:19 <mojavelinux> as I said the other day, I've brought unity to the household
15:28:29 <mojavelinux> okay, Forum Moderator is Forum Jedi
15:28:35 <mojavelinux> let's go old sckol
15:29:26 <mojavelinux> the other motivation for the forum moderator is this
15:29:48 <lightguard_jp> back
15:30:07 <mojavelinux> by making someone feel like they have some control, instead what's going on with the forums, they can actually tell people what's going on
15:30:16 <mojavelinux> we need "people on the ground" so to speak
15:30:37 <mojavelinux> because forums have no been our strong suit :P
15:31:16 <mojavelinux> btw, to save yourself time fixing problems in the forum, try to persude people to write an Arquillian test to demostrate the issue
15:31:21 <mojavelinux> it will save you and them a ton of time
15:31:44 <mojavelinux> and we can immediately add it to the test suite if it ends up finding a bug
15:32:04 <lightguard_jp> True, it's a bit of a hard sell for some people though
15:32:12 <bleathem> speaking of which, I have to the the Seam Faces/JSFUnit/arquillina tests off the ground
15:32:22 <lightguard_jp> Awesome!
15:32:24 <mojavelinux> well, forge makes this a lot simpler
15:32:26 <lightguard_jp> Great news
15:32:28 <bleathem> if they had a template test to start with for wach of the modules, it would help
15:32:38 <bleathem> ^for each of the
15:32:49 <kenfinnigan> bleathem: good idea
15:33:13 <kenfinnigan> maybe each module could provide a "parent" arquillian helper to create the initial deployment with all the bits they need
15:33:16 <mojavelinux> yeah, this is another really good case for why quickstart is so important
15:33:24 <mojavelinux> you don't just start once, you are starting almost everyday
15:33:37 <mojavelinux> in one way or another, and often it's getting someone else started than it is getting you started
15:33:42 <mojavelinux> each forum question is a starting point
15:33:54 <kenfinnigan> quickstart?
15:34:17 <mojavelinux> i.e., new-project
15:34:23 <kenfinnigan> ah
15:34:34 <mojavelinux> because their question is about their project, not your project
15:34:44 <mojavelinux> so you have to create a new project to try to match what issue they are having
15:35:00 <mojavelinux> you and them referring to the two sides of a forum discussion
15:35:04 <kenfinnigan> gotcha.  yes that is a pain and time consuming
15:35:40 <mojavelinux> so give Paul's arquillian plugin for forge a try, and let people in the forum know
15:35:42 <lightguard_jp> Yep
15:35:48 <mojavelinux> perhaps we need a page "debugging a Seam problem"
15:36:03 <lightguard_jp> A sticky on the forums
15:36:21 <lightguard_jp> Would someone mind doing that, please?
15:36:26 <mojavelinux> #idea create a page for how to troubleshoot a Seam problem, from the perspective of a helper
15:36:34 <lightguard_jp> A quick post on the forums about creating an arquillian test for problems.
15:36:38 <mojavelinux> yep
15:37:02 <lightguard_jp> Too bad Paul's not here.
15:37:17 <lightguard_jp> lincolnthree: Tell Paul :)
15:37:46 <lightguard_jp> Do we all agree with those definitions?
15:37:47 <mojavelinux> I can also talk to Martin
15:37:53 <kenfinnigan> yes
15:37:55 <mojavelinux> who has been working on test coverage lately
15:38:04 <lightguard_jp> mojavelinux: Either one
15:38:37 <lightguard_jp> #action mojavelinux Will make the small changes and put up the definitions on the sfwk.org
15:38:38 <bleathem> I agree with the definitions
15:38:47 <lincolnthree> lightguard_jp: paul's at work
15:38:57 <lightguard_jp> lincolnthree: Drat, too bad.
15:39:11 <aslak> mojavelinux, maybe we need a forum extension.. "Download Arquillian Skeleton with [Seam Persistence] and [JBoss AS 6]" ;)
15:39:32 <lightguard_jp> After the definitions are up we'll create the Doodles, hopefully today or tomorrow they'll be out.
15:39:39 <lightguard_jp> #info After the definitions are up we'll create the Doodles, hopefully today or tomorrow they'll be out.
15:40:05 <lightguard_jp> Moving on in that case
15:40:16 <mojavelinux> aslak yes, this really fits into our vision that Arquillian becomes the template for troubleshooting
15:40:17 <lightguard_jp> #topic Leads becoming familiar with other modules
15:40:41 <lightguard_jp> We've mentioned in the past we're getting a little siloed in development.
15:40:46 <bleathem> +1
15:40:51 <lightguard_jp> I'm also seeing it on the forums with my own knowledge.
15:41:09 <kenfinnigan> what's the best way to achieve knowledge spread?
15:41:16 <mojavelinux> I have an idea
15:41:16 <lightguard_jp> I'd like to see each module lead getting involved (at least using) one or two other modules so we spread the knowledge.
15:41:47 <bleathem> We should have sprints dedicated to different modules every couple of weeks, where the module lead outlines goals, and an y devs interested contribute
15:42:08 <kenfinnigan> bleathem: i like that
15:42:23 <mojavelinux> what I think this comes down to is that we need more places to see them in use, in other words, another full fledged example application
15:42:24 <bleathem> or one a month, depending on dev availability
15:42:28 <mojavelinux> fortunately, we have one already
15:42:37 <mojavelinux> it just needs to be revived
15:42:45 <mojavelinux> where's jose? he's the example reviver
15:42:47 <kenfinnigan> the wiki?
15:42:49 <mojavelinux> the example medic
15:42:57 <mojavelinux> nope, ticketmonster
15:43:06 <kenfinnigan> ah, yes
15:43:17 <gastaldi> yo
15:43:25 <lightguard_jp> We'll also have SU but that seems to have fallen down a bit due to the webinar and Shane's vacation.
15:43:30 <kenfinnigan> that also has errai and infinispan doesn't it?
15:43:41 <lightguard_jp> ticketmonster?
15:43:45 <mojavelinux> I like the sprints idea too...actually, that kind of gets back to what we were suggesting a few weeks ago in terms of a round robin of releases
15:43:45 <kenfinnigan> yeah
15:44:04 <mojavelinux> I'll share the ticketmonster design doc with the team...actually, I might just post it to seam-dev
15:44:09 <kenfinnigan> I think TM has a JSF or GWT front end
15:44:11 <mojavelinux> and here is the github repo
15:44:18 <mojavelinux> the frontend is jquery
15:44:24 <lightguard_jp> I think it's actually in the seam org github
15:44:25 <jose_freitas> here mojavelinux
15:44:25 <mojavelinux> I think we may need a JSF frontend
15:44:35 <mojavelinux> jose revived the booking example :)
15:44:35 <bleathem> +1
15:44:43 <kenfinnigan> ok, must be thinking of another example app
15:44:44 <jose_freitas> I like the idea of using in SU
15:44:45 <mojavelinux> we have another one on life support
15:44:54 <mojavelinux> I could be wrong
15:44:57 <mojavelinux> i'm checking
15:45:00 <lightguard_jp> #info we will revive ticketmonster and get development going to use that as an example
15:45:21 <mojavelinux> https://github.com/seam/ticket-monster
15:45:22 <gastaldi> great
15:45:30 <lightguard_jp> #info development sprints are a good idea too, need more finalized ideas on this
15:45:36 <mojavelinux> yes, jsf ji
15:45:37 <mojavelinux> ui
15:46:04 <mojavelinux> wait, not!
15:46:05 <gastaldi> richfaces 4
15:46:06 <lightguard_jp> #info ticketmonster needs a JSF UI also for a nice example
15:46:13 <mojavelinux> hahaha, jsf is being used as a servlet
15:46:20 <mojavelinux> it's like jsp done with jsf
15:46:21 <mojavelinux> hahaha
15:46:24 <kenfinnigan> wow
15:46:31 <bleathem> ouch
15:47:01 <mojavelinux> that's like using a butcher knife to cut up an apple
15:47:02 <lightguard_jp> Dan, you and jose_freitas will work on getting that brought back to life?
15:47:15 <mojavelinux> the good news is, there may be even more resources
15:47:20 <mojavelinux> as this is a priority for AS 7
15:47:21 <mojavelinux> release
15:47:39 <mojavelinux> i'm going to try to find out who is being added to it, but it should be something that helps seam too
15:47:39 <lightguard_jp> Or at least you two can be the go to guys for info about it?
15:47:49 <mojavelinux> and it's a great chance for the team to learn about errai :)
15:48:01 <kenfinnigan> that would be nice
15:48:16 <mojavelinux> yeah, richfaces 4 too
15:48:27 <mojavelinux> so ticket monster has two UIs
15:48:33 <mojavelinux> it has an admin, backoffice UI
15:48:37 <mojavelinux> and a customer facing UI
15:48:44 <jose_freitas> hm
15:48:49 <mojavelinux> GWT for the first, bastardized JSF for the second
15:49:14 <gastaldi> lol
15:49:28 <mojavelinux> I think we should focus primarily on the JSF part, namely making it use RichFaces instead of custom javascript
15:49:36 <mojavelinux> I think shane pretty much hates JSF
15:49:37 <kenfinnigan> agreed
15:49:42 <mojavelinux> which is why it doesn't use anything from JSF
15:49:44 <lightguard_jp> Good idea. We can hash out the details offline.
15:49:46 <gastaldi> agreed
15:49:54 <jose_freitas> agreed
15:50:02 <mojavelinux> okay, next up
15:50:07 <lightguard_jp> #agreed we'll revive ticketmonster, fix up the JSF and use it as an example of Seam 3.
15:50:16 <mojavelinux> oh yes, just for reference https://github.com/seam/ticket-monster/blob/master/jsf-ui/src/main/webapp/viewevent.xhtml
15:50:16 <lightguard_jp> #topic Site / forum moderation
15:50:23 <mojavelinux> good opportunity for reports too!
15:50:32 <mojavelinux> ticket monster == ticket master clone
15:50:45 <mojavelinux> or as we say in the UI
15:50:47 <mojavelinux> US
15:50:50 <mojavelinux> ticket bastard
15:51:06 <lincolnthree2> And if you see places where forge could have helped. Keep track and file issues
15:51:10 <lightguard_jp> I'll Dan talk about this one as well, but we have something we're looking at and evaluating currently
15:51:13 <jose_freitas> we have a company here called exactly ticket monster
15:51:17 <jose_freitas> that do just that
15:51:26 <mojavelinux> hahaha
15:51:30 <jose_freitas> http://www.ticketmonster.com.br/
15:51:34 <mojavelinux> infringement!
15:51:47 <mojavelinux> I think we should call it ticket basdard
15:51:47 <gastaldi> lol
15:51:50 <mojavelinux> bastard
15:51:55 <mojavelinux> no one will take that name from us
15:51:55 <jose_freitas> lol
15:52:04 <mojavelinux> all in favor of ticket bastard :)
15:52:06 <gastaldi> better
15:52:11 <jose_freitas> agreed
15:52:16 <kenfinnigan> +1
15:52:23 * lightguard_jp so much for moving on *sigh*
15:52:26 <gastaldi> +1
15:52:41 <gastaldi> lol
15:52:47 <mojavelinux> sorry, I couldn't resist
15:53:12 <lightguard_jp> mojavelinux: At least you're in better spirits today
15:53:34 <gastaldi> ticket bastards it is !
15:53:41 <mojavelinux> hahah, yes
15:53:51 <jose_freitas> ticket bastards from hell
15:54:02 <gastaldi> haha
15:54:14 <lightguard_jp> Site / forum migration, take it away mojavelinux 
15:54:27 <mojavelinux> okay, after this tweet-like comment
15:54:43 <mojavelinux> ticketbastard has an twitter handle: Promoting non-Ticketmaster Venues, Shows, and Festivals because I hate fucking fees!
15:54:44 <mojavelinux> hahaha
15:54:52 <mojavelinux> we stand for no fees, just OSS
15:54:56 <mojavelinux> okay, migration
15:55:23 <mojavelinux> as we mentioned before, we are going to take a multi-phase approach to migration
15:55:39 <mojavelinux> the first, and most painful right now, is the project site (if you can separate that from the rest)
15:55:49 <mojavelinux> it sucks from a user standpoint, and editing it makes me want to stab myself
15:56:06 <mojavelinux> plus, there are two levels of access, no one and everyone
15:56:23 <gastaldi> haha
15:56:32 <mojavelinux> enough complaining, what are we doing about it
15:56:38 <jose_freitas> there're 10 levels of access, no one and everyone
15:56:50 <mojavelinux> well, jason is leading the charge to make sure this migration happens in this century
15:57:05 <mojavelinux> the first part is the site content, and here's our philosophy
15:57:11 <mojavelinux> jboss currently uses magnolia
15:57:26 <mojavelinux> that's like stabbing yourself in the eye and leg at the same time
15:57:37 <mojavelinux> if you can believe it, it's even harder than editing a page on sfwk.org
15:57:45 <mojavelinux> so that gets a no vote of confidence from me
15:57:54 * lightguard_jp thinks Dan has been seeing too many knives lately
15:58:02 <mojavelinux> I'm sort of stabby right now
15:58:33 <mojavelinux> long story short, there is this general shift toward git-based revisioning and publishing
15:58:34 <mojavelinux> I love it
15:58:38 <mojavelinux> I'm sure we all love it
15:58:48 <mojavelinux> because github is pretty much the end of stabbing
15:58:52 <gastaldi> what about confluence ?
15:59:03 <mojavelinux> consider this, though
15:59:09 <mojavelinux> before confluence, which I think makes ugly websites
15:59:17 <kenfinnigan> mojavelinux: something like the torquebox site?
15:59:22 <mojavelinux> you see the website, you want to make a change
15:59:31 <mojavelinux> so you edit the template and do a pull request
15:59:38 <mojavelinux> one click on github.com and it's live
15:59:44 <mojavelinux> and we have history
15:59:47 <mojavelinux> and we have collaboration
15:59:55 <lightguard_jp> kenfinnigan: yep, kinda like torquebox
16:00:00 <mojavelinux> now, what do we use to save typing
16:00:04 <mojavelinux> awestruct
16:00:08 <mojavelinux> is what we are evaluating
16:00:21 <lightguard_jp> It does the torquebox site
16:00:24 <mojavelinux> it was created by bob mcwhirter and team and is used to make torquebox.org
16:00:42 <mojavelinux> I would like to adopt the jboss community header, because I do want to feel integrated again
16:00:53 <bleathem> +1
16:00:53 <mojavelinux> but below that, we can have our own design
16:01:15 <kenfinnigan> +1
16:01:43 <mojavelinux> I would really like to host this on openshift, but i'm not stuck on the idea
16:01:54 <mojavelinux> if Mark Newton wants to do something else, you guys shouldn't even care or know
16:02:02 <mojavelinux> because it's all going to be managed via github
16:02:20 <mojavelinux> and that's even if we don't use awestruct, that is something that I think is just a no brainer
16:02:24 <jose_freitas> I'm traumatized with ruby app installations, I got really beated up by gitorious
16:02:27 <mojavelinux> git push live
16:02:44 <mojavelinux> awestruct is not a ruby app
16:02:50 <mojavelinux> well, let me say that another way
16:02:56 <mojavelinux> what gets pushed is a static html file
16:03:06 <jose_freitas> I thought that torquebox were
16:03:09 <mojavelinux> any dynamic bits (mashups) are done with jquery
16:03:16 <jose_freitas> ok
16:03:21 <mojavelinux> torquebox is, this is just what makes their site
16:03:42 <gastaldi> Nice
16:03:44 <mojavelinux> and we'll get some google analytics in there
16:03:46 <mojavelinux> gets some damn stats
16:03:51 <jose_freitas> :)
16:03:56 <mojavelinux> but here is why this is so important
16:03:59 <mojavelinux> if we did magnolia
16:04:10 <mojavelinux> the only people that could edit the site are the core team
16:04:18 <mojavelinux> and anyone who gets a magnolia login, but those are hard to get
16:04:20 <gastaldi> how are we going to template it ?
16:04:29 <mojavelinux> so we could share the credentials, but that is just closed crap
16:04:33 <--> edburns is now known as edburns_away
16:04:45 <lightguard_jp> gastaldi: We're still looking and seeing what we can do
16:04:50 <mojavelinux> awestruct is one option
16:04:54 <gastaldi> hum
16:05:06 <mojavelinux> we are open to suggestions as long as it fits into a git push based deployment
16:05:13 <bleathem> sounds good, when is work on this going to begin?
16:05:18 <mojavelinux> or, I should say, as long as the content can be managed in git
16:05:20 <mojavelinux> now
16:05:23 <bleathem> nice
16:05:31 <mojavelinux> we will have more news soon
16:05:36 <gastaldi> how about velocity ? :)
16:05:38 <jose_freitas> woot
16:05:42 <mojavelinux> right now we are just starting sorting out an approach
16:05:58 <mojavelinux> the forum migration will follow, but that won't be until next month at least
16:06:00 <gastaldi> nice
16:06:03 <mojavelinux> last thing, AS 7
16:06:09 <mojavelinux> so AS 7 is going to be a major release
16:06:22 <lightguard_jp> #topic AS7
16:06:41 <mojavelinux> major as in, this is a game changer for the java community
16:07:01 <mojavelinux> #info what the team is asking is whether Seam works on it
16:07:12 <mojavelinux> #info so, if you have tests, make sure AS 7 is one of the target containers
16:07:16 <mojavelinux> #info if you have examples, same thing
16:07:21 <mojavelinux> basically, play with it
16:07:37 <mojavelinux> #info we want to discover any issues now, whether they are on our side or in AS 7
16:07:54 <lightguard_jp> We need to add to the parent or any arquillian.xml (if you're current with Arquillian) an AS7 version
16:07:59 <lightguard_jp> That you can test locally.
16:08:08 <kenfinnigan> is the best version to use for testing the beta3 or something else that we build locally?
16:08:09 <lightguard_jp> It wouldn't run on the cloudbees infra though
16:08:11 <mojavelinux> AS 7 is actually moving quite fast, right now they taking time to sort out any stability issues
16:08:38 <mojavelinux> lightguard_jp: if we test locally for now, that's a step forward
16:08:41 <lightguard_jp> Do we have an AS7 embedded arquillian?
16:08:57 <mojavelinux> yes, it's now in Arquillian Beta1 (the containers will be updated very soon)
16:09:02 <mojavelinux> if you need help -> #jbosstesting
16:09:13 <mojavelinux> oh, no embedded
16:09:15 <mojavelinux> managed
16:09:19 <lightguard_jp> Darn
16:09:23 <mojavelinux> you don't want embedded
16:09:29 <lightguard_jp> embedded would run on cloudbees
16:09:33 <mojavelinux> ah
16:09:34 <lightguard_jp> That was the only reason
16:09:38 <mojavelinux> actually, that is a very intersting question
16:09:48 <mojavelinux> what if jboss modules could be used to start arquillian embedded
16:10:04 <mojavelinux> I'll see what the guys say about that
16:10:10 <mojavelinux> that might actually be our solution
16:10:26 <mojavelinux> so it would be like managed, but in process
16:10:30 <mojavelinux> best of both worlds
16:10:35 <lightguard_jp>  #action mojavelinux will follow up with arquillian embedded jboss modules
16:10:40 <gastaldi> cool
16:10:42 <lincolnthree2> That's not a bad idea. Copy me on that discussion would you?
16:10:47 <mojavelinux> will do
16:10:53 <lincolnthree2> thx
16:11:04 <mojavelinux> okay, that wraps it up
16:11:25 <mojavelinux> if you have any questions about AS 7, don't even hesitate to hit up the #jboss-dev channel
16:11:30 <bleathem> don't forget the #endmeeting
16:11:33 <bleathem> :P
16:11:34 <mojavelinux> seriously, input is super valued at this point
16:11:38 <mojavelinux> #endmeeting