17:00:29 <jzb> #startmeeting
17:00:29 <cs-meeting> Meeting started Wed Jan 9 17:00:29 2013 UTC. The chair is jzb. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:29 <cs-meeting> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:00:53 <jzb> #chair chipc bhaisaab ke4qqq Noah noaresare pyr sebgoa serverchief1 u-ichi widodh
17:00:53 <cs-meeting> Current chairs: Noah bhaisaab chipc jzb ke4qqq noaresare pyr sebgoa serverchief1 u-ichi widodh
17:00:53 <noaresare> hello everyone, noa @ spotify here
17:01:02 <jzb> howdy noaresare
17:01:16 <serverchief1> hello
17:01:16 <jzb> for folks who are new to the meeting
17:01:17 <Noah> noaresare: you work for spotify?
17:01:26 <jzb> we go around the room in alpha order by nick
17:01:55 <jzb> if you have nothing to discuss, that's fine - just say so and we'll move on
17:02:06 <jzb> so let's get started
17:02:20 <jzb> bhaisaab: are you about? Anything to discuss or report this week?
17:03:07 <jzb> OK
17:03:14 <jzb> will circle back if bhaisaab joins
17:03:22 <jzb> chipc: I suspect you may have things to discuss or report 
17:03:27 <chipc> 4.1.0 stuff
17:03:43 <chipc> first, we are at serious risk of making anything close to what has been proposed
17:03:53 <chipc> we have 95 features / improvements proposed
17:04:03 <chipc> 62 are status Open
17:04:18 <chipc> which means that community members are either not updating like I have asked over and over
17:04:22 <chipc> or that they work has not started
17:04:24 <chipc> or both
17:04:31 <chipc> so status is difficult to judge
17:04:45 <chipc> I also have concerns about some specific community members being overcommitted
17:04:51 <chipc> in terms of number of features
17:05:03 <chipc> but I think that's a sub-concern to the overall scope
17:05:25 <jzb> #chair topcloud sudhap kdamage
17:05:25 <cs-meeting> Current chairs: Noah bhaisaab chipc jzb kdamage ke4qqq noaresare pyr sebgoa serverchief1 sudhap topcloud u-ichi widodh
17:05:31 <chipc> next: there are at least 7 features that were proposed for CloudStack, but appear to have already been built by Citrix for CloudPlatform
17:05:35 <Noah> chipc: does it matter if we're using time based releases?
17:05:50 <Noah> chipc: any features that are not ready don't make it in - simple as that
17:05:58 <chipc> Noah: no, except that I would expect that people are actually being realistic about what they think they can do
17:06:03 <chipc> so agreed
17:06:16 <chipc> ok, back to the feature development outside of the community problem
17:06:22 <Noah> its bound to be rough for a few cycles - but people will get used to it
17:06:27 <noaresare> chipc: I read that email about features built "outside the project". Why is this a problem?
17:06:51 <Noah> noaresare: because it fractures the community and forgoes oversight, input, etc
17:06:52 <chipc> because if the feature isn't built within the project, it's not part of the project without going through an IP clearance process
17:06:59 <chipc> plus what Noah just said
17:07:14 <noaresare> ok. agreed
17:07:18 <chipc> so for those features, ignoring the community issues, we have a legal obligation to confirm that they come in correctly
17:07:19 <Noah> things that are developed outside of the mailing lists tend to land in one big mamoth patch, which is no good
17:07:30 <serverchief1> chipc: because it was built by citrix - does it mean we cant use those features?
17:07:33 <chipc> I'm waiting for a representative of Citrix to propose the donations
17:07:44 <serverchief1> oh it remains to be seen
17:07:57 <chipc> there is a process to get them in, but at this point they have to be handled carefully
17:08:16 <chipc> and last - there are potentially some commits that I will be vetoing and reverting, re: the issue above
17:08:21 <chipc> where there was no discussion about the work
17:08:34 <Noah> wait, you're going to veto for lack of discussion?
17:08:55 <serverchief1> probably push back or revert would be a little better
17:08:59 <chipc> sorry, lack of discussion plus committed AFTER a commercial release from Citrix of that exact feature
17:09:14 <chipc> which means committed from a source outside the community
17:09:20 <Noah> so they are legally questionable?
17:09:26 <chipc> IMO, yes
17:09:29 <chipc> so with all that, I await someone from Citrix to own sorting this out…
17:09:30 <chipc> EOF
17:09:37 <Noah> okay - thats a more defensible reason for a veto
17:10:06 * ke4qqq is happy to see he isn't the only one tossing vetos
17:10:08 <chipc> Noah - lack of on-list discussion about a feature is just as important… but we can take that discussion onto the list or direct messages
17:10:18 <chipc> not hold up the meeting
17:10:27 <topcloud> chipc: so the concern is to go through the ip clearance process for those features right?
17:10:34 <Noah> yes, but much harder to be strict about - commit emails are, themselves, lazy consensus notifications
17:10:44 <Noah> we agree in broad strokes - happy to defer
17:10:50 <chipc> yeah, thx
17:10:50 <serverchief1> its a bit hard to keep track of everything on dev mailing list due to shear amount of emails
17:10:52 <chipc> topcloud: yes
17:11:00 <serverchief1> they may have been overlooked
17:11:22 <chipc> they have not been overlooked serverchief… unless someone can correct me
17:11:28 <chipc> I searched all over the place
17:11:29 <jzb> serverchief1: no doubt before vetoing the vetoer would search to be sure
17:11:33 <Noah> hmm. i can't remember where my propoposal to split the mailing list went
17:11:54 <topcloud> +1 to splitting the mailing list.
17:11:58 <serverchief1> +1
17:12:01 <topcloud> repropose
17:12:17 <ke4qqq> I don't think it stems the flow - you still have the same volume of mail
17:12:20 <kdamage> I just got my outlook rules working lol
17:12:21 <jzb> topcloud: that's been discussed on the list already
17:12:23 <chipc> topcloud: docs are problematic as well… we have docs being submitted for review BEFORE the feature is done in our repo
17:12:37 <topcloud> ke4qqq: it does for people who are only interested in one part.
17:12:43 <Noah> ke4qqq: it would allow people not interested in the JIRA firehose to ignore it, for eg
17:12:45 <topcloud> ke4qqq: it doesn't for us.
17:12:59 <jzb> Noah: that's what mail filters are for 
17:13:02 <ke4qqq> yeah - I agree, mine was a selfish outlook
17:13:17 <Noah> jzb: im for removing barriers to entering the community
17:13:32 <topcloud> jzb: imagine people with no server side filtering and reading these emails on their mobile phones.
17:13:53 <jzb> topcloud: there are a lot of ways to solve that problem
17:13:58 <topcloud> jzb: just the dings is enough to annoy the hell out of me.
17:14:12 <jzb> topcloud: e.g., use Gmail for apache mail
17:14:26 <jzb> but anyway - that's something that has been + can be discussed on the list
17:14:41 <jzb> chipc: anything else ?
17:14:45 <chipc> EOF
17:14:48 <ke4qqq> topcloud: you still let your phone ding? I thought we would have trained that out of you with our mail volume
17:15:01 <jzb> chipc: thanks
17:15:17 <topcloud> ke4qqq: imagine imagine. my filters are working 24x7
17:15:23 <topcloud> jzb: sorry to interrupt.
17:15:32 <topcloud> i just saw animesh joined.
17:15:41 <Noah> ill see if i can collect previous conversations about the mailing list thing and bring it up later on the lists
17:15:45 <jzb> #chair Animesh
17:15:45 <cs-meeting> Current chairs: Animesh Noah bhaisaab chipc jzb kdamage ke4qqq noaresare pyr sebgoa serverchief1 sudhap topcloud u-ichi widodh
17:15:55 <topcloud> animesh: i think you might have joined a little late but chipc was talking about the 7 features developed for 3.0.6
17:16:07 <Animesh> yes caught up in traffic
17:16:25 <topcloud> they need to go through the ip clearance. do you have an update on those?
17:16:35 <Animesh> ok I will check the log, are there any action items for me
17:17:07 <topcloud> yes....please continue...i'll send them to animesh.
17:17:07 <Animesh> No id dont' have update, let me review the log and get back later
17:17:35 <jzb> Animesh: would you be willing to take point on the 7 issues ?
17:17:39 <jzb> inside Citrix?
17:18:05 <Animesh> let me review the issues first, and I will follow up
17:18:22 <chipc> Animesh: thank you
17:18:39 <jzb> Animesh: did you have any issues to discuss or report?
17:18:47 <jzb> since we're on you already
17:19:15 <Animesh> Well I am planninf to follou up with Citrix engineers to report therir status on Apache jira every week
17:19:21 <chipc> thank you!
17:19:27 <jzb> woot
17:19:46 <topcloud> animesh: the thread on the issues are here: http://markmail.org/search/?q=cloudstack%3A+acs41+outside+from%3A%22Chip+Childers%22#query:cloudstack%3A%20acs41%20outside%20from%3A%22Chip%20Childers%22+page:1+mid:nu4f6tphsnsv7ls6+state:results
17:20:06 <Animesh> topcloud: thank you
17:21:00 <jzb> #link 4.1.0's 7 issues: http://markmail.org/thread/nu4f6tphsnsv7ls6
17:21:09 <jzb> Animesh: anything else?
17:21:19 * jzb (sort of like Carlin's 7 Dirty Words.)
17:21:43 <Animesh> No nothing else to report
17:22:17 <jzb> Animesh: thanks!
17:22:19 <jzb> OK,
17:22:24 <jzb> status report on 4.0.1
17:22:44 <jzb> We have one blocker bug (CLOUDSTACK-615) outstanding with no fix
17:23:16 <jzb> and one bug (CLOUDSTACK-605) that has a patch that's been awaiting review for about a month
17:23:42 <jzb> the fix for 605 looks simple enough so I'm going to apply that today
17:23:58 <jzb> it would be great if folks were reviewing these in a timely fashion, though
17:24:30 <jzb> We also still need to address upgrades - Alex raised an issue with the upgrade that Mice contributed
17:24:53 <jzb> See: http://markmail.org/thread/dpao2zhz566hkns7
17:25:08 <jzb> #link Do not retroactively change upgrade files http://markmail.org/thread/dpao2zhz566hkns7
17:25:37 <jzb> We need to fix this before a vote
17:25:41 <jzb> other than that, no issues
17:26:16 <ke4qqq> topcloud: is kelven available to look at 615?
17:26:38 <topcloud> ke4qqq: he's not here but i'll ask him.
17:26:47 <topcloud> when he gets in.
17:27:02 <ke4qqq> thanks!
17:27:09 <jzb> topcloud: you mean you all aren't in the office by 9 a.m. sharp every day?
17:27:16 * jzb is disillusioned
17:27:18 <jzb>
17:27:32 <jzb> kdamage: anything to discuss or report this week?
17:27:57 <kdamage> Just curious if there was any update on videos from CCC?
17:28:10 <jzb> kdamage: yes - I sent a note to -users and (I think) -dev
17:28:15 <jzb> they're going up, about 10 per day
17:28:19 <jzb> first batch went up yesterday
17:28:27 <serverchief1> how many in total?
17:28:28 <jzb> including chipc's
17:28:30 <kdamage> Can you repost the URL?
17:28:35 <jzb> kdamage: I can
17:28:42 <kdamage> I think I missed it, thanks
17:28:46 <kdamage> That's all
17:28:49 <jzb> kdamage: http://www.youtube.com/user/CloudStackCollab12
17:29:18 <jzb> we have some excellent public speakers in the project
17:29:43 <jzb> serverchief1: Not sure, 50+
17:29:58 <jzb> serverchief1: basically, all of the actual talks/keynotes
17:30:05 <serverchief1> jzb: awesome - the more - the better
17:30:10 <jzb> moving on…
17:30:16 <jzb> ke4qqq: anything to discuss or report?
17:30:23 <ke4qqq> a few things
17:30:43 <ke4qqq> just status stuff mainly: continuing to work on builds.a.o
17:30:50 <ke4qqq> several general builds/tests there
17:31:09 <ke4qqq> docs aren't working becuase the publican version is ancient
17:31:17 <ke4qqq> working on getting that updated
17:31:28 <jzb> ke4qqq: define "ancient"?
17:31:31 <ke4qqq> tsp has asked to add two external slaves, and we're trying to figure that out.
17:31:34 <jzb> and what version are you moving to?
17:31:35 <ke4qqq> publican 1.0
17:31:38 <ke4qqq> 2.8
17:31:43 <jzb> OK, yeah. That's ancient.
17:32:08 <ke4qqq> the builds@ folks were nice enough to install publican, but I wasn't specific enough about my needs.
17:32:50 <ke4qqq> I walked through almost 1/2 of the features for 4.1 in the past few days
17:33:19 <ke4qqq> and am somewhat concerned with scope - and especially some of the omnibus ones like 'make config more granular'
17:33:35 <jzb> ke4qqq: so - one of the bugs/features for 4.1 is improving the Publican output - how difficult is it going to be to change the Publican configuration on the build hosts?
17:33:49 <ke4qqq> jzb: easy
17:33:54 <jzb> oh, good.
17:33:55 <ke4qqq> we make it part of the brand
17:34:32 <ke4qqq> I personally am skeptical that it can all be accomplished in a timely manner - and topcloud one question (from a meddler)
17:35:26 <ke4qqq> is it possible to perhaps split up the javelin merge? Edison is talking about not using the storage stuff in the 4.1 timeframe, which has been keeping people at bay for working on things like sheepdog integration
17:35:51 <ke4qqq> and with that question I am EOF
17:36:26 <jzb> thanks ke4qqq
17:37:03 <jzb> topcloud: ?
17:37:41 <topcloud> none from me.
17:37:54 <jzb> topcloud: see ke4qqq's question above
17:37:56 <ke4qqq> topcloud: see my question to you
17:38:04 <ke4qqq> at :35
17:39:48 <jzb> OK, we'll circle back when topcloud catches up
17:39:55 <jzb> #chair mkochco
17:39:55 <cs-meeting> Current chairs: Animesh Noah bhaisaab chipc jzb kdamage ke4qqq mkochco noaresare pyr sebgoa serverchief1 sudhap topcloud u-ichi widodh
17:40:05 <jzb> mkochco: anything to discuss or report?
17:40:07 <topcloud> ke4qqq: i don't think edison is talking about not using storage stuff.
17:40:41 <topcloud> he's saying the same thing i was. which is that we will not switch cloudstack to use storage refactor until it works.
17:40:52 <topcloud> because we're not doing in place code changes to cloudstack.
17:41:04 <topcloud> i'll talk to him today.
17:41:22 <ke4qqq> topcloud: ok, the exchange with the basho folks I interpreted differently
17:41:45 <ke4qqq> as they were worried about the effects of the storage change on their S3 stuff.
17:43:26 <mmartinz> storage changes ? i feel a bit out-of-date
17:43:27 * widodh just got home
17:43:32 <topcloud> we'll take all of that in when we switch. basically if the existing code doesn't work, we can't switch....but framework needs to be in for us to even start on that.
17:43:35 <jzb> #chair widodh
17:43:35 <cs-meeting> Current chairs: Animesh Noah bhaisaab chipc jzb kdamage ke4qqq mkochco noaresare pyr sebgoa serverchief1 sudhap topcloud u-ichi widodh
17:43:39 <widodh> cooking dinner now, so probably won't make it in 15 min
17:43:46 <jzb> widodh: OK
17:43:54 <widodh> But I haven't got anything very special
17:43:56 <jzb> #chair mmartinz
17:43:56 <cs-meeting> Current chairs: Animesh Noah bhaisaab chipc jzb kdamage ke4qqq mkochco mmartinz noaresare pyr sebgoa serverchief1 sudhap topcloud u-ichi widodh
17:44:02 <Noah> jzb: i dont think you need to chair everyone like you do
17:44:11 <Noah> jzb: should be sufficient to have a single chair who's running the mtg
17:44:14 <widodh> I already mentioned on the ml that I'm working on the Ubuntu packaging
17:44:25 <jzb> Noah: it allows other people to "action" items, etc.
17:44:27 <Noah> jzb: at least thats how we do it for couchdb (as we stole the mtg idea. haha. thanks guys!)
17:44:32 <Noah> jzb: hmm, okay
17:44:39 <jzb> though it is underused
17:44:52 <jzb> OK, let's move on to mmartinz
17:44:58 <jzb> mmartinz: anything to discuss or report?
17:44:59 <ke4qqq> mmartinz: see Edison's relatively frequent updates on cloudstack-dev to get a sense of what is going on
17:47:07 <jzb> OK, I'll move on
17:47:10 <mmartinz> i came here a bit spontanous tbh , i got nothing to report, but if You are interested in adding MooseFS as storage i can send to someone info what needs to be altered in "shared mount point" to make it work
17:47:37 <jzb> mmartinz: thanks
17:47:51 <jzb> Noah: anything to discuss or report?
17:47:59 <Noah> jzb: nope! thanks
17:48:00 <Noah> oh, wait
17:48:06 <ke4qqq> mmartinz: I am sure folks would be interested - can you send that offer to cloudstack-dev@incubator.apache.org?
17:48:12 <Noah> i am back from a three week vacation - sorry for not communicating that properly
17:48:32 <Noah> that's it
17:48:46 <ke4qqq> Noah: status on IP Clearance stuff for the tests?
17:48:47 <jzb> Noah: we'll let it slip this time, but next time we're docking your pay
17:48:53 <Noah> jzb: hehe
17:49:16 <Noah> ke4qqq: chipc has re-started a thread about it on private@
17:49:24 <Noah> ke4qqq: im not caught up yet though
17:49:30 <chipc> Noah: I'l bring it to dev@ today
17:49:40 <chipc> I have a link to the actual artifact being donated
17:49:47 <chipc> and I have the XML file ready
17:49:53 <chipc> I'll let you run with it from there...
17:50:12 <chipc> #action: chip to get the test code donation discussion onto the dev list
17:50:35 <mmartinz> ke4qqq: ill try not to forget to do it tomorrow, this FS is quite useful, i use servers that give their storage to moosefs and ram/cpu to cloud itself pretty safe and reliable
17:51:01 <jzb> Noah: anything else?
17:51:07 <jzb> or anything else for Noah ?
17:51:39 <jzb> OK
17:51:44 <Noah> cool
17:51:45 <Animesh> Well can we get clarification on IP clearance for any bug fixes in 3.0.6
17:51:46 <Noah> sorry, no
17:52:03 <ke4qqq> Animesh: what clarification do you need?
17:52:48 <Animesh> noah: well my assumption is features developed outside of ASF repo need ip clearance, but what about bug fixes
17:53:03 <edison_cs> moring, guys
17:53:21 <Noah> Animesh: it's about size, not nature
17:53:31 <Noah> Animesh: a patch is fine - a 20k line patch is not so fine
17:53:49 <Animesh> noah: thanks for clarification
17:54:02 <Noah> same applies to commits - if a committer landed an entire feature in one commit, that is an issue
17:56:25 <jzb> noaresare: anything to discuss/report?
17:56:33 <noaresare> well, yes, a few things
17:56:43 <noaresare> first of all I would like to present myself somewhat
17:56:52 <chipc> noaresare: welcome
17:57:01 <chipc> happy to have you!
17:57:24 <noaresare> I'm Noa Resare, I work with the backend infrastructure team at Spotify and we have been moving slowly towards using cloudstack for our development VMs in the last months
17:57:53 <topcloud> noaresare: welcome
17:58:11 <noaresare> I've been trying to get us to prioritize being more visible in the cloudstack community and now it seems like I've gotten a few precious time slices to do just that
17:58:30 <ke4qqq> awesome!
17:58:33 <serverchief1> Noa - are you NYC based?
17:58:35 <noaresare> So, I'm going to spend some time working on the deb packaging and also go to the build a cloud day
17:58:43 <noaresare> serverchief1: nope, I work out of the stockholm office
17:58:55 <noaresare> (the one in Ghent, right next to Fosdem)
17:59:02 <serverchief1> i c
17:59:36 <noaresare> do, besides the packaging stuff I'll be looking at general release guidelines / testing etc stuff
17:59:47 <vogxn> noaresare: good to have you. welcome.
18:00:05 <edison_cs> noaresare: welcome!
18:00:13 <noaresare> since we're the team responsible for the continous integration, code review build environment at Spotify I'm kind of inclined to look harder at those parts
18:00:19 <sebgoa> noaresare: thanks for agreeing to come the build a cloud day in Ghent. cu there
18:00:20 <jzb> noaresare: welcome Anything else to talk about?
18:00:38 <topcloud> nosaresare: i buy anybody a beer if they get the packaging work sorted out.
18:00:43 <noaresare> not at the moment. I'll try to bring stuff up on the mail list as I encounter them
18:01:10 <noaresare> oh, one thing. me and widodh has started to work on a branch on github with the packaging stuff
18:01:16 <vogxn> noaresare: we'd love to see some CI action as well
18:01:30 <ke4qqq> vogxn: +1
18:01:34 <chipc> noaresare: the contributions you've already made are appreciated
18:01:46 <jzb> +1
18:01:56 <jzb> moving on
18:02:04 <jzb> pyr: anything to discuss or report?
18:03:46 <jzb> moving on
18:04:06 <topcloud> kelven will be on to talk about 615. what was the specific question? is it just to look at the bug?
18:04:10 <jzb> sebgoa: anything to discuss or report?
18:04:26 <sebgoa> Hi. Going through the apache committer info
18:04:34 <sebgoa> got connected to apache planet.
18:04:44 <sebgoa> I assigned cloud monkey docs to myself
18:04:52 <sebgoa> I will keep an eye on the marketplace thread
18:04:55 <sebgoa> that's about it
18:05:25 <ke4qqq> topcloud: yes, it's a blocker for the 4.0.1 release
18:05:31 <sebgoa> oh yeah…and organizing a build a cloud day in Ghent, Belgium Feb 1st. Register...
18:06:06 <jzb> sebgoa: cool - thanks!
18:06:30 <jzb> serverchief1: anything from you this week?
18:06:43 <serverchief1> hi, i'm ilya musayev - as on dev mailing list, i'm currently working on centos version of system offerings
18:06:56 <serverchief1> any thoughts on hosting it on sf.net?
18:07:10 <serverchief1> the templates
18:07:46 <serverchief1> apache maynot be a best fit as we are technically not distributing a source code
18:07:54 <serverchief1> as per chip
18:08:06 <ke4qqq> serverchief1: the previous discussion we had was that templates could be hosted on asf infra - with the understanding it would be a convenience binary, but not a release....but that was an informal discussion at OSCON with some of the wise folks in power at the ASF.
18:08:30 <serverchief1> ok.. so apache could be ok with hosting it?
18:09:33 <ke4qqq> serverchief1: may - we'll need to ask for permission
18:09:59 <serverchief1> ok.. we can sort this out later, i'm hoping to get the centos version of system offerings completed this week, just need to ask chiradeep few questions
18:10:01 <ke4qqq> but other projects have binaries that contain forbidden items
18:10:09 <ke4qqq> serverchief1: awesome!
18:10:34 <serverchief1> if anyone is NYC local, we are thinking of hosting cloudstack meetup
18:10:35 <jzb> serverchief1: thanks
18:10:54 <serverchief1> pending my employer ok for use of facility
18:10:57 <serverchief1> EOF
18:11:09 <jzb> serverchief1: I may know someone who'd like to help with that
18:11:29 <jzb> sudhap: anything to discuss or report?
18:12:15 <sudhap> I went over QA tasks for new features. I am reviewing them even though ke4qqq and chipc have created them
18:12:37 <sudhap> also started to get builds done for master
18:12:54 <chipc> has to go for a bit
18:13:01 <sudhap> going successfully for time being - will be reporting obvious failures
18:13:36 <sudhap> couple of engineers would like to help with automation setup and running tests as we do that internally
18:13:51 <sudhap> they need guidence though
18:14:03 <ke4qqq> guidance on what?
18:14:07 <jzb> sudhap: have they spoken up on-list?
18:14:28 <sudhap> not yet - but will be doing that soon
18:14:52 <vogxn> sudhap: we have our automated setup running already on jenkins.a.o. is the proposal different?
18:15:18 <sudhap> no - they may not be familar with asf infra and set up done
18:15:43 <vogxn> the infra is actually within citrix and only reports go to asf. i will put up a wiki and TODO tasks on this
18:15:45 <sudhap> that is the guidence they need
18:16:00 <vogxn> pls ask the engineers to speak up on list and i am happy to guide them
18:16:12 <sudhap> vogxn: that would be great
18:16:15 <ke4qqq> vogxn: can you make sure that it's documented well enough for someone else to replicate
18:16:33 <vogxn> ke4qqq: i will. i've been sitting on it. sorry about that
18:16:48 <ke4qqq> awesome
18:16:55 <sudhap> for time being we are running builds and setting up automation internally
18:17:03 <sudhap> for ASF Master sanity
18:17:20 <vogxn> sudhap: i'm doing the same for asf. better to not duplicate efforts?
18:18:18 <edison_cs> +vogxn
18:18:24 <edison_cs> +1, vogxn
18:18:40 <edison_cs> better to just use one automate system
18:18:49 <sudhap> vogxn: it will get repurposed to future releases so not sure if that can be used or not
18:19:02 <sudhap> iedison_cs: if there is a way to do that I am all for it
18:19:17 <vogxn> sudhap: let's take it to the lists and work it out.
18:19:34 <sudhap> vogxn: sure
18:20:02 <sudhap> I assume that test code IP clearance is in progress
18:20:13 <vogxn> yes. working on it. will talk about it on my turn
18:20:17 <sudhap> That is also something that we need
18:20:43 <sudhap> second topic is regarding the feature set for 41
18:21:15 <sudhap> I am worried that on Jan 31st lot of features with questionable quality might get on to master
18:21:52 <chipc> comes back
18:22:41 <ke4qqq> sudhap: I expect testing to be in place before things get merged, and for tests to by and large pass - much like Alex et al, are doing with javelin
18:22:44 <jzb> sudhap: any in particular?
18:23:07 <chipc> jzb: probably all of them that come in near the end
18:23:12 <chipc> but it's hard to predict
18:23:28 <chipc> ke4qqq: that's the right approach
18:23:38 <jzb> chipc: as a former writer, I always felt that the closer to deadline, the better it was
18:23:45 <chipc> ha
18:23:57 <chipc> and as a developer, I'd agree… by my QA team wouldn't
18:24:02 <jzb> fair enough
18:24:09 <jzb> sudhap: any other issues?
18:24:19 <ke4qqq> and I expect that we'll see a few vetos on code that doesn't meet those expectations
18:24:51 <chipc> ke4qqq: want to take an action to remind people about it? I've already done so, but no acks so it might require reinforcement
18:25:19 <ke4qqq> sure I'll do so shortly.
18:25:41 <jzb> OK, I guess that was it for sudhap
18:25:56 <jzb> topcloud: did you say you have nothing this week, or was that someone else?
18:26:48 <chipc> sudhap: since you're back… did you have meeting notes from the QA meeting yesterday to post to the list?
18:27:14 <sudhap> chipc: sorry not yet - will do it today
18:27:17 <chipc> thx
18:27:23 <ke4qqq> bah - missed that meeting 
18:27:24 <topcloud> jzb: nothing...what i have i posted to the list.
18:27:41 <jzb> sudhap: have you been announcing the QA meetings to the list?
18:27:50 <sudhap> jzb: yes
18:27:58 <jzb> sudhap: cool.
18:28:00 <jzb> thanks
18:28:07 <chipc> #action ke4qqq to remind the community about feature quality expectations prior to master branch merge
18:28:17 <chipc> #action sudhap to email out QA meeting minutes
18:28:17 <jzb> chipc: thanks
18:28:35 <jzb> u-ichi: anything to discuss or report this week?
18:29:56 <jzb> Moving on
18:30:06 <jzb> vogxn: anything to discuss or report this week?
18:30:18 <vogxn> yes - working on a few things this week.
18:30:44 <vogxn> 1. seen couple of minor isssues on master after the merge of api_refactoring. looking to run our smoke tests on it before javelin comes in
18:31:12 <vogxn> 2. since packaging is WIP and our CI tests depend on it. I've broken out hte packaging and running from source so as to get tests going
18:31:32 <vogxn> 3. to add some more fang to the tests i'l working to get in some tests through IP clearance so i can run them
18:31:58 <vogxn> 4. #action item from last week for follow up with infra on moving our CI to builds.a.o still pending on me
18:31:59 <ke4qqq> vogxn: are there reports for those tests?
18:32:12 <vogxn> ke4qqq: i will setup the reports via jenkins
18:32:17 <vogxn> and share with the lists
18:32:34 <ke4qqq> vogxn: I pinged gmcdonald about the issue - he's concerned about how to have those slaves added securely, stilling pondering
18:32:40 <ke4qqq> vogxn: to commits@?
18:32:58 <vogxn> ke4qqq: haven't enabled email . but can do. not a big deal
18:33:25 <vogxn> there's many more things in my head - but will probably bring them up for next week's meeting
18:33:34 <vogxn> as i won't get through those this week
18:33:40 <vogxn> ah and yes -document our CI
18:34:23 <vogxn> that's it for now
18:34:27 <jzb> vogxn: thanks
18:34:43 <jzb> #action vogxn follow up with infra on moving our CI to builds.a.o still pending on me
18:35:03 <jzb> widodh: have you made it back? I think it's been more than 15 minutes
18:35:09 <widodh> jzb
18:35:16 <widodh> yes, just finished dinner, pff
18:35:24 <jzb> widodh: hope it was tasty
18:35:33 <widodh> yep
18:35:35 <kdamage_> this might be a record length meeting
18:35:51 <widodh> Nothing special to report, noaresare already mentioned we have started work on the Ubuntu packaging
18:36:07 <widodh> this will also flow back to the RPM packaging since it shares a lot with the DEB packaging
18:36:23 <widodh> That was actually it for now
18:36:36 <jzb> widodh: awesome, thanks
18:36:39 <jzb> OK
18:36:46 <jzb> did we miss anyone?
18:37:15 <noaresare> I can just mention that I got 11 new proper machines provisioned today, so now we have somewhere to test the 4.1 packaging effort
18:37:25 <jzb> noaresare: groovy
18:37:30 <jzb> OK folks
18:37:40 <jzb> that's a wrap - thanks for joining + have a great week
18:37:45 <jzb> #endmeeting
Overview
Content Tools
Apps