| *** open_stack has joined #openstack-meeting | 01:54 | |
| spy | #startmeeting | 01:56 |
|---|---|---|
| open_stack | Meeting started Fri Aug 27 01:56:09 2010 UTC. The chair is spy. Information about MeetBot at http://wiki.debian.org/MeetBot. | 01:56 |
| open_stack | Useful Commands: #action #agreed #help #info #idea #link #topic. | 01:56 |
| spy | #action blah blah | 01:56 |
| spy | #agreed blah blah | 01:56 |
| spy | #info blah blah | 01:56 |
| spy | #endmeeting | 01:56 |
| open_stack | Meeting ended Fri Aug 27 01:56:31 2010 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 01:56 |
| open_stack | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2010/openstack-meeting.2010-08-27-01.56.html | 01:56 |
| open_stack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2010/openstack-meeting.2010-08-27-01.56.txt | 01:56 |
| open_stack | Log: http://eavesdrop.openstack.org/meetings/openstack-meeting/2010/openstack-meeting.2010-08-27-01.56.log.html | 01:56 |
| spy | dendro-afk: should be ready to go | 02:14 |
| *** spy sets mode: +o open_stack | 02:15 | |
| *** dendro-afk is now known as dendrobates | 12:50 | |
| *** kim0 has joined #openstack-meeting | 13:13 | |
| *** ttx has joined #openstack-meeting | 13:47 | |
| *** zul has joined #openstack-meeting | 14:21 | |
| *** gasbakid has joined #openstack-meeting | 14:22 | |
| *** gasbakid has quit IRC | 14:47 | |
| *** dendrobates is now known as dendro-afk | 15:09 | |
| *** zhixuewu has joined #openstack-meeting | 15:57 | |
| *** timrc has joined #openstack-meeting | 15:58 | |
| *** dendro-afk is now known as dendrobates | 16:06 | |
| *** gholt has joined #openstack-meeting | 16:16 | |
| *** michalis has joined #openstack-meeting | 16:17 | |
| *** gustavomzw has joined #openstack-meeting | 16:17 | |
| *** michalis has left #openstack-meeting | 16:17 | |
| *** murkk has joined #openstack-meeting | 16:17 | |
| *** comstud has joined #openstack-meeting | 16:17 | |
| *** jk0 has joined #openstack-meeting | 16:19 | |
| *** cw has joined #openstack-meeting | 16:21 | |
| *** dendrobates is now known as dendro-afk | 16:21 | |
| *** metcalfc has joined #openstack-meeting | 16:22 | |
| *** dendro-afk is now known as dendrobates | 16:23 | |
| *** al-maisan has joined #openstack-meeting | 16:28 | |
| *** littleidea has joined #openstack-meeting | 16:28 | |
| *** glange has joined #openstack-meeting | 16:31 | |
| *** clayg has joined #openstack-meeting | 16:32 | |
| *** Daviey has joined #openstack-meeting | 16:33 | |
| *** xfrogman5 has joined #openstack-meeting | 16:34 | |
| *** letterj has joined #openstack-meeting | 16:35 | |
| *** kirkland has joined #openstack-meeting | 16:40 | |
| *** dubs has joined #openstack-meeting | 16:44 | |
| *** ctennis has joined #openstack-meeting | 16:45 | |
| *** User has joined #openstack-meeting | 16:47 | |
| *** Tushar has joined #openstack-meeting | 16:47 | |
| *** Tushar has quit IRC | 16:48 | |
| *** Tushar has joined #openstack-meeting | 16:48 | |
| *** _0x44 has joined #openstack-meeting | 16:50 | |
| *** jiboumans has joined #openstack-meeting | 16:51 | |
| *** nwl2110 has joined #openstack-meeting | 16:53 | |
| *** pvo has joined #openstack-meeting | 16:53 | |
| pvo | dendrobates: you make it back? | 16:54 |
| *** sirp1 has joined #openstack-meeting | 16:57 | |
| *** dabo has joined #openstack-meeting | 16:59 | |
| *** soren has joined #openstack-meeting | 17:00 | |
| soren | Aha! Way more people in here than in #openstack-meeting on OFTC :) | 17:00 |
| gholt | Heh | 17:01 |
| comstud | hehehe | 17:01 |
| *** ali`` has joined #openstack-meeting | 17:01 | |
| jk0 | h3h3 | 17:01 |
| comstud | t33h33 | 17:02 |
| _0x44 | soren: A meeting by yourself on another network is probably the easiest way to get everyone to agree to whatever your demands are :) | 17:02 |
| comstud | that's true | 17:02 |
| soren | _0x44: Oh, it was very productive. :) | 17:03 |
| soren | dendrobates: I assume you're chairing? | 17:03 |
| kirkland | soren: dendrobates is having some connectivity issues | 17:04 |
| kirkland | soren: he will be here shortly | 17:04 |
| soren | cool beans | 17:04 |
| dendrobates | #startmeeting | 17:04 |
| open_stack | Meeting started Fri Aug 27 17:04:28 2010 UTC. The chair is dendrobates. Information about MeetBot at http://wiki.debian.org/MeetBot. | 17:04 |
| open_stack | Useful Commands: #action #agreed #help #info #idea #link #topic. | 17:04 |
| dendrobates | hello | 17:04 |
| pvo | phew, it worked. :) | 17:04 |
| _0x44 | pvo: Is he connected over your nexus one? | 17:04 |
| pvo | _0x44: hopefully over his nexus one. : ) | 17:05 |
| jk0 | hah | 17:05 |
| spy | yay | 17:05 |
| dendrobates | #link http://wiki.openstack.org/Meetings | 17:05 |
| dendrobates | I am lagging a bit so if I drop I will need someone to take over | 17:05 |
| dendrobates | Topic: Release | 17:06 |
| *** eday has joined #openstack-meeting | 17:06 | |
| dendrobates | #topic Blueprints | 17:07 |
| *** open_stack changes topic to "Blueprints" | 17:07 | |
| dendrobates | damn meetbot | 17:07 |
| *** _cerberus_ has joined #openstack-meeting | 17:07 | |
| *** mencken has joined #openstack-meeting | 17:07 | |
| dendrobates | first I wan to talk about what we want the austin release to be. | 17:07 |
| dendrobates | We doing time based not feature based releases | 17:08 |
| dendrobates | with the caveat that we might slip a date only if a mandatory feature is not ready. | 17:08 |
| dendrobates | but we don;t expect that to happen. | 17:09 |
| *** tr3buchet has joined #openstack-meeting | 17:09 | |
| dendrobates | The mandatory features for Austin are: | 17:09 |
| dendrobates | Rackspace API | 17:09 |
| dendrobates | Image caching service | 17:09 |
| dendrobates | Xen support | 17:09 |
| *** annegentle has joined #openstack-meeting | 17:10 | |
| clayg | Image caching service == Glance ? | 17:10 |
| dendrobates | everything else only goes in if it is ready by feature freeze and stable by final freeze | 17:10 |
| dendrobates | clayg: yes | 17:11 |
| dendrobates | do the swift guys have any required features? | 17:11 |
| pvo | what about the pluggable scheduler for nova? Is that mandatory? | 17:11 |
| clayg | is rconradharris here? | 17:11 |
| _0x44 | dendrobates: We need to #info that for the meetbot to log it. | 17:11 |
| _0x44 | #info mandatory features for austin are: Rackspace API, Image Caching Service, Xen support | 17:11 |
| dubs | clayg: yes, that is sirp1 | 17:11 |
| sirp1 | *rconradharris* | 17:11 |
| dendrobates | meetbot is not responding | 17:11 |
| pvo | it doesn't while in flight | 17:12 |
| spy | dendrobates: it doesn't respond for info | 17:12 |
| dendrobates | hmm | 17:12 |
| gholt | For Swift, Very Large File Support is required, I have many more desired. | 17:12 |
| dendrobates | ok | 17:12 |
| pvo | #help | 17:12 |
| dendrobates | gholt: what about nova auth for swirt | 17:12 |
| dendrobates | required or not? | 17:12 |
| gholt | Unsure on that. I'd like a separate Scalable Auth Project. I've been working on Swauth to hopefully fill that gap, but.. | 17:13 |
| *** gasbakid has joined #openstack-meeting | 17:13 | |
| _0x44 | #info swift mandatory features for austin: very large file support, more desired | 17:13 |
| dendrobates | ok, we will not make it a req, if it gets done it gets done. | 17:13 |
| dubs | gholt: are public containers in swift set for Austin? | 17:13 |
| gholt | I hope so, and they should be barring performance problems. | 17:14 |
| gholt | They are second on my list. :) | 17:14 |
| pvo | dubs: that what I heard. | 17:14 |
| dendrobates | So everybody should have gotten the message that for every feature we need a blueprint and spec by next friday | 17:14 |
| dendrobates | I will be glad to help anyone that needs it | 17:15 |
| gholt | Yes, I've been putting that off, sorry. I'll do that today/this-weekend for what I see in Swift. | 17:15 |
| letterj | What are we going to use for a mulit-server test/qa lab? | 17:16 |
| gholt | I love for bringing that up. :) | 17:16 |
| *** al-maisan is now known as almaisan-away | 17:16 | |
| letterj | Is having a test/qa lab a requirement for the release? | 17:17 |
| dendrobates | We have a couple of options, we can use soren's uml work to do some testing in the rackspace cloud | 17:17 |
| dendrobates | and we will have to spin up some servers in the rackspace lab for bare metal testing | 17:17 |
| pvo | I think the concern is how to measure performance impacts for large clusters | 17:18 |
| dendrobates | NASA might be able to help with testing as well. | 17:18 |
| letterj | there is no public access in the rackspace lab. (Something to keep in mind) | 17:18 |
| gholt | Is the funding in place, ongoing for a Rackspace sponsored lab? Will it be accessible to all contributors? etc. | 17:18 |
| dendrobates | We need a in depth test plan, which we donot have yet. | 17:18 |
| letterj | I'm assuming blueprints will be needed for that? | 17:19 |
| pvo | dendrobates: you or I can take that as an action item | 17:19 |
| pvo | its a discussion point first before we have blueprint, no? | 17:19 |
| dendrobates | #action find out about rackspace test lab for qa | 17:20 |
| pvo | #action Determine testing/qa environments for OpenStack | 17:20 |
| pvo | heh | 17:20 |
| letterj | I'll be happy to help with the swift side as much as I can | 17:20 |
| dendrobates | a blueprint for what, testing? | 17:20 |
| letterj | yes testing and qa process | 17:20 |
| pvo | yea, to find out about testing | 17:20 |
| dendrobates | I hadn't thought that we would, but it is a good idea | 17:21 |
| dendrobates | #action create a testing/QA blueprint | 17:22 |
| dendrobates | Does anyone have any questions about blueprints? | 17:22 |
| dendrobates | Is there anyone else that would volunteer to help others with Blueprints? | 17:22 |
| gholt | There will definitely be some lab contention, so getting your-favorite-feature-to-be-tested on some list will help. "You get x days in the lab starting on y, succeed or unmerge" :) | 17:23 |
| pvo | i guess we can explore UML in the public cloud, no? | 17:23 |
| spy | really if we could get some sort of openstack images in the cloud, we could spin up an environment very easily | 17:23 |
| spy | we could have the images check out the latest code as they come on-line or something | 17:23 |
| soren | pvo: Yeah, with my last few patches to libvirt, its UML support seems to be in really good shape. | 17:24 |
| spy | probably wouldn't be ideal for performance but integration testing | 17:24 |
| dendrobates | that's a good thing about having Rackspace as a primary sponsor servers galoree | 17:24 |
| pvo | soren: yea, thats exactly what I was thinking. | 17:24 |
| dendrobates | the topic is still blueprints | 17:25 |
| dendrobates | are there any more questions about them? | 17:25 |
| *** movmov has joined #openstack-meeting | 17:25 | |
| soren | My primary motivation for doing that work was exactly for testing, but of course we still need testing with serious hypervisors. | 17:25 |
| *** movmov has quit IRC | 17:25 | |
| *** movmov has joined #openstack-meeting | 17:25 | |
| dendrobates | does everyone understand what needs to be done? | 17:25 |
| dendrobates | I will take silence as yes | 17:25 |
| littleidea | is there a good document that explains blueprints and how to use them/interact with the community through them? | 17:26 |
| dendrobates | littleidea: I'm not sure. There should be. I'll ask the launchpad folks | 17:26 |
| dendrobates | if I find anything, I'll send it to the openstack ml | 17:27 |
| _0x44 | Are we still using the etherpad to do the writeups of the blueprints since the blueprint UI was so abysmal? | 17:27 |
| * _0x44 remembers some discussion about that in #openstack | 17:27 | |
| eday | https://help.launchpad.net/Blueprint is a good start | 17:27 |
| sirp1 | #link https://help.launchpad.net/Blueprint | 17:27 |
| soren | https://edge.launchpad.net/+tour/feature-tracking perhaps | 17:27 |
| soren | Err... without "edge.". | 17:28 |
| dendrobates | they need to end up in lainchpad so I can track and approve them | 17:28 |
| soren | #link https://launchpad.net/+tour/feature-tracking | 17:28 |
| dendrobates | I think we need a naming scheme for blueprints too | 17:28 |
| dendrobates | any suggestions? | 17:28 |
| pvo | can you give an example? | 17:29 |
| kirkland | $(tempfile) | 17:29 |
| pvo | are you meaning if we want it in austin, it would be austin-someniftyfeature ? | 17:29 |
| dendrobates | openstack-$release-feature | 17:29 |
| pvo | works for me | 17:29 |
| clayg | and if it's not ready for release... does it get renamed to try for next time? | 17:29 |
| dendrobates | or openstack-component-release-feature | 17:29 |
| dendrobates | or ... | 17:30 |
| dendrobates | yes | 17:30 |
| pvo | just nitpicking, but is the 'openstack' part redundant? | 17:30 |
| _0x44 | If they're already associated with a | 17:30 |
| _0x44 | Err what pvo said | 17:30 |
| dendrobates | true, | 17:30 |
| _0x44 | Would release-component-feature be better? | 17:30 |
| _0x44 | That way they're grouped by release | 17:30 |
| pvo | yes | 17:30 |
| dendrobates | but shutup :) | 17:30 |
| eday | _0x44: yeah, there is a wiki/spec link on the blueprint, and I've been linking ehterpad docs to those that need more | 17:30 |
| _0x44 | And then by component | 17:30 |
| *** jaypipes has joined #openstack-meeting | 17:30 | |
| _0x44 | eday: I think people have preferred the etherpad docs to the wiki/spec stuff attached to the blueprints. I guess we can use both, but it would be nice if we only had to worry about one. | 17:31 |
| eday | _0x44: well, they don't really overlap.. etherpad is just the description.. blueprints have assignment, project tracking, dependencies, ... | 17:32 |
| spy | might be a good idea to work in etherpad, and once the doc is completed update it in the blueprint | 17:32 |
| eday | I would say don't put the release name in the blueprint, since we have URLs like this to do that for us: https://blueprints.launchpad.net/nova/austin | 17:33 |
| _0x44 | eday: No, I meant use etherpad instead of the wiki/spec, not instead of the blueprint. | 17:33 |
| jaypipes | spy: ++ | 17:33 |
| eday | lots of renaming if a feature doesn't make a release | 17:33 |
| eday | _0x44: oh, yeah | 17:33 |
| _0x44 | Are we doing blueprints in each component or in the umbrella project? | 17:34 |
| eday | _0x44: I've been using etherpad over the wiki | 17:34 |
| dabo | eday: +1 | 17:34 |
| jaypipes | _0x44: good question. | 17:34 |
| _0x44 | If we do them in the components, then the naming scheme is just "feature name" | 17:34 |
| jaypipes | _0x44: I prefer to put them in the specific project unless the blueprint touches multiple projects... | 17:34 |
| eday | jaypipes: ++, and if they do touch many, it's probably going to actually be in another project like openstack-common :) | 17:35 |
| jaypipes | _0x44: or "feature-category-feature-name" ... example: data-model-support-sqlite ? | 17:35 |
| jaypipes | eday: yeah, agreed. | 17:35 |
| _0x44 | jaypipes I'd prefer a different delimiter than hyphen in that case. | 17:36 |
| dendrobates | ok I'm back | 17:37 |
| jaypipes | _0x44: sure, no worries... | 17:37 |
| *** dabo is now known as dabo_brb | 17:37 | |
| dendrobates | did we come to agreement on bluepprint naming? | 17:37 |
| _0x44 | dendrobates: Blueprints in the umbrella project or in the component projects? | 17:37 |
| jaypipes | _0x44: any prefix is fine. Consistency is my only need | 17:37 |
| dendrobates | umbrella | 17:37 |
| _0x44 | WHy? | 17:38 |
| * jaypipes votes for blueprints in subproject | 17:38 | |
| * _0x44 agrees with jaypipes | 17:38 | |
| dendrobates | jaypipes: why? | 17:38 |
| _0x44 | (shock, horror) | 17:38 |
| jaypipes | dendrobates: for blueprints that touch on multiple projects, use the openstack-common project. | 17:38 |
| jaypipes | dendrobates: and for blueprints that affect things like the unified build and packaging platforms (like Hduson/Tarmac), put the blueprint in the umbrella project | 17:39 |
| dendrobates | I am concerned with tracking the whole project and ensuring all the subprojects are on track | 17:39 |
| dendrobates | ok, I see | 17:39 |
| dendrobates | I'm talking about naming only | 17:39 |
| eday | dendrobates: you still cna if they are created in the context of a project | 17:39 |
| dendrobates | not obout where we create them | 17:39 |
| jaypipes | dendrobates: I understand that concern, but Nova devs don't necessarily want to sift through Swift blueprints and vice versa... | 17:39 |
| *** nwl2110 has quit IRC | 17:39 | |
| _0x44 | dendrobates: Right, but if they're tracked in the sub project they won't need a project prefix. | 17:40 |
| dendrobates | the will all show up in the umbrella project any way, so I agree | 17:40 |
| dendrobates | I would still like a prefix | 17:40 |
| _0x44 | We can use "feature-categoryDELIMITERfeature-name" | 17:40 |
| jaypipes | dendrobates: ah, sorry. misunderstood. I think it would be a better idea (than prefixing blueprint names with the project name) to bug the LP team to have better search/filtering for lists of blueprints! :) | 17:40 |
| _0x44 | ^^^ +1 | 17:40 |
| gholt | Ah, do the blueprints float up to the umbrella? | 17:41 |
| * jaypipes has had a beef with the blueprints filtering ability for a while now.. | 17:41 | |
| dendrobates | let me check , I assumed so. | 17:41 |
| eday | gholt: they do, see: https://blueprints.launchpad.net/openstack/ | 17:41 |
| jaypipes | gholt: yes | 17:41 |
| gholt | Gotcha. They do have the project column though... | 17:41 |
| jaypipes | gholt: which would be great if we could filter the list by project... :) | 17:41 |
| gholt | Well, none of the project workers would use that, just dendrobates. :) | 17:41 |
| eday | jaypipes: just add project to that URL :) | 17:42 |
| dendrobates | yes | 17:42 |
| dendrobates | ant it list the sub project | 17:42 |
| _0x44 | dendrobates: Each blueprint is already labeled by project | 17:42 |
| dendrobates | weeeeee | 17:42 |
| jaypipes | gholt: hey, poison frog is important, too ;) | 17:42 |
| jaypipes | _0x44, eday: hmm, that's new. cool.. much beter. | 17:42 |
| _0x44 | jaypipes: Only because Destro hangs with the Baronness | 17:42 |
| jaypipes | hehe | 17:42 |
| dendrobates | so are we in agreement? | 17:43 |
| jaypipes | OK, so does that settle the prefix-with-project debate? | 17:43 |
| *** movmov has quit IRC | 17:43 | |
| jaypipes | ++ from me. | 17:43 |
| dendrobates | blueprints under the subproject named - $release-feature? | 17:43 |
| dendrobates | or did I miss something else? | 17:43 |
| _0x44 | dendrobates: We sort of decided not to prefix with release name | 17:44 |
| eday | dendrobates: I think we decided without project name in there, since that is already a field | 17:44 |
| _0x44 | Because if it gets dumped from a release we have to rename it. | 17:44 |
| pvo | so, just feature, under the subproject | 17:44 |
| gholt | Series is also a blueprint column. :) | 17:44 |
| gholt | So just component/feature is fine by me. Hehe | 17:45 |
| dendrobates | I want release in the name | 17:45 |
| eday | dendrobates: why? | 17:45 |
| _0x44 | So $feature_category/$feature | 17:45 |
| dendrobates | they are trivial to change | 17:45 |
| _0x44 | ? | 17:45 |
| dendrobates | and they help with sorting. | 17:45 |
| soren | Searchability. | 17:45 |
| soren | Stuff doesn't land on b.l.n/openstack/austin (as an example) until it's actually been approved for that release. | 17:46 |
| soren | ...so until then, the only way to filter stuff is by name. | 17:46 |
| soren | IIRC. | 17:46 |
| dendrobates | so let me repeat I want the release as a prefix | 17:46 |
| gholt | soren: Ah, gotcha | 17:46 |
| dendrobates | it also let's you weed out old bluprints | 17:46 |
| jaypipes | dendrobates: I strongly disagree with that, having been the person to rename crap-tons of blueprints in the past... | 17:46 |
| eday | soren: but then as features slip we need to rename them all :) | 17:47 |
| dendrobates | jaypipes: let;s agree to disagree. I have also renamed a crap ton of blueprints | 17:47 |
| _0x44 | I think we can probably compromise on this by allowing dendrobates release names in blueprints, but if they slip he has to rename them. | 17:47 |
| dendrobates | or delegate someone to do it | 17:47 |
| _0x44 | I dunno, if you want them this badly, you should be prepared to do the effort of maintaining them. | 17:48 |
| jaypipes | dendrobates: I agree to that, as long as I never am the delegate ;) | 17:48 |
| dendrobates | agreed | 17:48 |
| eday | or the folks assigned can rename their own so it's not just one.. spread the burden. but anyways, not a big deal :) | 17:49 |
| *** jbryce has joined #openstack-meeting | 17:49 | |
| dendrobates | it is probably a candidate for a simple script | 17:49 |
| * jaypipes disagrees for another reason... if I post something on a mailing list referencing the blueprint, and it is renamed because of a release slip, the link is now defunct... | 17:49 | |
| eday | although I would file this as a LP feature request, since this is redundant info in their system | 17:50 |
| dendrobates | eday | 17:50 |
| dendrobates | true | 17:50 |
| eday | but we can have that discussion later | 17:50 |
| dendrobates | Can we do it this release and revisit at the dev summit? | 17:51 |
| dendrobates | We can invite the LP devs | 17:51 |
| jaypipes | dendrobates: fine by me. | 17:51 |
| eday | sounds good | 17:51 |
| dendrobates | ok | 17:51 |
| dendrobates | so for this release $(release)-feature | 17:52 |
| dendrobates | name me as the approver. | 17:52 |
| dendrobates | Sept 3 is the deadline | 17:52 |
| dendrobates | any last questions. | 17:52 |
| jaypipes | nope | 17:52 |
| _0x44 | None here | 17:53 |
| dendrobates | great | 17:53 |
| eday | this may be more dev/process, but do we want to use milestones for smaller releases? ie, every two weeks or something? | 17:53 |
| eday | (since this relates to blueprints, being a field in them) | 17:53 |
| dendrobates | I was thinking of using milestones for release cycle stuff | 17:53 |
| dendrobates | such as feature freeze, Beta, and RC | 17:54 |
| dendrobates | Let's take this discussion to the mailing list for time sake. | 17:55 |
| eday | ok... just thinking if you only get a PPA update/tarball every 3-6 months.. is that often enough? | 17:55 |
| dendrobates | I think we should have daily builds, and then a beta, release candidate, ... | 17:56 |
| dendrobates | in a 6 mo release we can insert more. | 17:56 |
| eday | k | 17:56 |
| dendrobates | btw, it has been suggested that we have two more 3 month releases before switching to a 6 month schedule. | 17:57 |
| dendrobates | #topic release schedule | 17:57 |
| *** open_stack changes topic to "release schedule" | 17:58 | |
| dendrobates | is there anyone who disagrees with that? | 17:58 |
| dendrobates | countdown 5 | 17:58 |
| dendrobates | 4 | 17:58 |
| dendrobates | 3 | 17:58 |
| dendrobates | 2 | 17:58 |
| dendrobates | 1 | 17:58 |
| dendrobates | done | 17:58 |
| dendrobates | we are running out of time let move the remaining topics to the mailing list, except meeting time | 17:59 |
| soren | Well.. | 17:59 |
| dendrobates | too late!!!!!!!! :) | 17:59 |
| soren | Does that mean we'll have an extra summit? | 17:59 |
| eday | sounds good, and I wouldn't be opposed to keeping 3 month indefinitely :) | 17:59 |
| dendrobates | no, the next summit will cover 2 three month releases | 17:59 |
| soren | Alright. | 17:59 |
| dendrobates | #topic meeting time | 18:00 |
| *** open_stack changes topic to "meeting time" | 18:00 | |
| soren | I'd very much like to discuss this meeting time, by the way. | 18:00 |
| soren | Oh | 18:00 |
| soren | Heh :) | 18:00 |
| dendrobates | I want to move it to 3am DK time. | 18:00 |
| soren | +1 | 18:00 |
| eday | soren: because it's friday night, or just any night? | 18:01 |
| soren | I've said it many times before. Middle of the night beats the 5-8 pm slot any day. | 18:01 |
| dendrobates | so next week I want to keep the day the same, because of the blueprint deadline | 18:01 |
| dendrobates | after that we should move to a more reasonable day | 18:01 |
| soren | eday: I'd be cool with a couple of hours later if it was a different day. | 18:01 |
| dendrobates | but does anyone have a better time suggestion | 18:01 |
| soren | eday: Tuesday 1900 UTC? | 18:02 |
| soren | Err.. | 18:02 |
| soren | Not just to eday, obviously :) | 18:02 |
| dendrobates | A couple hours later might allow our friends in Asia to patrticipate | 18:02 |
| soren | I work late Tuesdays anyway, so that would be ideal for me. | 18:03 |
| _0x44 | How abotu 1530 or 1600 CDT next friday, then we move to Tuesdays? | 18:03 |
| dendrobates | after next week | 18:03 |
| dendrobates | great, but I think that is VERY early in Japan, where I know we have people that want to participate | 18:04 |
| soren | How long do we expect the meetings to be? If they're capped at 1 hour, 1600 CDT (2100 UTC, right?) is fine. | 18:04 |
| soren | ....while we're in DST, at least. | 18:05 |
| dendrobates | that is 6am in Japan, | 18:05 |
| dendrobates | which is better than this, | 18:05 |
| _0x44 | So 1900 CDT? | 18:05 |
| dendrobates | but 10pm for most of EU | 18:06 |
| dendrobates | works for me. | 18:06 |
| _0x44 | That's really late in the EU though. | 18:06 |
| soren | 1600 CDT is 2300 for EU. | 18:06 |
| soren | Well, mainland EU. | 18:06 |
| *** ali`` has left #openstack-meeting | 18:07 | |
| ttx | I think there is no time that can fit all. Even USwestcoast + europe is difficult, without considering Japan. | 18:07 |
| dendrobates | how about 3 hours forward 20:00 UTC | 18:07 |
| dendrobates | http://goo.gl/tdg0 | 18:07 |
| dendrobates | anyone | 18:08 |
| soren | That's fine with me. | 18:08 |
| soren | Perfect, even. | 18:08 |
| _0x44 | 1500 CDT is fine | 18:09 |
| dendrobates | any other Europeans want to comment? | 18:09 |
| soren | It's outside business hours, but also outside family time. => me happy | 18:09 |
| soren | Er... Hang on. | 18:09 |
| soren | Which day? | 18:09 |
| dendrobates | next week it is friday | 18:09 |
| dendrobates | after that we will change it | 18:09 |
| soren | Wicked. | 18:09 |
| dendrobates | countdown for objections 5 | 18:10 |
| dendrobates | 4 | 18:10 |
| dendrobates | 3 | 18:10 |
| dendrobates | 2 | 18:10 |
| dendrobates | 1 | 18:10 |
| dendrobates | #item next release meeting http://goo.gl/WHj2 | 18:11 |
| dendrobates | We've gone over | 18:11 |
| dendrobates | any last items? | 18:11 |
| dendrobates | ok, continue discussions on #openstack if you want | 18:12 |
| dendrobates | #endmeeting | 18:12 |
| *** open_stack changes topic to "Next OpenStack release meeting on Friday August 27th 17:00UTC/12:00CDT http://wiki.openstack.org/Meetings" | 18:12 | |
| open_stack | Meeting ended Fri Aug 27 18:12:23 2010 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:12 |
| open_stack | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2010/openstack-meeting.2010-08-27-17.04.html | 18:12 |
| open_stack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2010/openstack-meeting.2010-08-27-17.04.txt | 18:12 |
| open_stack | Log: http://eavesdrop.openstack.org/meetings/openstack-meeting/2010/openstack-meeting.2010-08-27-17.04.log.html | 18:12 |
| dendrobates | thanks everyone | 18:12 |
| _0x44 | Thanks dendrobates | 18:12 |
| *** zul has quit IRC | 18:14 | |
| *** clayg has left #openstack-meeting | 18:14 | |
| *** gholt has left #openstack-meeting | 18:14 | |
| *** dubs has left #openstack-meeting | 18:14 | |
| *** annegentle has left #openstack-meeting | 18:15 | |
| *** deshantm has joined #openstack-meeting | 18:15 | |
| *** kirkland has left #openstack-meeting | 18:16 | |
| *** Tushar has quit IRC | 18:22 | |
| *** dabo_brb has left #openstack-meeting | 18:38 | |
| *** dabo_brb has quit IRC | 18:38 | |
| *** jbryce has left #openstack-meeting | 18:53 | |
| *** _cerberus_ has left #openstack-meeting | 19:08 | |
| *** spy changes topic to " Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2010/" | 19:13 | |
| *** mencken has quit IRC | 19:15 | |
| *** ctennis has quit IRC | 19:17 | |
| *** jk0 has left #openstack-meeting | 19:20 | |
| *** _0x44 has left #openstack-meeting | 19:23 | |
| *** dendrobates is now known as dendro-afk | 20:31 | |
| *** kim0 has quit IRC | 20:36 | |
| *** vishy has joined #openstack-meeting | 20:58 | |
| *** ctennis has joined #openstack-meeting | 20:58 | |
| vishy | so my timing was off on the meeting :) | 20:58 |
| vishy | I hope it went well | 20:58 |
| xfrogman5 | Missed it by that much... :-) | 21:04 |
| xfrogman5 | vishy: the minutes are available | 21:05 |
| vishy | xfrogman: cool, reading them now | 21:17 |
| vishy | xfrogman5: cool, reading them now | 21:17 |
| vishy | \win 2 | 21:22 |
| *** letterj has left #openstack-meeting | 21:33 | |
| *** xfrogman5 has quit IRC | 21:38 | |
| *** ctennis has quit IRC | 23:03 | |
| *** littleidea has quit IRC | 23:03 | |
| *** ctennis has joined #openstack-meeting | 23:03 | |
| *** littleidea has joined #openstack-meeting | 23:03 | |
| *** dendro-afk is now known as dendrobates | 23:28 | |
| *** sirp1 has quit IRC | 23:43 | |
| *** dendrobates is now known as dendro-afk | 23:45 | |
| *** glange has left #openstack-meeting | 23:49 | |
| *** gasbakid has quit IRC | 23:56 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!