Monday, 2011-12-12

*** beekhof_ has quit IRC00:07
*** beekhof_ has joined #openstack-meeting00:12
*** beekhof_ has quit IRC00:30
*** beekhof has joined #openstack-meeting00:31
*** jmckenty has joined #openstack-meeting00:57
*** beekhof__ has joined #openstack-meeting00:59
*** beekhof has quit IRC01:00
*** beekhof_1 has joined #openstack-meeting01:27
*** beekhof__ has quit IRC01:28
*** beekhof_ has joined #openstack-meeting01:54
*** adjohn has joined #openstack-meeting01:54
*** beekhof_1 has quit IRC01:55
*** jeremyb has quit IRC01:56
*** jeremyb has joined #openstack-meeting01:56
*** littleidea has quit IRC02:02
*** jmckenty has quit IRC02:18
*** beekhof_ has quit IRC02:20
*** beekhof_ has joined #openstack-meeting02:34
*** beekhof_ has quit IRC02:38
*** beekhof has joined #openstack-meeting02:39
*** jmckenty has joined #openstack-meeting02:42
*** beekhof has quit IRC03:00
*** beekhof_ has joined #openstack-meeting03:05
*** mdomsch has joined #openstack-meeting03:47
*** adjohn has quit IRC04:42
*** adjohn has joined #openstack-meeting04:52
*** adjohn has quit IRC04:58
*** adjohn has joined #openstack-meeting05:40
*** adjohn has quit IRC05:47
*** mdomsch has quit IRC05:50
*** adjohn has joined #openstack-meeting06:00
*** adjohn has quit IRC06:00
*** dwalleck has joined #openstack-meeting06:11
*** lloydde has joined #openstack-meeting06:19
*** novas0x2a|laptop has quit IRC06:29
*** lloydde has quit IRC06:39
*** dwalleck has quit IRC06:59
*** ttx has quit IRC07:45
*** ttx has joined #openstack-meeting07:45
*** jakedahn has joined #openstack-meeting08:10
*** jakedahn has quit IRC08:11
*** novas0x2a|laptop has joined #openstack-meeting08:15
*** novas0x2a|laptop has quit IRC08:30
*** novas0x2a|laptop has joined #openstack-meeting08:31
*** novas0x2a|laptop has quit IRC08:39
*** novas0x2a|laptop has joined #openstack-meeting08:40
*** novas0x2a|laptop has quit IRC08:55
*** jmckenty has quit IRC09:08
*** darraghb has joined #openstack-meeting09:32
*** dendro-afk has quit IRC10:55
*** mattray has joined #openstack-meeting13:50
*** dprince has joined #openstack-meeting13:52
*** mdomsch has joined #openstack-meeting13:57
*** dolphm has joined #openstack-meeting13:57
*** deshantm_laptop has joined #openstack-meeting14:23
*** dolphm has quit IRC14:29
*** dwalleck has joined #openstack-meeting14:56
*** deshantm_laptop_ has joined #openstack-meeting15:18
*** deshantm_laptop has quit IRC15:18
*** deshantm_laptop_ is now known as deshantm_laptop15:19
*** CDY has joined #openstack-meeting15:23
*** dwalleck has quit IRC15:32
*** jpipes has joined #openstack-meeting15:56
*** rnirmal has joined #openstack-meeting15:56
*** adjohn has joined #openstack-meeting16:01
*** jpipes has quit IRC16:03
*** dwalleck has joined #openstack-meeting16:19
*** ironcame1 is now known as ironcamel16:31
*** joesavak has joined #openstack-meeting16:42
*** mattray has quit IRC16:49
*** mdomsch has quit IRC16:58
*** oubiwann has joined #openstack-meeting17:00
*** sleepsonthefloo has joined #openstack-meeting17:14
*** hggdh has quit IRC17:16
*** jsavak has joined #openstack-meeting17:21
*** adjohn has quit IRC17:23
*** joesavak has quit IRC17:24
*** hggdh has joined #openstack-meeting17:25
*** dwalleck has joined #openstack-meeting17:28
*** jog0 has joined #openstack-meeting17:34
*** bengrue has joined #openstack-meeting17:36
*** dwalleck_ has joined #openstack-meeting17:36
*** jdurgin has joined #openstack-meeting17:40
*** dwalleck has quit IRC17:40
*** dwalleck_ has quit IRC17:42
*** dwalleck has joined #openstack-meeting17:43
*** davlap has joined #openstack-meeting17:44
*** davlap has quit IRC17:55
*** davlap has joined #openstack-meeting17:56
*** jmckenty has joined #openstack-meeting18:00
*** sleepsonthefloo has quit IRC18:02
*** hggdh has quit IRC18:05
*** dwalleck has quit IRC18:06
*** hggdh has joined #openstack-meeting18:07
*** sleepsonthefloo has joined #openstack-meeting18:18
*** novas0x2a|laptop has joined #openstack-meeting18:22
*** littleidea has joined #openstack-meeting18:30
*** bcwaldon has joined #openstack-meeting18:31
*** lloydde has joined #openstack-meeting18:33
*** novas0x2a|laptop has quit IRC18:36
*** novas0x2a|laptop has joined #openstack-meeting18:36
*** darraghb has quit IRC18:39
*** davlap has quit IRC18:40
*** sleepsonthefloo_ has joined #openstack-meeting18:43
*** sleepsonthefloo has quit IRC18:47
*** sleepsonthefloo_ is now known as sleepsonthefloo18:47
*** adjohn has joined #openstack-meeting18:48
*** dwalleck has joined #openstack-meeting18:52
*** deshantm_laptop has quit IRC18:55
*** dwcramer has joined #openstack-meeting19:03
*** GheRivero_ has joined #openstack-meeting19:09
*** adjohn has quit IRC19:13
*** adjohn has joined #openstack-meeting19:13
*** AlanClark has joined #openstack-meeting19:18
*** donaldngo_hp has joined #openstack-meeting19:26
*** davlap has joined #openstack-meeting19:40
*** mdomsch has joined #openstack-meeting19:41
annegentleDoc/Web team meeting in here in about 12 mins19:48
*** jog0 has left #openstack-meeting19:51
*** jog0 has joined #openstack-meeting19:51
*** davlap has quit IRC19:56
*** davlap has joined #openstack-meeting19:57
*** dubsquared has joined #openstack-meeting20:00
annegentleanyone around for the Doc/Web team meeting?20:01
bcwaldonyep20:01
annegentlecoolio20:01
dubsquared<-20:01
annegentlewelcome dubsquared20:02
dubsquaredhow goes it20:02
annegentlewell, thanks20:03
annegentlelloydde: around?20:03
annegentlenot sure anyone interested in translations will be able to attend at this time...20:03
annegentlebut it's on the agenda.20:03
annegentleI can go ahead and start20:03
annegentle#startmeeting20:03
openstackMeeting started Mon Dec 12 20:03:49 2011 UTC.  The chair is annegentle. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.20:03
annegentleWelcome to the Doc / Web team meeting, we meet monthly about documentation and the OpenStack website.20:04
annegentle#topic API quick start and reference page20:04
*** openstack changes topic to "API quick start and reference page"20:04
annegentleThis is probably a repeat from the weekly team meeting, but we welcome input on http://heckj.github.com/api-site-mock/20:04
annegentleThe idea is to provide a reference site for developers consuming OpenStack APIs.20:05
annegentleWe're soliciting ideas for integrating extension information.20:06
annegentleWhich leads to the next topic, the extension documentation.20:06
annegentle#topic Extension documentation20:06
*** openstack changes topic to "Extension documentation"20:06
annegentleJorge posted to the mailing list last week, seeking feedback on http://http://docs.rackspace.com/openstack-extensions20:06
annegentlewhoops weird double http on that one :)20:06
annegentle#info seeking input on http://heckj.github.com/api-site-mock/20:07
annegentle#info seeking input on http://docs.rackspace.com/openstack-extensions20:07
annegentlefeedback on the Extensions site can be funneled to Jorge20:07
annegentleand for the API site, heckj mostly did the mockup20:08
annegentleI don't have much to add on those two. We are seeking more ways to get design feedback. The Dashboard team especially needs it, so we're working on inventive ways to gather input.20:08
annegentleOne idea is to hold a monthly review meeting via webinar-ish methods.20:09
*** jmckenty has quit IRC20:09
annegentleIdeally we'll loop in more of the actual audience for these sites than the devs of the sites, ya know?20:10
bcwaldonwon't most of the community that cares be on the mailing list?20:10
annegentle#info Looking for more ways to get reviews and input on designs.20:10
annegentlebcwaldon: I'm thinking of it as not all of Rackspace's customers who will migrate to the next Compute API aren't on the OpenStack list, for example.20:10
bcwaldonannegentle: very true20:11
bcwaldonannegentle: but should they be involved at this level?20:11
dubsquaredI think it's a fair ask to assume that a lot of the visitors to the site might be new to the project, or are just looking ffor one specific piece off info?20:11
annegentlebcwaldon: and HP's public cloud customers could give valuable input, that sort of thing20:11
bcwaldonannegentle: so you're kind of looking to build a customer advisory board for openstack20:11
bcwaldonand this could be one of the discussion topics20:12
annegentledubsquared: visitors to the API site certainly may be new to the project… but I'm envisioning they're just looking for "what can I GET on the Compute API"20:12
annegentlebcwaldon: maybe not that lofty a goal, but that would be awesome, to get more "real" customers reviewing sites, info, docs, and the Dashboard UI20:12
dubsquareddo you mean in that the context of "what can GET do for me?"20:12
bcwaldonannegentle: maybe we just approach who we think will be consumers of these resources and ask them?20:13
dubsquaredwhat can POST, what can …..?20:13
bcwaldonannegentle: I know a group here that might care20:13
annegentledubsquared: yep, really just a minimal reference site20:13
dubsquaredgotcha ...20:13
annegentlebcwaldon: that would be awesome if we found a small group that would like to poke at early designs, ya knkow?20:13
bcwaldonannegentle: sure, let me actually ask someone right now...20:13
annegentlebcwaldon: excellent, thanks.20:13
bcwaldonI'll get back to you after the meeting20:13
annegentledo you all think a webinar approach would work well for Dashboard UI?20:14
annegentlenearly all open source projects have the difficulty of shoe-horning dev processes into design process or the other way around20:14
annegentleso I do think it's an "audience" solution much of the time, meet devs where devs hang out, find users where users hang out.20:14
annegentleanyway, the next topic is discussing how to track bugs and content requests for openstack.org20:15
annegentle#topic Openstack.org site processes20:15
*** openstack changes topic to "Openstack.org site processes"20:15
annegentleSo the process now is to log a bug against the Launchpad openstack-manuals project and tag it "website"20:16
annegentleAnd even that process is new, so we can change it as needed. One thought is to have an openstack-org Launchpad project for bug and request tracking.20:16
annegentleAny preferences?20:16
annegentleSeems like we had a lot of excitement about the process surrounding the "security" page but now interest has died down a little? :)20:17
annegentleWe did the work on the security page, tracking it with this doc bug: https://bugs.launchpad.net/openstack-manuals/+bug/89801020:17
uvirtbotLaunchpad bug 898010 in openstack-manuals "Security page rev1 on openstack.org" [High,Confirmed]20:18
dubsquaredthat seems to be a reasonable method, as long as it's published as /the/ method :)20:18
annegentleWe had another bug come in about fonts used in a PDF from the openstack.org site, which we logged, tracked, and completed. So the process seems to work.20:18
annegentledubsquared: yeah, find a process and stick to it! :)20:18
annegentleI think Todd and I are fine with either, just a matter of setting up openstack-org on Launchpad and publishing that is "the" way20:20
annegentleAlso the name "openstack-org" matches the Github repo I believe.20:20
dubsquared#winning20:20
annegentlehee20:20
*** toddmorey has joined #openstack-meeting20:20
annegentlewelcome Todd20:20
toddmoreyHello!20:21
annegentleWe were just talking about setting up an "openstack-org" Launchpad project for tracking requests/bugs20:21
annegentletoddmorey: do you have any preference for the project name?20:21
toddmoreyI think openstack-org works20:22
annegentleYeah I like it.20:22
annegentle#action Anne to set up Launchpad project called openstack-org to track content requests and bug fixes with openstack.org site20:22
toddmoreyWe are also adding an expanded footer that has a small "feedback on this page" form for each webpage on the .org site. Those will then be filtered and added as requests/bugs into launchpad as appropriate20:23
annegentletoddmorey: oh nice.20:23
annegentle#info Feedback on this page form being added to each openstack.org page to add to Launchpad for tracking20:23
toddmorey(so that's a way for casual browsers to also provide quick insights to us without having to know about launchpad.) But we want to have it all end up in the same place and I like the idea of using launchpad.20:24
annegentleFor now, I think it's just Todd and I who have author privs on the openstack.org site, but maybe we can set up a "core" team like docs-core is set up.20:24
toddmoreyyes, and we'd like to get some translators going as well for a few key pages to start20:24
annegentletoddmorey: ah, nice segue into Translations!20:25
annegentle#topic Translation process20:25
*** openstack changes topic to "Translation process"20:25
annegentleMy very rough outline for a translation process uses Launchpad at the heart of it for storing files and assigning permissions for translators.20:26
annegentleThe process is so rough it's untested :)20:26
annegentleBut I did want to see if there's interest in pursuing such a process. Seems like there's not enough interest for a full-fledged process, but we can keep it around for when the time's right.20:27
annegentleEssex may be the release after which we translate docs, I'm not sure.20:27
annegentleSo I think I'll leave it at that - process outlined, no owners yet.20:27
annegentle#info Translation process is rough and untested, when sufficient interest arises we can test.20:28
annegentleNo actions at this time, I believe.20:28
annegentletoddmorey: though for specific openstack.org pages, I wonder if a post to the mailing list would suffice?20:28
annegentletoddmorey: a post to request help?20:29
toddmoreyYes, that's a good idea.20:29
annegentleokay20:29
annegentlelet's email a bit to pinpoint pages and such20:29
toddmoreyIt's a fairly simple process in the CMS, but once we have volunteers we could provide them instructions or do a quick demo20:30
annegentle#Action Anne to email Todd about specific openstack.org pages to translate20:30
annegentleOk, last item before open discussion is about work to move from Cloud Sites to Cloud Servers20:30
annegentle#topic Move docs.openstack.org from Cloud Sites to Cloud Servers20:30
*** openstack changes topic to "Move docs.openstack.org from Cloud Sites to Cloud Servers"20:30
annegentleSo, Rackspace hosts docs.openstack.org, and currently it's set up as a Cloud Sites account.20:31
annegentleThe Rackspace Doc Tools team is moving to Cloud Servers for the Rackspace content, and wants to move OpenStack content over too.20:31
annegentleI'm fine with it as long as the sys admin work is done by Rackspace, ensuring backup and assistance 24/7.20:32
annegentleSo the research item for the Doc Tools team is to ensure the same level of service.20:32
annegentleThe benefit is that we can automatically create the landing page20:32
annegentlerather than manually20:32
*** mattray has joined #openstack-meeting20:32
dubsquaredWho is going to own the support for the site after the move to cloudservers?20:32
toddmoreyright, me too. as long as the servers have owners and someone to call if docs isn't responding for some reason20:32
annegentledubsquared: the "research item" is "let's make sure we have a Managed Cloud Servers account :)20:33
dubsquaredword :)20:33
annegentleayup20:33
annegentleThis move will mean changes to Jenkins builds.20:33
annegentleI believe it's just a change to the FTP settings in one location.20:33
annegentleAnd probably an additional build job for this automatic landing page.20:34
annegentle#info In research stages for moving docs.openstack.org from Cloud Sites to Cloud Servers, ensuring same SLA as now.20:34
annegentleBasically I don't want calls in the middle of the night if the site goes down :)20:34
annegentleNo action right now, the actions are being taken by joesavak and the Doc Tools team.20:35
annegentleSo, that's it for December. Any items for open discussion?20:35
annegentle#topic Open discussion20:35
*** openstack changes topic to "Open discussion"20:35
annegentleA book I'm working on that I'm excited about is https://github.com/annegentle/openstack-manuals/tree/installdocs20:36
annegentleit's a new document for installing manually using Cloud Builders packages "diablo-final"20:37
toddmoreyyay!20:37
toddmoreythat's awesome20:37
annegentleand I just got Compute, Identity, and Dashboard working today.20:37
toddmoreyand badly needed20:37
annegentlewhew!20:37
annegentleThe merge back in is going to be NUTS. But it's a separate document so I think it'll go okay.20:37
toddmoreyOne thought for the website is the current "action item" for each project page is to push them to download code.20:38
annegentle#info New install/deploy document draft nearly ready for publishing20:38
annegentle#link https://github.com/annegentle/openstack-manuals/tree/installdocs20:38
toddmoreyWe'd like to instead point people to a getting started guide. This install guide sounds like the ticket.20:38
annegentletoddmorey: oh yes this is what we'd want to point them to20:38
jsavak\o - just joined20:38
annegentleHi Joe!20:38
jsavakhi!20:38
annegentleAny update on a Managed Cloud Servers account for docs.openstack.org?20:39
jsavaki have some info on the cloud servers move -20:39
annegentleexcellent20:39
jsavakyup - after speaking with monty - we are going to create them as regular cloud servers and add them to the puppet scripts for monitoring20:39
jsavakzns confirmed this approach20:40
annegentlejsavak: will Monty get the notifications on the monitors20:40
*** dwcramer has quit IRC20:41
jsavaknot sure. I'll confirm with Monty - but I think it would be whoever gets the jenkins alerts...20:41
annegentlejsavak: ok so it's more or less Jenkins that says "broke!"20:41
annegentlejsavak: and then is the CI team the "fixers?"20:41
jsavaki think so (or hope so)20:41
annegentlejsavak: that may not be acceptable… need to figure out if they're really up for an SLA or some sort of terms.20:42
jsavakand will confirm20:42
annegentleI have some trepidation :)20:42
jsavakyup. I think things will be more concrete with openstack foundations, but right now I have trepidation too.20:42
annegentleIs plan B for OpenStack to stay on an earlier snapshot of the build tools? Is there no branch for "we still use Cloud Sites?"20:43
*** davlap has quit IRC20:43
jsavakno branch was being planned for cloud sites support20:43
jsavakthe work hasn't started and i'm sure we'll discover a lot of the answers when we get David & Monty together20:44
annegentlejsavak: may need to at least visit and discuss that… seems like there are enough difference between the SLAs to look into options.20:44
annegentleWe can discuss more as you find out more, also.20:44
jsavaksounds good20:44
annegentleOk, we can wrap up if there's no other discussion items.20:44
annegentlethanks all for coming. We missed our usual "regulars" Joe Heck and Todd Deshane, but thanks y'all for coming!20:45
annegentle#endmeeting20:45
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"20:45
openstackMeeting ended Mon Dec 12 20:45:53 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-12-20.03.html20:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-12-20.03.txt20:45
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-12-20.03.log.html20:45
*** jmckenty has joined #openstack-meeting20:48
*** jmckenty has quit IRC20:56
vishyanyone here?21:01
bcwaldonbeep21:01
_0x44(ò_ó)ᕤ21:01
_0x44I only have 20 minutes though.21:02
dubsquared(╯°□°)╯︵ ┻━┻21:02
dubsquaredunacceptable ^^21:03
_0x4417 now.21:03
vishywell ok lets start21:04
vishy#startmeeting21:04
openstackMeeting started Mon Dec 12 21:04:23 2011 UTC.  The chair is vishy. Information about MeetBot at http://wiki.debian.org/MeetBot.21:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.21:04
vishy#topic First Nova Subteam Meeting21:04
*** openstack changes topic to "First Nova Subteam Meeting"21:04
vishywelcome everyone21:04
vishyfirst item on the agenda is figure out how we don't have to do this21:05
vishy#topic Best method of communication21:05
*** openstack changes topic to "Best method of communication"21:05
vishy#info Goals for communication:21:05
vishy#info Efficiently managing and targeting blueprints21:06
vishy#info Addressing shared blueprints and work across teams21:06
vishy#info Ensuring we aren't duplicating work21:06
vishy#info Ensuring we aren't blocking each other21:06
vishy#info Staying abreast of decisions made by teams21:06
vishy#info Staying aligned with the release schedule21:06
vishysoren sugested that this could all be done via email21:07
*** smoser has joined #openstack-meeting21:07
_0x44Should there be a sub-team mailinglist?21:07
vishythis seems like a possibility but we all have to be better at emailing updates21:07
vishy_0x44: based on the relative value of the other mailing lists I'm not sure it is necessary21:08
*** martine has joined #openstack-meeting21:08
vishywe could just hit openstack mailing list with a [subteam] heading if necessary21:08
vishyother options are:21:08
bcwaldonvishy: I like that approach21:08
vishyregular meetings (maybe biweekly)21:08
_0x44I personally think a lot of the db discussions would have been better done on a mailing list instead of an IRC meeting as the only people who attend have been myself, bcwaldon, and monsyne dragon.21:08
vishyshared place to put updates21:08
bcwaldonI bet we would get better participation through email anyways21:09
vishy_0x44: agreed.  I was trying to avoid the bikeshedding that sometimes occurs on the ml21:09
vishyby shrinking the commenters to people who are actually going to work on it21:09
vishybut I'm not sure if that really worked21:09
vishyi think it has been pretty effective for nova-api21:09
vishy(which had the most bikeshedding imo)21:10
bcwaldonI know there are people that work on the nova apis that don't come to nova-api team meetings, but I'm not sure if that's because they dont care about doing it right or what21:10
vishy#idea the team leads are probably enough to prevent bikeshedding21:10
*** jmckenty has joined #openstack-meeting21:10
bcwaldonvishy: yeah, as long as we empower the team leads enough to shut down bikesheders21:11
vishy#idea so we can return to ML discussions if the team leads are willing to keep the discussions focused and directed.21:11
_0x44vishy: +1 to that.21:11
vishydoes anyone have alternative proposals or other suggestions?21:11
bcwaldonvishy: how about we encourage email correspondence through the list and say meetings can be scheduled when its absolutely necessary21:12
vishybcwaldon: I like it21:12
bcwaldonbut to include those in other timezones, we absolutely need to shoot for email21:12
bcwaldonwhen I say *other*, I mean non-US timezones21:12
bcwaldonI would love to see if participation picks up from non-US timezones if we eradicate all these meetings21:13
vishyso cross team communication can include multiple headers or will be with the [subteam] heading if it applies to everyone21:13
vishyso If i'm emailing the team leads, I'm going to use the [subteam] heading, so eyes out for those21:13
_0x44I like that, especially since the person doing the most work on db clean up right now isn't able to attend the -db meeting.21:13
bcwaldonvishy: does it make sense to have team-specific mailing lists21:14
vishy#action vishy to email the list explaining use of the list by subteams.21:14
bcwaldonI know we've already gone back and forth on that one21:14
vishybcwaldon: no, we have those and i think it is not necessary21:14
*** joesavak has joined #openstack-meeting21:14
bcwaldoncan you explain why21:14
vishybcwaldon: my last email suggested using [api] header for example for nova-api related discussion21:14
vishybcwaldon: it isolates information21:14
bcwaldonkind of like the meetings do21:15
vishybcwaldon: people can ignore messages they don't care about21:15
bcwaldonso what's the point of having logical teams on launchpad?21:15
bcwaldonI've got ~50 people on nova-api that have never said a word21:15
vishybcwaldon: perhaps there isn't a lot of value21:15
vishybcwaldon: aside from having a team lead21:15
bcwaldonthat's what I'm thinking21:15
vishybcwaldon: I don't know that we need to remove the teams though21:16
vishywe can just shut down the ml after everyone has switched over to using the main ml21:16
bcwaldonI think what's most important here is that people that care about different topics can have a way to communicate with one another21:16
vishybcwaldon: actually21:16
vishybcwaldon: the subteams on launchpad are great for tracking blueprints21:16
bcwaldonvishy: good point21:16
vishybcwaldon: so i think they still have value21:16
bcwaldonabsolutely21:16
vishy#info subteams will not use separate mailing lists, but still have value for blueprint tracking21:17
vishyok next topic21:17
*** jsavak has quit IRC21:17
vishy#topic Blueprint management and targetting21:17
*** openstack changes topic to "Blueprint management and targetting"21:17
vishy#info we need to get better at assigning and targetting blueprints21:18
vishythere is a lot of stuff still assigned to teams with no actual person assigned21:18
vishyhow can we improve that21:18
vishysuggestions?21:18
bcwaldonso the problem I see a lot on the project is that we're great at reacing to what features are proposed to be added21:18
bcwaldonbut when we have a feature that a specific company isn't driving, it just sits21:19
bcwaldonsince we don't have resources to allocate to those kinds of features21:19
vishybcwaldon: I agree.  Unfortunately a lot of the stuff is important to others21:19
vishybcwaldon: for example separate-volume-api21:19
_0x44I have to run21:19
bcwaldonbye _0x4421:19
bcwaldon!21:19
_0x44Sorry21:19
vishy_0x44: ok thx, will send out update21:20
bcwaldonvishy: so we're back to more of a technical-debt problem21:20
bcwaldonhow can a product organization prioritize technical debt21:20
bcwaldonwhen there are so many tempting features21:20
vishybcwaldon: I don't think there are that many tempting features left21:20
vishybcwaldon: we don't have that much feature work targeted21:21
bcwaldonmaybe at this point21:21
bcwaldonthis feeling has been around a while21:21
bcwaldonI'm digging down deep21:21
vishybcwaldon: so i feel like we should all be moving to technical debt, cleanup, bugfixing, perf testing21:21
bcwaldonvishy: absolutely!21:21
*** jmckenty has quit IRC21:22
*** jmckenty_ has joined #openstack-meeting21:22
vishybcwaldon: looks like it is me and you now21:23
bcwaldonjust the two of us21:23
bcwaldonwe are nova21:23
vishyhaha21:23
bcwaldonso yes, we do need to get better at assigning blueprints21:23
bcwaldonhow about I go over the nova-api blueprints and send out an email to the team21:24
vishythat would be cool21:24
vishyI will take a look at the state of the other ones21:24
*** dwalleck has quit IRC21:24
bcwaldonok21:24
bcwaldonwhat other problems can I solve for you21:25
*** dwalleck has joined #openstack-meeting21:25
vishyi guess that is it21:25
bcwaldonactually21:25
bcwaldonlet me ask a question21:25
vishy#action bcwaldon to clean up nova-api blueprints and email about targeting21:25
bcwaldonfor the openstack-api-ssl bp, there has been a review in gerrit forever21:26
vishy#action vishy to look over other blueprints and send out specific email to [subteam] highlighting issues21:26
bcwaldonhow would you suggest we move forward with that21:26
vishybcwaldon: is that an hp one?21:26
vishysometimes you have to kick them21:26
vishyi kicked them about the vm state one and they updated it21:26
bcwaldonvishy: we're in a public forum!21:26
bcwaldonok, I'll ping them21:26
bcwaldondo you want to be my assignee for separate-nova-volumeapi21:27
mtaylorvishy: can I kick anybody for you?21:27
vishybcwaldon: I guess it should be me, but I want to talk with you about where exactly we should move the parts21:27
vishybcwaldon: we discussed it briefly but i will probably bug you about it more21:27
bcwaldonyeah, I need to talk to you about adminapi21:27
bcwaldonwe can hop on skype21:28
vishylets finish this meeting21:28
bcwaldonyes21:28
vishy#topic open discussion21:28
*** openstack changes topic to "open discussion"21:28
vishyany questions comments?21:28
vishythoughts?21:28
vishycomplaints?21:28
bcwaldonmtaylor: this is directed at you21:28
vishyis anyone even here?21:28
vishy:)21:28
bcwaldonjust the two of us21:28
mtayloro/21:28
bcwaldonwe can make it if we try21:28
* mtaylor is just lurking21:29
vishy#endmeeting21:29
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"21:29
openstackMeeting ended Mon Dec 12 21:29:18 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-12-21.04.html21:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-12-21.04.txt21:29
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-12-21.04.log.html21:29
zuli was lurking as well21:30
mtaylorzul is a lurker21:30
zulamongst other things21:30
*** davlap has joined #openstack-meeting21:32
*** jmckenty_ has quit IRC21:33
*** dprince has quit IRC21:46
*** GheRivero_ has left #openstack-meeting22:04
*** martine has quit IRC22:08
*** joesavak has quit IRC22:16
_0x44 (╯°□°)╯︵ ┻━┻22:50
novas0x2a|laptopcannae lurk under de tables22:51
dubsquaredhey hey...22:51
dubsquaredcalm down… ┬┬ ノ( ゜-゜ノ)22:51
*** novas0x2a|laptop has quit IRC22:51
*** nati2 has joined #openstack-meeting22:52
*** novas0x2a|laptop has joined #openstack-meeting22:52
*** mdomsch has quit IRC23:01
*** pvo has left #openstack-meeting23:08
*** pvo has joined #openstack-meeting23:08
*** rnirmal has quit IRC23:12
*** nati2 has quit IRC23:12
*** nati2 has joined #openstack-meeting23:13
*** davlap has quit IRC23:15
*** nati2 has quit IRC23:18
*** nati2_ has joined #openstack-meeting23:18
*** mattray has quit IRC23:20
*** AlanClark has quit IRC23:27
*** AlanClark has joined #openstack-meeting23:27
*** nati2_ has quit IRC23:30
*** dubsquared has quit IRC23:45

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!