17:03:45 <jzb> #startmeeting
17:03:45 <cs-meeting> Meeting started Wed Dec 5 17:03:45 2012 UTC. The chair is jzb. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:03:45 <cs-meeting> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:04:17 <jzb> #chair bhaisaab iswc kdamage ke4qqq noahnoahnoahnoah rajesh_battala_ serverchief1 topcloud u-ichi
17:04:17 <cs-meeting> Current chairs: bhaisaab iswc jzb kdamage ke4qqq noahnoahnoahnoah rajesh_battala_ serverchief1 topcloud u-ichi
17:04:35 <jzb> Howdy all, and welcome to the post-conference IRC meeting
17:05:16 <jzb> I hope everyone has caught up on sleep and such
17:05:25 <jzb> #chair jsm
17:05:25 <cs-meeting> Current chairs: bhaisaab iswc jsm jzb kdamage ke4qqq noahnoahnoahnoah rajesh_battala_ serverchief1 topcloud u-ichi
17:05:28 <Animesh> Yes,
17:05:43 <jzb> OK, as per usual, we'll go around the room in alpha order and see if anyone has anything to discuss or report
17:06:03 <jzb> #chair Animesh
17:06:03 <cs-meeting> Current chairs: Animesh bhaisaab iswc jsm jzb kdamage ke4qqq noahnoahnoahnoah rajesh_battala_ serverchief1 topcloud u-ichi
17:06:10 <jzb> Animesh: that means you're up 1st.
17:06:17 <jzb> Animesh: anything to discuss or report?
17:06:19 <Animesh> Yes
17:06:40 <jzb> #topic Animesh has the floor
17:06:54 <Animesh> I am intersted in taking forward one of the presentation in conference on securiy to make it generic
17:07:05 <Animesh> will start a thread on mailing list
17:07:06 <jzb> Animesh: ?
17:07:31 <Animesh> Thats all from my side
17:07:48 * bhaisaab on
17:07:57 * bhaisaab o/
17:08:36 <jzb> Animesh: OK
17:08:54 <jzb> #action Animesh to start a thread on security related to conference presentation
17:09:07 <jzb> bhaisaab: anything to discuss or report?
17:09:13 <bhaisaab> to report: Don't worry about it, to make cloudmonkey compatible with Python 2.5, sets was used.
17:09:22 <bhaisaab> ah, copy paste
17:09:30 <bhaisaab> to report: https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=shortlog;h=refs/heads/api_refactoring
17:09:41 <bhaisaab> on going work on api_refactoring branch
17:09:57 <bhaisaab> I'm moving pkgs to org.apache.cloudstack.api.{user,admin}
17:10:10 <bhaisaab> to discuss: sugggestions on the same
17:10:33 <jzb> #link https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=shortlog;h=refs/heads/api_refactoring
17:10:57 <bhaisaab> right now some classes are spread across cloud-server which should be in cloud-api, I want to do this because we want to refactor and separate api server from mgmt/core, run as a separate service
17:11:32 <bhaisaab> and eventually, api server would just translate/transfer requests/jobs for cloud-engine
17:11:39 <bhaisaab> any suggestions, flames?
17:11:50 <bhaisaab> that's all from my side
17:12:39 * bhaisaab ahem ahem, okay better wait for reply on thread on the ML
17:12:53 <jzb> bhaisaab: have you started a thread on the ML?
17:13:30 <bhaisaab> jzb: yes, http://markmail.org/thread/iim6atqn2mh6m7s2
17:13:58 <jzb> #link http://markmail.org/thread/iim6atqn2mh6m7s2
17:14:05 <jzb> bhaisaab: excellent.
17:14:07 <Animesh> bhaisaab: any update on name conflict of cloudmomkey
17:14:26 <bhaisaab> I've already moved all user level apis to org.apache.cloudstack.api in the api_refactoring branch
17:14:43 <bhaisaab> Animesh: I'm not going to bring this up, trademarks@a.o should handle this
17:15:01 <Animesh> ok
17:15:13 <bhaisaab> if you ask my stand on the issue, I would not want to rename the cli
17:15:26 <bhaisaab> *would->don't
17:15:40 <bhaisaab> alright, let's move on to iswc?
17:15:50 <jzb> sounds good
17:15:57 <jzb> iswc: anything to discuss or report?
17:16:44 <iswc> still recovering from my losses at the casino
17:17:09 <iswc> oh, sorry.. regarding the conference?
17:17:40 <jzb> iswc: anything regarding releases, etc. or the project
17:17:51 <jzb> iswc: Afraid there's not much we can do about your casino losses (smile)
17:17:57 <iswc> not yet, Kelcey and I are going to get back into document writing
17:18:09 <jzb> iswc: don't feel bad, I dropped a whole $24 on slots.
17:18:09 <kdamage> Yup
17:18:12 <iswc> we had some good conversations during the conference about it, but outside of that nothing new
17:18:18 <bhaisaab> iswc: cool, kdamage your book on cs?
17:18:32 <kdamage> And the publican stuff
17:18:42 <bhaisaab> cool
17:18:50 <jzb> iswc: OK, you or kdamage should feel free to ping me if you need any help with Publican or getting things committed to docs.
17:19:17 <jzb> moving on...
17:19:29 <jzb> jsm: welcome - anything to discuss or report?
17:19:38 <jsm> yes
17:19:55 <jsm> i'm here to talk about devcloud. i did a lot of work a couple of months ago cleaning up the work in tools/devcloud/. There was a lot of messy puppet work that was cleaned up, a lot of the rvm, ruby, gemset stuff cleaned up, and a cleaner way to build all the parts. devcloud as I see is built from three things: the base os vm, xen on top of that base os vm, and cloudstack on top of that vm.
17:20:11 <jsm> Right now, it appears that tools/devcloud is used to build the devcloud vm, and devcloud is built on the vm. But I thought a different approach would be interesting. What if we used devcloud as a proper Vagrant vm?
17:20:26 <jsm> what if we cd tools/devcloud and did a vagrant up and had a properly working Vagrant vm?
17:20:32 <jsm> and you deployed you code to it?
17:20:52 <kdamage> I like it!
17:20:58 <sebgoa> that was chipc 's concept
17:21:12 <bhaisaab> jsm: that is the idea, the problem is how to configure a vagrant box, I don't them both but planing to do something about it soon
17:21:28 <jsm> I've got the vagrant box configured
17:21:44 <bhaisaab> jsm: awesome, send patches already... wait but based off debian wheezy?
17:21:45 <jsm> right now it's still ubuntu 12.04, but I will switch to wheezy as per devcloud2 if necessary
17:22:04 <bhaisaab> jsm: not required if you can get it working, does it work for you?
17:22:21 <jsm> I had it working with a single nic before
17:22:27 <jsm> do we require 2 nics now?
17:22:35 <bhaisaab> jsm: another reason why I'm inclined towards debian is that they have a higher security and stability threshold unlike ubuntu
17:23:05 <bhaisaab> jsm: how would you make it possible to run multiple devcloud, you want a nic that can share network infra b/w vms and the host os
17:23:17 <bhaisaab> that's why host-only adapter was chosen and nat for internet for dom0
17:23:19 <jsm> also, it's quite a hefty patch because it obliterates most things that were in tools/devcloud
17:23:27 <jzb> bhaisaab: the downside w/Debian is a somewhat unpredictable release schedule. Maybe that doesn't matter so much on devcloud, though.
17:23:34 <jsm> bhaisaab: ok, that makes sense
17:23:36 <topcloud> the original intent for devcloud was two fold: 1. was a dev environment for developers. 2. a cloud in a box to quickly demonstrate cloudstack.
17:23:36 <bhaisaab> jsm: clean it up and send it (big grin)
17:23:47 <topcloud> does this work with #2?
17:24:00 <jsm> #2?
17:24:06 <topcloud> the second goal.
17:24:09 <bhaisaab> jzb: no the sched. may not be available but it's known that they would release around feb '13, like t
17:24:22 <bhaisaab> they did in feb '11 and feb '09 for last two releases
17:24:30 <bhaisaab> they are already in a code freeze since june/july
17:24:54 <jsm> so i guess my problem is i'll need assistance with a marvin config that will auto configure the devcloud instance
17:25:15 <bhaisaab> jsm: yes, we want both, #1 so developer won't have to change their workflow and #2 so a user/dev should be able to play with it, try out cloudstack
17:25:44 <sebgoa> have you tried the tools/devcloud/devcloud.cfg ?
17:25:45 <bhaisaab> jsm: don't worry about the marvin deployDatacenter stuff, that is for automatically deploying a basic zone, which one can do manually as well
17:26:08 <jsm> sebgoa: it seems to have changed since we last worked on it, but haven't tried it yet (smile)
17:26:23 <bhaisaab> oh, I forgot to share but I'd silently updated the wiki: https://cwiki.apache.org/CLOUDSTACK/devcloud.html
17:27:27 <jzb> #link https://cwiki.apache.org/CLOUDSTACK/devcloud.html
17:27:29 <jsm> ok, so one other part : as for my deliverable, i'll just have the new process for building devcloud… i won't have the ability to do the build locally and a rdeploy to the devcloud instance (that's beyond my scope of knowledge)
17:27:32 <jzb> #topic devcloud
17:27:53 <bhaisaab> what I can fix is viewee that creates a basic os, and vagrant to run it and puppet to install pkgs on it
17:28:03 <jsm> bhaisaab: i have done that work already
17:28:25 <bhaisaab> jsm: awesome, so share it already1
17:28:27 <bhaisaab> !
17:28:33 <sebgoa> jsm: why don't you send your patches and we check the vm it builds
17:28:49 <jsm> sebgoa: is it best to send patches or point to a fork ?
17:29:01 <sebgoa> patch
17:29:07 <bhaisaab> jsm: my question is does that work with host-only+nat, if not that was reason for devcloud2, otherwise there is not much difference between dc2 and dc1
17:29:17 <bhaisaab> jsm: patch on reviewboard
17:29:29 <bhaisaab> jsm: https://reviews.apache.org/account/login/?next_page=/dashboard/
17:29:31 <jzb> Might be good to have a branch for jsm's work
17:29:49 <jsm> bhaisaab: not yet, i will add that feature
17:29:54 <jsm> bhaisaab: if required
17:30:24 <bhaisaab> jsm: what you can do is fork the repo on github and share your branch with us, I too have a fork I work on: https://github.com/apache/incubator-cloudstack
17:30:30 <jsm> i apologize for the delay, i had a lot of this stuff done with a lot of sebgoa's help a couple of months ago, but then got yanked on another project
17:30:48 <bhaisaab> no worries, take your time
17:31:47 <jsm> ok cool, give me till COB on Friday
17:31:54 <jzb> jsm: we appreciate the work - no need to apologize! (smile)
17:31:58 <jsm> hopefully I'll have something up sooner
17:32:04 <jzb> jsm: anything else to discuss or report?
17:32:09 <jsm> that's all.
17:32:14 <jzb> jsm: thanks!
17:32:23 <jzb> OK, that means I'm up
17:32:32 <jzb> #topic 4.0.1
17:33:05 <bhaisaab> yeah, jzb status?
17:33:09 <jzb> I'm behind on 4.0.1 but I'm working on that today and tomorrow. I hope to be able to freeze by Friday.
17:34:04 <jzb> We have one blocker bug I'm trying to find the patches for
17:34:08 <topcloud> jzb: what do you think of the bug tracking process?
17:34:11 <jzb> CLOUDSTACK-560
17:34:20 <topcloud> has it been too burdensome?
17:34:39 <jzb> looks like that was fixed in CloudPlatform, but not pushed into CS
17:34:43 <jzb> topcloud: no - I think it's fine.
17:35:18 <topcloud> jzb: if that's the case, we should be able to find someone in citrix to cherry-pick it over.
17:35:18 <jzb> topcloud: we should definitely keep everything in Jira where possible.
17:36:03 <jzb> topcloud: Looks like Shweta committed it?
17:36:13 <jzb> topcloud: would be great if they'd submit a patch via ReviewBoard
17:36:16 <topcloud> animesh: can you take this?
17:36:49 <Animesh> Sure
17:37:19 <jzb> The only other thing I have right now is post-conference feedback
17:37:28 <jzb> #topic conference
17:37:52 <jzb> I overlooked creating feedback forms - I'm going to send out an email with a comment form to all conference attendees
17:38:09 <jzb> and also start a thread on the ML about the conference and what we can do better/ differently next time.
17:38:28 <bhaisaab> jzb: yes, also when can we see the videos/photos?
17:38:32 <jzb> #action jzb working on 4.0.1 to freeze by Friday
17:38:48 <jzb> #action jzb start discussion on conference / debrief on ML.
17:38:51 <kdamage> Second, videos
17:39:03 <jzb> bhaisaab: I've uploaded some photos already
17:39:11 <Animesh> jzb: when will the slides and videos from confernece made available
17:39:16 <jzb> http://dissociatedpress.net/uploads/CCC/
17:39:29 <sebgoa> slides at http://www.aarondelp.com/2012/12/links-to-everything-cloudstack.html
17:39:31 <jzb> Animesh: asked already, give me some time to type (wink)
17:39:40 <jzb> videos are going to take a bit longer
17:39:48 <jzb> we have 1TB of videos to edit + upload
17:40:09 <bhaisaab> jzb: yes, I saw them they were awesome; committers gangam style
17:40:26 <jzb> bhaisaab: I'll try to get the rest up sometime this week.
17:40:38 <jzb> I took a lot of shots. Not sure where the best place to post them all would be.
17:41:08 <bhaisaab> jzb: cool, looking forward to them all
17:41:09 <jzb> I wonder how Infra would feel about a 1GB photo archive on the CloudStack.org site ...
17:41:10 <bhaisaab> http://dissociatedpress.net/uploads/CCC/DSC_0467.jpg
17:41:21 <bhaisaab> 1TB?
17:41:40 <bhaisaab> why not share videos on youtube?
17:41:40 <jzb> bhaisaab: 1TB of video, about 1GB of decent photos
17:42:02 <bhaisaab> oh (big grin), photos-> minus.com, google+, flickr?
17:42:02 <jzb> bhaisaab: yeah, we'll put the videos on YouTube, I was talking about the photos
17:42:12 <rajesh_battala> Hi All, In India, we had a session on "Hacking Apache Cloudstack" at foss.in.
17:42:37 <jzb> bhaisaab: we'd need a paid account for Flickr for that many photos.
17:42:46 <bhaisaab> jzb: oh (big grin)
17:42:48 <jzb> Never heard of Minus.com... will look at that.
17:42:58 <jzb> anyway, I'll figure it out.
17:43:03 <sebgoa> jzb: dropbox folder ?
17:43:07 <kdamage> I can't host photo site... Unlimited bandwidth and storage
17:43:11 <bhaisaab> jzb: I used to do vlmc alpha releases on it
17:43:57 <jzb> we'll get 'em up.
17:43:59 <bhaisaab> jzb: for 1Gb I think you can host on your people.a.o account also, I've shared like 3-5G of devcloud, photos etc. on it
17:44:06 <jzb> OK
17:44:14 <jzb> bhaisaab: people.a.o - that's a great idea.
17:44:32 <jzb> Let me write up a quick script to ImageMagick thumbnails and pull together a gallery.
17:44:43 <bhaisaab> (smile) yeah, I hope they don't have any limits
17:44:44 <jzb> but that's probably the best idea.
17:44:47 <jzb> we'll find out (smile)
17:44:49 <bhaisaab> (big grin)
17:45:03 <jzb> I'll try to trim them a bit + cherry pick the best photos
17:45:09 <jzb> keep it to 500MB or so
17:45:18 <bhaisaab> jzb: alright can we move on, rajesh wanted to share somethin
17:45:30 <bhaisaab> jzb: no keep the original ones, 1G should be fine (smile)
17:45:31 <jzb> if anybody wants a REALLY high-res photo from the conference, email me + I'll send the RAW photo
17:45:46 <bhaisaab> *fine on people.a.o
17:45:49 <jzb> yeah, let's move on
17:45:55 <jzb> next up is kdamage
17:46:04 <kdamage> 2 things
17:46:24 <jzb> #action jzb put up conf photos on people.a.o
17:46:38 <rajesh_battala> I had uploaded few photos from foss.in conference https://picasaweb.google.com/113880250095401204688/ApacheCloudStackFoss2012?authuser=0&authkey=Gv1sRgCKHz-4fks4yd4QE&feat=directlink
17:47:04 <bhaisaab> rajesh_battala: if you can you'll have your turn, just saying (tongue)
17:47:07 <kdamage> I spoke with F5 this morning and they want to commit resources for me to document their Cloudstack product interactions.
17:47:36 <kdamage> So that hopefully will be comming to docs including autoscale
17:48:00 <jzb> kdamage: awesome!
17:48:24 <kdamage> Second: I'm a VMware Vancouver covered in Cloudstack clothing recruiting vendors to make CloudStack Vancouver happen!
17:48:32 <kdamage> At*
17:48:33 <topcloud> nice...who added autoscale for f5?
17:48:54 <kdamage> It's in process the F5 stuff
17:49:05 <bhaisaab> kewl
17:49:05 <topcloud> kdamage: you brave soul you!
17:49:44 <kdamage> So if I can pull off CloudStack Vancouver, you better all fly out here! (smile)
17:50:12 <bhaisaab> kdamage: send us the flight tickets (smile)
17:50:17 <kdamage> I'll keep the community posted on both.
17:50:32 <kdamage> Ask Citrix (smile) I will be, lol
17:50:45 <kdamage> That's all for this week
17:50:46 <sebgoa> kdamage: you want to talk about the transifex stuff ?
17:50:50 <topcloud> plan it close to a weekend so i can ski at whistler...none of these weekend conference at vegas crap...couldn't do anything after the conference.
17:51:07 <kdamage> sebgoa: Sure
17:51:22 <jzb> topcloud: you had energy after the conference to do anything?
17:51:26 <kdamage> topcloud: Of course
17:51:26 <jzb> obviously we're doing it wrong.
17:51:42 <topcloud> jzb: i didn't but wish i had
17:51:42 * jzb makes note to make topcloud party harder at next conference
17:51:52 <bhaisaab> (smile) kdamage
17:51:53 <topcloud> lol
17:51:57 <kdamage> Lol
17:52:02 <jzb> kdamage: anything else?
17:52:11 <kdamage> Nope, thanks
17:52:33 <bhaisaab> jzb: topcloud is kicka$$
17:52:35 <jzb> kdamage: thanks
17:52:40 <jzb> OK, next up
17:52:49 <jzb> ke4qqq: anything to discuss or report?
17:54:16 <jzb> OK, I guess we'll circle back to ke4qqq if he returns
17:54:24 <jzb> noahnoahnoahnoah: anything to discuss or report?
17:54:25 <kdamage> Brb
17:56:05 <bhaisaab> noahnoahnoahnoah: ping
17:56:08 <jzb> ok
17:56:09 <jzb> let's move on
17:56:19 <jzb> rajesh_battala: now it's your turn (smile)
17:56:25 <bhaisaab> rajesh_battala: foss.in stories please!
17:56:25 <noahnoahnoahnoah> jzb: nope
17:56:26 <noahnoahnoahnoah> sorry
17:56:31 <noahnoahnoahnoah> on a call at work sorry (smile)
17:56:32 <jzb> rajesh_battala: let's hear all about FOSS.in
17:56:39 <rajesh_battala> hi
17:56:45 <jzb> noahnoahnoahnoah: no worries. Enjoy the call.
17:56:57 <bhaisaab> lol, we can circle back?
17:57:03 <bhaisaab> rajesh_battala: hi, go ahead
17:57:04 <rajesh_battala> we had 3hours session "Hacking Apache CloudStack" at FOSS.in
17:57:22 <bhaisaab> rajesh_battala: devcloud worked fine for attendees?
17:57:25 <rajesh_battala> there was tremendous response esp from students
17:57:35 <bhaisaab> the best crowd ever (big grin)
17:57:45 <topcloud> jzb: that is one of the feedback i have for vegas conf. the hacking sessions are too short.
17:57:47 <rajesh_battala> 80 -90% of people were able to setup devcloud
17:58:04 <sebgoa> sweet
17:58:08 <bhaisaab> nice
17:58:10 <rajesh_battala> few people were having issues.
17:58:19 <bhaisaab> rajesh_battala: window guys, yes?
17:58:23 <bhaisaab> *windows
17:58:29 <rajesh_battala> but we solved them and cloudstack is up and running
17:58:41 <jzb> topcloud: yeah, I have heard that. We'll definitely address that next time.
17:58:45 <jzb> topcloud: thanks
17:58:48 <bhaisaab> rajesh_battala: cool, see any potential developers during the event?
17:58:51 <bhaisaab> or contributors
17:59:06 <rajesh_battala> most of them were on Windows , few on linux and mac
17:59:32 <kdamage> Windows FTW...
17:59:37 <bhaisaab> rajesh_battala: cool, write and share a blog about this
17:59:42 <rajesh_battala> ppl from Juniper, Cloudbyte, thoughtworks were interested to contribute to Cloudstack.
17:59:53 <bhaisaab> kdamage: lol, epic fail sometimes (make that many time (smile)
18:00:04 <bhaisaab> rajesh_battala: wow, awesome
18:00:19 <rajesh_battala> thoughtworks were interested to contribute to CS by adding Solaris zones
18:00:32 <jzb> that'd be interesting.
18:00:37 <rajesh_battala> Juniper were interested to contributed SDN
18:00:43 <bhaisaab> topcloud: a potential new contributor for a new hypv
18:00:52 <kdamage> Nice
18:00:57 <topcloud> nice
18:01:18 <bhaisaab> we gotta do the arch work, before they find out our existing code
18:01:24 <rajesh_battala> Cloudbyte people were trying to add their storage support to CS
18:01:47 <bhaisaab> nice
18:02:21 <bhaisaab> how many were they, people who attended the hacking session only?
18:02:27 <jzb> rajesh_battala: will you write up an event report?
18:02:42 <jzb> send it to -dev and or post on a blog?
18:02:47 <rajesh_battala> hands on session went for long time, few people stayed back even after conference to know more about devcloud and get their code up and running
18:02:56 <bhaisaab> rajesh_battala: write a blog and share link on ml ftw
18:03:00 <rajesh_battala> sure. will do that.
18:03:31 <bhaisaab> rajesh_battala: cool, glad the devcloud image worked
18:03:40 <jzb> rajesh_battala: awesomesauce
18:03:58 <rajesh_battala> jzb: thanks
18:04:01 <jzb> rajesh_battala: anything else we should cover ?
18:04:14 <sebgoa> rajesh_battala: can you have a look at https://issues.apache.org/jira/browse/CLOUDSTACK-308
18:04:23 <rajesh_battala> that's it from myside
18:04:34 <rajesh_battala> sebgoa: looking at it
18:04:37 <sebgoa> thanks
18:04:52 <jzb> thanks rajesh_battala !
18:04:59 <jzb> OK, next up...
18:05:06 <jzb> sebgoa: anything to discuss or report?
18:05:13 <sebgoa> couple things
18:05:24 <sebgoa> got a patch pending for awsapi docs https://reviews.apache.org/r/8237/
18:05:37 <rajesh_battala> sebgoa: will work on that to close it
18:05:40 <sebgoa> fixes quite a few things would be nice to get it looked at
18:06:33 <sebgoa> other thing is https://issues.apache.org/jira/browse/CLOUDSTACK-488 I am struggling with this
18:06:53 <sebgoa> there is thread with Likitha on ML, but I can't get it to work
18:08:03 <rajesh_battala> sebgoa: awsapi is not able to connect to db. db property is not set for awsapi project in the config properites.
18:08:21 <rajesh_battala> I discussed with likitha,
18:09:00 <sebgoa> rajesh_battala: would be nice if you could share step by step instructions to deploy awsapi from source code with maven
18:09:14 <rajesh_battala> ok sure.
18:09:26 <rajesh_battala> will write a wiki page for it.
18:09:45 <sebgoa> I did not update the ticket, I solved the db issue but ec2-service.properties does not get "loaded" during awsapi deployment
18:10:07 <sebgoa> ok thanks
18:10:22 <jzb> sebgoa: any other issues, topics?
18:10:32 <sebgoa> one last bit
18:10:39 <rajesh_battala> sebgoa: plz update ur investigation/fixes on that ticket.
18:10:44 <sebgoa> damage sent a patch for creating transifex file
18:10:59 <topcloud> i've gotta run everyone. i don't have anything to report.
18:11:11 <jzb> topcloud: thanks for joining
18:11:12 <sebgoa> I think we should have a policy that docs xml file should have less than 50 chars
18:11:27 <jzb> sebgoa: that would make very short documentation
18:11:29 <sebgoa> but I could be convinced otherwise
18:11:35 <sebgoa> th filename
18:11:38 <jzb> ah
18:11:39 <jzb> (smile)
18:11:53 <sebgoa> might solve docs issues though...
18:11:55 <jzb> sebgoa: do we have any that are > 50 now?
18:11:56 <sebgoa> (smile)
18:12:03 <sebgoa> 5 out of 444
18:12:07 <kdamage> sebgoa: Agreed
18:12:18 <jzb> heh
18:12:20 <sebgoa> if my count is right
18:12:41 <jzb> sebgoa: sounds like a rational thing to me - do you want to bring that up on the ML?
18:12:41 <kdamage> And chop+suffix makes for an ugly naming convention
18:12:59 <sebgoa> ok I will bring it up. would like to know what ke4qqq thought about it
18:13:16 <sebgoa> we could enforce that with a jenkins job....maybe
18:13:20 <jzb> I think he's indisposed
18:13:45 <sebgoa> ok I will bring it up as a DISCUSS
18:13:52 <sebgoa> that's it for me, thanks for listening
18:14:08 <jzb> #action sebgoa to bring up 50-character filename limit for XML/doc files on -dev ML
18:14:17 <sebgoa> filenames...
18:14:17 <jzb> sebgoa: do we have any limit for other filenames?
18:14:34 <sebgoa> jzb:don't know
18:14:40 <jzb> might be good to look at too
18:14:45 <sebgoa> k
18:15:01 <jzb> OK, let's move on
18:15:06 <kdamage> Ok so close my patch submission
18:15:06 <jzb> serverchief1: anything to discuss or report?
18:16:06 <sebgoa> kdamage: would be nice to see a patch that builds the translation with tx client…
18:16:22 <jzb> OK, moving on...
18:16:23 <kdamage> Ok lets discuss out of meeting
18:16:29 <jzb> sudhap: anything to discuss or report?
18:16:56 <sudhap> jzb: working on 401 install/upgrades
18:17:03 <sudhap> running in to some issues to make builds
18:17:08 <sudhap> will take it up in ML
18:17:13 <jzb> sudhap: OK
18:17:33 <jzb> sudhap: my first time doing rm duties, so feel free to grab me if there's anything I can do, OK?
18:17:48 <sudhap> will try to close it by monday - any pending defects would be validated
18:18:00 <sudhap> jzb: sure
18:18:13 <jzb> #action sudhap bring up 4.0.1-incubator install/upgrade issues on ML
18:18:17 <jzb> sudhap: thanks!
18:18:20 <jzb> OK
18:18:27 <jzb> u-ichi: welcome, anything to discuss or report?
18:19:43 <jzb> Ok, no response so I guess that's a no.
18:20:13 <jzb> we're about 20 minutes past the hour so unless anyone has a last-minute issue, I'm going to close the meeting
18:20:16 <jzb> going once...
18:20:23 <jzb> twice... (smile)
18:20:38 <jzb> OK, thanks everybody for turning up!
18:20:42 <jzb> #endmeeting

  • No labels