20:01:18 <rbergeron> #startmeeting Cloud SIG
20:01:18 <zodbot> Meeting started Thu Jun 24 20:01:18 2010 UTC.  The chair is rbergeron. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:01:18 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:01:29 <rbergeron> #meetingname Cloud SIG meeting
20:01:29 <zodbot> The meeting name has been set to 'cloud_sig_meeting'
20:02:11 <rbergeron> Hey folks. Anyone around?
20:02:17 <jeevan_ullas> yes.
20:02:18 * ke4qqq is here
20:02:26 * jeevan_ullas is here
20:02:44 <ke4qqq> jforbes: ??
20:03:00 * rbergeron wonders if jforbes is at summit...
20:03:06 <ke4qqq> Oxf13: ??
20:03:16 <jforbes> Sorry, here, just got back from vacation today and still playing catchup
20:03:21 <rbergeron> oh ;)
20:03:26 <rbergeron> #chair jforbes
20:03:26 <zodbot> Current chairs: jforbes rbergeron
20:03:31 <jforbes> Wow, there are people here, no one has showed for the last 2 weeks :)
20:03:37 * ke4qqq wonders if we should pingall
20:03:39 <rbergeron> yes, we're recruiting. :)
20:03:55 <ke4qqq> yeah - lets change that
20:03:57 * gholms|work takes a seat in the bleachers
20:03:59 <jforbes> #topic status
20:04:05 <jforbes> #topic kernel status
20:04:35 <jforbes> So we have the patches required for the kernels to work committed to fedora CVS and they should make the next kernel update, we are kinda stuck until then
20:04:47 <ke4qqq> timeline on that?
20:05:16 <jforbes> next kernel pushed... not sure when, just got back from a week of vacation and still playing catchup
20:05:53 <ke4qqq> whats the plan once that push occurs?? is someone on the hook to push kernel images up?
20:06:30 <smooge> ok if people can wait 10 minutes I will start up as infrastructure looks short because of RHsummit
20:06:56 <rbergeron> smooge - awesome, thank you sir :)
20:07:00 <rbergeron> smooge - we already started
20:07:33 * ke4qqq really wishes this was in -meeting or -meeting-1 so there were more eyes on it, but that's future
20:08:27 <rbergeron> jforbes: so - i don't mean to come in and commandeer or anything here or start barraging you with questions - but I'm from marketing, so i'm not the most technical person on earth -
20:08:28 <jforbes> Teah, I am on the hook to push the kernel when ready
20:08:37 <rbergeron> but am interested in figuring out what is going on here
20:09:00 <rbergeron> helping where I can - and i'm trying to find like... meeting agenda... to-do list other than what's on http://fedoraproject.org/wiki/Features/FedoraOnEC2
20:09:07 <rbergeron> I'm curious if I'm missing anything
20:09:15 <rbergeron> (not to derail your current topic, of course)
20:09:45 <jforbes> rbergeron: Well, we are kind of in a holding pattern waiting on the kernel, I usually push an email with agenda call on the meeting day, but just got back and didn't catch up yet
20:09:46 <Oxf13> sorry I'm here now.
20:10:16 <rbergeron> ah.
20:10:27 <rbergeron> So - is there a to-do list once the kernel business gets sorted out?
20:10:37 <jforbes> And you haven't seen any notes on the wiki because no one has showe dup for a meeting for the past 2 weeks
20:11:05 <jforbes> Next step after the kernel is getting F13 images created and pushed, huff was working on that kickstart...
20:11:11 <jforbes> huff: you here ?
20:11:15 <ke4qqq> sooooo what about AMI stuff - can that be done in parallel?
20:11:29 <huff> jforbes: yes im here
20:11:36 <rbergeron> jforbes: hopefully we can change that (people showing up) :)
20:11:41 <ke4qqq> already done? (/me hasn't made it through all the meeting minutes yet, so I am behind)
20:11:46 <huff> so I have a RHEL6 image should be easy to convirt to f13
20:12:00 <huff> do we have any requiremnts in terms of feture sets
20:12:10 <huff> or package's for that matter
20:12:13 <jforbes> huff: Great.  I think on feature set we are lookiing for minimal
20:12:20 * ke4qqq thought the idea was for a simple webserver - pretty minimal
20:12:40 <jforbes> Like what we were doing with F12... small and simple that people can build on
20:12:45 <huff> k
20:12:51 <rbergeron> Can we get feature set documented on wiki?
20:12:56 <huff> ill post somthign to the list tomrrow
20:13:09 <ke4qqq> and link to ks?
20:13:20 <huff> ke4qqq: sure thing
20:13:39 <ke4qqq> awesome!
20:14:32 <ke4qqq> soooo this didn't make the F12 or F13 feature list - does it need to be resubmitted - or perhaps a better question - assuming we drag some new victims^H^H^H^ volunteers - what can they do to move this along?
20:15:14 <jforbes> Well, everything is held up by kernel, but once that is done we can start with more folks doing image testing, ks tuning, etc
20:15:20 <rbergeron> #action huff to post AMI feature set to mailing list
20:15:34 <rbergeron> jforbes: can we actually start figuring out what those line items are - start recruiting people to do that stuff?
20:15:54 <gholms|work> ke4qqq: It has to go back before fesco
20:15:58 <ke4qqq> and more importantly - how do we do image testing - do we need to purchase a block of EC2 accounts?
20:16:19 <ke4qqq> gholms|work: I guess my question is, do we care enough about it to do the work, and do we need to find an owner for that chunk of work
20:16:25 <huff> i think we should work with amazon to do the testing
20:16:33 <huff> they are doing some of it on the rhel side
20:16:36 <rbergeron> ke4qqq: i think that's part of "let's figure out the line item list of what we need to do" - anything we have questions about, we can figure out mystery items now
20:16:49 <rbergeron> so we're ready to go when kernel stuff is ready.
20:16:51 <huff> not sure who has the contacts since gdk left
20:17:06 <jforbes> rbergeron: Well, we need to test and tune the image, and we need to come up with a process to make sure that this is a simple and repeatable process that releng can use for F14
20:17:11 <ke4qqq> gdk is reachable if no one else has the contacts
20:17:23 <jforbes> huff: I have them
20:17:44 <jforbes> huff: they did some kernel testing for us as well, so we know the patch is good
20:17:51 <huff> cool
20:18:04 <huff> they were talking about large scale testing
20:18:08 <rbergeron> jforbes: can we make a list in the wiki - so that people who want to get involved know what work there is to do - how they contribute - etc
20:18:13 <ke4qqq> ok, so we need to document how people can test - and should we see if QA will setup a TestDay to get more people involved?
20:18:15 <huff> ie spin up 300-400 instances
20:18:23 <huff> to make sure they test on all possiable hosts
20:18:33 <rbergeron> and i mean more list-y than "we need to test and tune" - even if it's that we need to brainstorm that stuff and sort it out later?
20:19:15 <jforbes> We need to see about that.  not sure if we can do a test day without making the people pay to run the instance
20:19:31 <ke4qqq> we can purchase a block of ec2 accounts, that doesn't worry me so much
20:20:24 <jforbes> But yes, we can get some detailed plans on the wiki.  I will email the list for feedback on the plan tomorrow
20:20:43 <rbergeron> ke4qqq: how much does that run?
20:21:08 <rbergeron> or anyone... what would a block of accounts cost?
20:21:12 <ke4qqq> rbergeron: insignificant comparatively
20:21:20 <imcleod> There's no startup cost, only hourly.
20:21:32 <imcleod> Cheapest instances are 0.08 USD per hour
20:21:38 <rbergeron> yes - i mean a block of accounts for a test day
20:21:55 <jforbes> Yeah, but you can't run the cheapest instances for 64bit
20:22:02 <imcleod> true
20:22:09 <jforbes> rbergeron: the problem is giving out credentials to people for accoutns
20:22:45 <gholms|work> You can use spot instances for cheaper rates.
20:22:46 <jforbes> rbergeron: anyone with credentials for an account can run whatever they want there.  There is no prepay, it's a bill you later kinda thing
20:23:21 <rbergeron> soooo - if we are doing a test day - that's a day - could we not set up a block of generically-named account that are valid for a day?
20:23:34 <rbergeron> if we want to circumvent the "i'm hosting the universe for my friendz on amazon" situation :)
20:23:57 <jforbes> rbergeron: right
20:23:58 <gholms|work> We'd need a way to kill all the instances afterward, but that sounds like the best way to do it.
20:24:07 <rbergeron> I just have to think that we're not the only people facing this situation :)
20:24:29 <rbergeron> If we're the only ones wondering how to test without giving out blanket access to host music libraries
20:24:34 <rbergeron> that would be pretty scary :)
20:24:46 <gholms|work> euca2ools is capable of starting/listing/stopping instances, so we don't need to tell people to install rpmfusion either!  ;)
20:25:16 <rbergeron> anyway - so - greg had the amazon contact info - I'd imagine those same contacts might have some ideas on setting up testing / temporary accounts, no?
20:25:20 <jforbes> rbergeron: the preferred method for most people is here is a public image, test it on your account and give feedback
20:25:33 * ke4qqq thinks we are following a rabbit hole..... can we assign a task out of this?
20:25:44 <jforbes> rbergeron: Because if you don't have an EC2 account, you wont be running the images anyway.
20:26:31 <rbergeron> do we not trust people to not be going crazy on their accounts?
20:26:56 <rbergeron> ke4qqq: would you like to volunteer for something? :)
20:27:22 <ke4qqq> I am happy to research and report - and if necessary get us finding
20:27:23 <rbergeron> perhaps - talking to amazon folk and seeing if there is a best practice already recommended for testing things?
20:27:23 <ke4qqq> funding
20:27:29 <rbergeron> or - talk otto max about funding?
20:27:33 <rbergeron> err, talk to
20:27:41 <rbergeron> or whoever it would be
20:28:17 <rbergeron> ke4qqq: research and report on... testing, costs, etc?
20:28:19 <jforbes> Like I said, seems the best practice would be to make the images public for test day
20:28:44 <rbergeron> And people would need their own accounts for that
20:28:53 <jforbes> People can test them on their own accounts, and there is nothing to worry about there. If they don't have an account, they won't be the best of testers anyway
20:29:12 <jforbes> rbergeron: people without accounts would spend half of the test day learning how to interact with EC2 to begin with
20:29:33 <rbergeron> If there is documentation on what to test / how to test - or we actually take the initiative to help people set up accounts beforehand and get interested / acquainted
20:29:35 <ke4qqq> does that give us the possibility of bad rap for something that fails miserably?
20:30:12 <rbergeron> It (a) gets them involved - even if they're slow at first, they may catch up - (b) If we get people trained beforehand - we don't run the risk of that spending a half a test day doing the trianing.
20:30:15 <ke4qqq> or is just level of success that we are hoping to tune?
20:30:18 <rbergeron> Granted, we do the training beforehand instead -
20:30:42 <rbergeron> and we can either view that as a time-sink or not - but I like to think that at least any time sunk into the training will yield us at least a few new good contributors or testers.
20:30:49 <jforbes> No, why would we get a bad rap, we should do some manner of testing before test day, and expect the images to work.  I expect test day will be more fine tuning the contents of the images, etc
20:30:51 <rbergeron> Or documenters, or marketeers, or translators.
20:31:01 <ke4qqq> ok
20:31:44 <jforbes> This is all based on released F13, so really people are testing the image contents to make sure that they meet the needs for the minimal set
20:31:45 <rbergeron> so - I guess this is still somewhat up in the air but - ke4qqq, are you willing ot still look into that stuff just so we have it at least as reference information?
20:32:04 <ke4qqq> do we want to set a goal date for having: a) AKI uploaded, b) AMI uploaded, and c) stuff ready to test
20:32:32 <ke4qqq> rbergeron: feel free to task me as appropriate
20:32:37 <jforbes> ke4qqq: not until the kernel is ready
20:32:43 * rbergeron throws ke4qqq under the bus
20:32:53 <rbergeron> what about f14 feature list?
20:32:59 <rbergeron> same thing there?
20:33:11 <jforbes> No, we could start working that out now
20:33:28 <ke4qqq> only a few weeks til feature deadline (2 weeks, or less)
20:34:18 <rbergeron> #action ke4qqq Research and report back on possible costs of testing, if amazon has a recommendation on testing with large groups of testers, check into cost approval with ... whoever would pay for it.
20:34:54 <jforbes> Yeah, though fedora code will not change for this, so it is more about defining a process that can be followed to get F14 images posted on release day
20:35:20 <ke4qqq> it will get some press coverage too - feature list gets a good deal of coverage
20:35:26 <rbergeron> feature submission deadline is 7-13
20:37:10 <rbergeron> so - yes, we want to submit something for F14, or not
20:37:25 <jforbes> Yes, we will
20:37:31 <jforbes> I will submit it
20:37:35 <ke4qqq> awesome
20:37:36 <rbergeron> :D
20:38:14 <rbergeron> #action jforbes submit for F14 feature list
20:38:28 * rbergeron is a lover of #actioning, hopes jforbes doesnt' mind :)
20:38:42 <jforbes> Nope, not at all :)
20:39:22 <rbergeron> so - we were somewhere around kernel status
20:39:34 <gholms|work> Is EC2 able to boot with stock kernels these days?
20:39:39 <rbergeron> when we got off that topic quite a bit - were there other agenda items? :)
20:39:59 <jforbes> gholms|work: stock? no
20:40:07 <jforbes> gholms|work: which is why we have a patch to fix it
20:40:07 <ke4qqq> sooooo to return the favor - I assume you are going to start carpetbombing lots of outlets talking about this stuff right??? <--- rbergeron
20:40:40 <rbergeron> ke4qqq: as far as - get your butts in here and help?
20:40:56 <ke4qqq> yeah - and oohhhh shiny coming soon....
20:41:03 <rbergeron> When we have something out, definitely - we'll press the living heck out of it
20:41:11 <rbergeron> As well as the process -
20:41:20 <rbergeron> and i was going to ask if anyone's considered doing a cloud.fp.o webpage
20:41:23 <rbergeron> by chance
20:42:03 <rbergeron> but - in the meantime - blogging and so forth - as well as maybe a story going through RH press blog - might help us pick up new contributors
20:42:08 <rbergeron> but I think it would be wise to be ready to handle them.
20:42:24 <rbergeron> jforbes: i talked to smooge today a bit - he is really interested in coming to these meetings, but they're at the same time as infrastructure meetings.
20:42:30 <ke4qqq> jforbes: so the plan still is to use thincrust (I haven't cought up all the meeting logs, so may be way behind) to generate AMI? or something else?
20:42:44 * ke4qqq shuts up - doesn't want to double team jforbes
20:42:59 <rbergeron> I know you had requested some meeting time stuff - but apparently nobody has come for two weeks - is it possible to just bump it back to where it was (2100 UTC, i think?)
20:43:12 <rbergeron> or try again - if people voted on a time and they're not showing up
20:43:14 <rbergeron> ;)
20:43:15 <jforbes> rbergeron: Yeah, we had a problem there.  We had no one showing for the meeting at all, so I sent out a whenisgood to the list, and this was the best time it came up with
20:44:07 <jforbes> rbergeron: Well, so far attendence at this time has been about as good as the old time, so it doesn't seem that either of them work
20:44:08 <rbergeron> sooo - maybe we could try that again? I hate to exclude basically all of infrastrucutre folks - because I think a lot of those folks have interest here (not just smooge)
20:44:12 * rbergeron nods
20:44:30 <rbergeron> #action rbergeron to figure out an even better time for a meeting
20:44:34 <rbergeron> ^^^ is that okay?
20:44:52 <jforbes> Then again, a lot of the responses on that whenisgood were from people who I have never seen here
20:44:56 <rbergeron> right
20:44:58 <smooge> catching up. looking at the data for F8 (our big amazon ) most people use i386
20:45:02 <rbergeron> hi smooge
20:46:11 <huff> I have to run here in a bit is there anythign else yall need from me?
20:46:14 <jforbes> That's fine, but at least for the time being (getting images generated, kernels uploaded, and process for releng defined) we need huff and Oxf13.  There were not many times that they could all make
20:46:16 <ke4qqq> smooge: doesn't that make sense for most memory profiles on ec2?
20:46:42 * Oxf13 perks up at his name
20:46:51 <ke4qqq> ahhh so they are constraints - when can huff and Oxf13 devote time
20:47:19 <Oxf13> what am I being volunteered for again?
20:47:21 <jforbes> ke4qqq: Right, at least until we have the rudimentary images worked out, their times were deemed a priority
20:47:44 <rbergeron> Oxf13: the fate of the known universe, you know, little things
20:47:47 <ke4qqq> Oxf13: jforbes just said cloud sig rises and falls on you and huff - so when works for meetings
20:47:47 <rbergeron> :)
20:47:48 <jforbes> Oxf13: nothing at the moment, just saying a meeting time you were available was critical while we work on the process for pushing these images
20:48:05 <jforbes> hold on, I can make the responses public
20:49:10 <rbergeron> is there anyone not here now that has been significantly, actively interested in participating?
20:49:23 <jforbes> http://whenisgood.net/i4nhgw/results/bisfn3
20:49:58 <ke4qqq> Oxf13: also - while your focus is in this window - any idea on timeline of ec2 capable kernel being pushed? /me assumes you (or some other relenger) will be pushing it.....
20:50:06 <jforbes> smooge and mdomsch have been active participants (though neither repsonded to the whenisgood request)
20:50:16 <jforbes> ke4qqq: no, they wont
20:50:47 * jeevan_ullas raises his hand on rbergeron 's q
20:50:47 <Oxf13> ke4qqq: we may mash the button for the push action, but we don't really have visibility into when a package might show up in our queue.
20:50:52 <smooge> sorry i didn't see the whenisgood until it was announced it was over. My fault
20:50:55 <Oxf13> ke4qqq: we do pushes pretty much daily.
20:51:00 <jforbes> ke4qqq: kernel follows the same update process as anything else.  When the kernel folks push it to updates-testing, test and give it karma
20:51:16 <rbergeron> #link http://whenisgood.net/i4nhgw/results/bisfn3
20:51:46 <rbergeron> jeevan_ullas: yes?
20:52:05 <rbergeron> you're here now - so i'm thinking you're clearly interested - do you know of others?
20:52:24 <imcleod> rbergeron: The #stormgrind folks might well be interested.
20:52:29 <imcleod> Bob M and Marek Goldman.
20:53:02 <jeevan_ullas> rbergeron: very much interested. been here at 2:23am speaks for that. had sent a mail to the ML. yes also involved in boxgrinder. not intense but have used it internally.
20:53:32 <jeevan_ullas> will love to take up any task which the SIG might have for contributors like me in near future
20:54:03 <jeevan_ullas> testing is one area i can contribute but i dont have a ec2 account
20:54:34 <gholms|work> You can make one for free and use one for pennies an hour.
20:55:12 <rbergeron> jeevan_ullas: awesome, thanks. it's good to have people willing to contribute!
20:55:24 <rbergeron> imcleod: cool, thanks for the info.
20:55:35 <jeevan_ullas> gholms|work: i can probably do that.
20:55:36 <rbergeron> #info huff, Oxf13, s
20:55:39 <rbergeron> #undo
20:55:39 <zodbot> Removing item from minutes: <MeetBot.items.Info object at 0x14f5e250>
20:56:28 <rbergeron> #info huff, Oxf13, smooge, jforbes, rbergeron, #stormgrind folks - Bob M and Marek Goldman, jeevan_ullas, gholms - all interested.
20:56:36 <rbergeron> #info and ke4qqq.
20:56:39 * huff has to run now
20:56:41 <rbergeron> :D lol
20:56:41 <huff> if you need anything from me please shoot me an email, Ill have and updated ks file to the list tomorrow
20:56:52 <rbergeron> yes - thanks huff!!
20:56:52 <ke4qqq> huff thanks!!!!
20:57:36 <jforbes> thanks huff
20:58:50 <jforbes> Okay anyone have anything else for today?
20:58:54 <imcleod> jforbes: After a suitable kernel spin is available, how long do you anticipate it will take to produce the AKI?
20:59:26 <jforbes> imcleod: whenever I find my first rountuit... So guessing within 24 hours
20:59:33 <imcleod> Because I for one (and I suspect Marek as well) am ready to pounce on AMI creation and testing once that AKI is visible.
20:59:34 <ke4qqq> cool
20:59:58 <imcleod> Yes.  Cool.
21:00:31 <jforbes> Yeah, it doesn't take me long at all to create/push the AKI once we get the kernel
21:01:57 <jeevan_ullas> can we test the images (kernel/fs) for eucalyptus by any chance? or are they specific to EC2
21:01:58 <rbergeron> imcleod: are you handling the AMI piece?
21:02:27 <rbergeron> i don't believe we have a package for eucalyptus
21:02:32 <rbergeron> is that correct?
21:02:55 <jforbes> huff has been doing the ks, and I upload the AMIs when we have a working image
21:03:08 <jeevan_ullas> going through the previous mails in ML i think its not there yet.
21:03:24 <jeevan_ullas> but if i have eucalyptus setup on f13 box can i use the images
21:03:45 <rbergeron> is getting eucalyptus packaged something that needs to happen?
21:03:52 <rbergeron> if not short-term - maybe long-term
21:04:03 <jforbes> euca2ools is packaged
21:04:18 <jforbes> yum search euca2ools
21:04:24 <jforbes> ========================================================= Matched: euca2ools =========================================================
21:04:27 <jforbes> euca2ools.noarch : Elastic Utility Computing Architecture Command-Line Tools
21:05:00 <gholms|work> eucalyptus is the server side.  I'm afraid I'm terrible at Java packaging.
21:06:09 <rbergeron> Is it something that needs to be done longer-term - or not?
21:06:12 <jeevan_ullas> there are other dependencies which needs to be packaged for fedora as i see in ML
21:06:26 <jeevan_ullas> i believe it should be set a long term goal IMHO
21:06:26 <gholms|work> Side note:  any complaints if I update euca2ools to a development version that claims to support block device mapping?  I hear we need that to prep Fedora AMIs.
21:06:27 <jforbes> not necessary, though some people might want it
21:06:56 <rbergeron> jeevan_ullas: can you send a note to the mailing list with what you think some of those might be? dependencies, packages, etc.
21:07:01 <jforbes> gholms|work: no complaints, though send out a note for testing
21:07:20 <jeevan_ullas> rbergeron: sure i can collect the data. i believe it was discussed earlier too (as i read through the ML)
21:07:24 <gholms|work> Heh, maybe I'll actually get some testers this time.  :P
21:07:39 <rbergeron> gholms|work: let's hope so
21:07:40 <rbergeron> :)
21:07:40 <jeevan_ullas> need to check what's the progress on that side. afaik eucalyptus folks are working on that
21:08:03 <ke4qqq> gholms|work: make it known what you need - we can get bodies to help
21:08:16 <rbergeron> jeevan_ullas: let's get it on the mailing list and then into wiki - maybe start organizing a to-do now and to-do later or - to-do if you want to help out with packaging stuff.
21:08:17 <jforbes> I thought I heard some eucalyptus folks were testing with fedora, not sure what has come of it
21:08:30 <rbergeron> jeevan_ullas: sound good?
21:08:35 <jeevan_ullas> rbergeron: yep.
21:08:48 * gregdek lurks.
21:08:54 <jeevan_ullas> jforbes: i use eucalyptus on fedora works great for me. if packaged would be great. i can see how i can hep
21:08:57 <jeevan_ullas> help*
21:09:03 <gholms|work> ke4qqq: Sure thing.  The best testing would involve using it to control EC2 and prep AMIs; I'll send an email later.
21:09:15 <rbergeron> #action jeevan_ullas send note to mailing list with list of packages, dependencies, etc. that we might want to get people to volunteer to work on packaging, even if they are more longer-term / strategic items.
21:09:21 <rbergeron> jeevan_ullas: thanks!
21:09:31 <rbergeron> #action rbergeron to take list from jeevan_ullas mail and get it on wiki.
21:10:01 <jeevan_ullas> also if any wiki works on documentation side needs to be done (basic stuff) i am willing to help.
21:10:54 <jeevan_ullas> also to build ami and push to ec2 are we using boxgrinder?
21:11:11 * rbergeron throws gregdek a plow
21:11:27 <jforbes> jeevan_ullas: not initially, though perhaps longer term
21:12:09 <jeevan_ullas> ok
21:12:37 <imcleod> jforbes jeevan_ullas: That's actually what I'm going to attempt to do once the AKI is available.
21:12:40 <rbergeron> jeevan_ullas: docs is an excellent thing to start thinking about - I believe there's a spot on the wiki page, if you want to drop initial thoughts in there if nothing else.
21:13:02 <jeevan_ullas> imcleod: sounds cool.
21:13:04 <rbergeron> #link http://fedoraproject.org/wiki/Features/FedoraOnEC2#Documentation
21:13:27 <jeevan_ullas> i will blog about the meetup tomorrow and will keep doing that weekly.
21:13:38 <ke4qqq> jeevan_ullas: awesome!!!
21:14:42 <rbergeron> jeevan_ullas: thanks - blogging really helps to show momentum and get people involved.
21:14:49 <rbergeron> jforbes: is there anything ou wanted to cover today?
21:14:55 <rbergeron> or anyone else, for that matter?
21:15:17 <jforbes> rbergeron: nope, got what I needed
21:15:35 <rbergeron> cool. want me to ship out meeting logs?
21:15:42 <jforbes> sure
21:15:45 <rbergeron> #topic Open floor
21:15:48 <rbergeron> anyone have anything else?
21:15:58 * rbergeron wonders where the bot is
21:16:02 <rbergeron> #chair
21:16:02 <zodbot> Current chairs: jforbes rbergeron
21:16:15 <rbergeron> odd - usually it changes the topic
21:16:19 <ke4qqq> zodbot: doesn't have ops
21:16:23 <gholms|work> It doesn't have ops.
21:16:23 <gregdek> You may not have sufficient permissions.
21:16:38 <jeevan_ullas> regarding the cloud.fp.o can we talk with the website folks if they have any bandwidth
21:16:39 <gholms|work> So we're going to be meeting in here for now?
21:16:40 <gregdek> LOL
21:16:48 <jeevan_ullas> IMHO it is a great idea to have such kind of page later
21:16:55 * rbergeron notes that, thankfully, she's not in charge of anything technical ;)
21:17:02 <ke4qqq> jeevan_ullas: thanks for volunteering!! :)
21:17:18 <ke4qqq> gholms|work: I'd really like to see us in -meeting or -meeting-1 - get more eyes on what's going on
21:17:21 <jeevan_ullas> :)
21:18:08 <rbergeron> ke4qqq: i'm going to see if i can get a better meeting time than this - conflicting with infr. meeting is bad juju as i'd think those folks would be interested (actually know some of them are)
21:18:13 <jforbes> I have ops
21:18:20 <rbergeron> jforbes: op the bot! ;)
21:18:34 <ke4qqq> can you make this channel -t so mere mortals can set topic - or does that require spot?
21:18:40 <jforbes> Oh, I had ops...
21:18:47 <gholms|work> (Can someone fix /topic when we know when the next meeting will be?)
21:19:14 <jeevan_ullas> yep an a link to SIG wiki page
21:19:54 <ke4qqq> smooge: can you get zodbot opped and make this channel -t so mere mortals can change topic??
21:19:59 <rbergeron> ke4qqq: can you figure out how to get us ops or topic or whatever
21:20:01 <rbergeron> oh
21:20:04 <rbergeron> never mind.
21:20:26 <jforbes> sorry, had to get ops back myself first
21:20:54 <jforbes> And yes, I will change the topic when we know the next meeting time
21:21:05 <ke4qqq> it isn't weekly?
21:21:31 <jforbes> It is, but someone had the action item to see about a better time from today's meeting :)
21:21:46 <ke4qqq> ah yes :)
21:21:52 <gholms|work> Anything else?
21:22:52 <jforbes> #endmeeting