Tuesday, 2018-03-06

*** mriedem has quit IRC02:03
*** liujiong has joined #openstack-tc02:34
*** harlowja has quit IRC03:18
*** chkumar246 is now known as chandankumar04:59
*** harlowja has joined #openstack-tc05:12
*** ykarel has joined #openstack-tc05:44
*** ykarel has quit IRC06:19
*** harlowja has quit IRC06:29
*** chandankumar has quit IRC06:35
*** chandankumar has joined #openstack-tc06:36
*** liujiong has quit IRC06:50
*** liujiong has joined #openstack-tc06:50
*** liujiong has quit IRC06:50
*** ykarel has joined #openstack-tc07:50
*** cdent has joined #openstack-tc08:45
openstackgerritMerged openstack/governance master: Retire horizon-cisco-ui project  https://review.openstack.org/54180908:45
openstackgerritMerged openstack/governance master: replace tracking sections with storyboard links for rocky goals  https://review.openstack.org/54513008:47
openstackgerritMerged openstack/governance master: Update status of 'API deployed in uwsgi' goal  https://review.openstack.org/54548408:47
openstackgerritMerged openstack/governance master: [rally] Add a separate repo for OpenStack plugins  https://review.openstack.org/54582708:49
openstackgerritMerged openstack/governance master: Add openstack-ansible-nspawn.* to OpenStack-Ansible  https://review.openstack.org/54609108:49
openstackgerritMerged openstack/governance master: Add puppet-monasca to Puppet OpenStack  https://review.openstack.org/54619008:49
openstackgerritMerged openstack/governance master: Add openstack-ansible-os_panko to OSA deliverable  https://review.openstack.org/54657208:49
openstackgerritMerged openstack/governance master: Add roles into openstack-ansible deliverable  https://review.openstack.org/54657508:49
openstackgerritMerged openstack/governance master: Add Glance completion info for policy in code goal  https://review.openstack.org/54698108:52
* ttx grabs coffee08:58
ttxtc-members: good morning09:05
ttxI expect most to still be in post-snowpenstack recovery09:06
* cmurphy finally got home yesterday afternoon after getting stuck in Amsterdam overnight :(09:07
ttxQuick thing I wanted to mention: the OpenStack Foundation is likely to join the Open Container Initiative (OCI) to show its support for the spec (which is used by Kata Containers but also by OpenStack LOCI). Let me know if you have questions on that09:08
ttxAlso PowerStackers will be approved on Friday unless new objections are posted09:09
cdentI'm sort of here, good morning everyone.09:12
cdentJoining OCI seems reasonable, but I worry a little bit about perceptions that the infra side of the house is being de-emphasized (emphasis on the "perceptions").09:13
ttxcdent: I think that should be fixed by the messaging around open infrastructure, which paints the overarching story09:16
cmurphyi've also noticed a perception that the foundation is chasing the new container hotness rather than sticking close to its infra roots09:16
cmurphyso yes better messaging would be good09:16
ttxIn that case it's just supporting the OCI standard, which we happen to leverage in LOCI (our OCi container packaging for OpenStack)09:17
ttxand that Kata Containers is compatible with.09:17
ttxbut yes I can see how that needs to be counterbalanced09:17
cdentI think it is a confluence of factors, none of which in themselves is a big deal, but in a stressed out or paranoid mind feels differently:09:18
cdentthe ptg is too expensive to continue09:18
cdentlet's do kata09:19
cdentlet's do oci09:19
cdent"my presentation at summit is far more likely to get accepted if it is about nfv or containers"09:19
cmurphywhere did "the ptg is too expensive to continue" come from?09:19
cdentboard meeting09:19
cmurphythat is new to me09:19
cdentthey decided to punt on that one09:19
cmurphyi guess i'll listen in on the next board meeting then09:20
cdentbut yeah, never ever do the board meeting on a ptg day09:20
cmurphyfor real09:20
ttxcmurphy: we definitely need to find a more sustainable model, but there is also the question of inclusivity. Lots of complaints from Chinese contributors that they are unable to attend09:20
cdentI continue to think representation of individual daily developers in board and foundation activities is way low09:20
cmurphyttx: due to expense?09:22
ttxWhich is why there are two options on the table: continue as separate but with some alternate funding model (like increased ticket price), or co-locate with summit again so that it's less travel09:22
ttxcmurphy: I feel like money is not the only factor. Having to ask for visas every 3 months is not fun09:23
cmurphyoh right :/09:23
ttxWe are preparing a dev survey on the topic09:23
* cmurphy reminded of her privilege09:23
ttxnot just PTG attendess, all -dev09:23
cdentI suspect the power of the rumor mill is being underestimated09:24
ttxI think if we did not receive that many complaints against the separated event, the question of continuing PTGs would not even be on the table09:24
cdentIs there a clear picture of how those complaints divide up amongst  regular contributors, casual contributors, managers of contributors, companies wth contributors, $other?09:25
ttxBUT that all may be an illusion. If people need to meet regularly to do their work, they will. Unofficial meetups or PTG. Which will always screw up some portion of contributors09:25
* johnthetubaguy wonders in late and reads scrollback09:27
ttxcdent: I received that feedback from regular Chinese devs in Sydney09:27
ttxnot their management... but I know others at the Foundation received that feedback from managers as well09:28
ttxI'd say from significant/intermediary-sized Chinese contributing companies09:28
ttxanyway, let's collect data first09:29
ttxcmurphy: at the board meeting the conclusion was that we should definitely organize the next noe, and make the call for 2019 by Vancouver joint meeting.09:29
cdentttx: I was meaning about the "separated event", was that what you meant?09:30
cdentI think the PTG is the only openstack event I've experience in the last 3.5 years that has felt like community09:30
cdentand the only one that actively drives cross project work09:31
ttxcdent: yes, those contributors were advocating for co-location with summit again09:31
johnthetubaguyttx: +1 on waiting for more data. I certainly heard complaints about the expensive of it all since it was introduced09:31
cdentthe expense concern, to me, is bogus. How much money are companies making off the back of contributor labor?09:31
cdenttravel difficulties and amount is certainly a thing to think about, though09:31
ttxcdent: it's bogus because the event makes you more productive, yes09:31
ttxBUT unfortunately not many companies think sanely when it comes to money09:32
johnthetubaguycdent: I am curious how it feels different to the design summits?09:32
ttxWith design summits we traded productivity for not engaging with the rest of the community09:32
johnthetubaguyttx: +1 on the lack of sanity, I found it was more a lack of clear precedent, everyone else manages without the travel etc...09:33
cdentjohnthetubaguy: I'm not sure I can explain that in clear terms. It just does. :)09:33
ttxso yes we could be productive, but by isolting ourselves from the others09:33
johnthetubaguyttx: actually the whole opps vs dev sessions is coming back to me now09:33
ttxcdent: the calculation should be obvious. Attending the pTG makes you at least 10% more productive for the rest of the cycle. Which has an obvious RoI09:34
johnthetubaguycdent: thinking back, it is like the midcycle, but with friends and not isolation, I think my memory was playing tricks on me there09:35
ttxSending a team of 10 people to the PTG is a better move than keeping an 11-people team at home09:35
cdentYeah, midcycles have never been a positive experience for me09:35
ttxUnfortunately travel budgets and sponsoring budgets don't work that way09:35
johnthetubaguytried so many ways to ring fence travel budget, every one fails, and its always considered optional, but oddly not for sales people...09:38
cdentjohnthetubaguy: yeah, the travel budget for sales thing is fun09:39
johnthetubaguyit feels a lot of this is about lack of precedent, we are strangely diverse in leadership, etc.09:43
johnthetubaguythe academics seem to get the idea of going to talk to others about what we are doing and getting feedback and new ideas09:43
* cdent nods09:44
*** dims has quit IRC09:45
*** dims has joined #openstack-tc09:49
cdentA survey of "attitudes to the ptg" will be useful, especially if lots of people respond.09:49
cmurphyanyone thinking of attending https://events.linuxfoundation.org/events/open-source-summit-europe-2018/ ? they are having "open collaboration conference" and "diversity empowerment summit" tracks in their CfP which sounds relevant to this discussion and the OpenStack TC in general09:50
cdentThe other thing I think we ought to consider is more active interaction between the TC and the foundation's planning. I'm not sure what that would look like though. I'd like to see more explicit info sharing rather than tacit.09:50
ttxAgreed, which is why I'm raising the OCI topic here :)09:50
cdentcmurphy: sounds interesting, timing may be problematic for me09:51
cdentttx, yes, thanks for that09:51
ttxcmurphy: been considering it yes09:52
cdentI think there should be more PTGs and less conferences :)09:54
ttxEmilienM: hola!09:56
cdentEmilienM: morning09:56
cmurphyI feel like I recall the selling point of having PTGs was that devs would no longer have to attend the summits, which did not end up being the case at all it feels like09:56
cmurphyif there was no forum at the summit then maybe the goal of having less travel would actually be achievable with PTGs09:57
cmurphyEmilienM: I hope you are not still in Dublin09:57
ttxNah, the selling point is that devs present at summits would be able to engage and share with others09:57
ttxrather than be holed up in a room with their team for 3 days09:57
EmilienMcmurphy: thanks! I made it to my parent's place09:58
cmurphyEmilienM: oh good :)09:58
EmilienMI'm currently baby sitting a 3 weeks old baby09:58
EmilienMwhile trying to get some work done. But he's not helping :-P09:59
ttxWe also said that it changed dev travel to summit from a MUST to a SHOULD09:59
cdentttx we say that's the selling point, but I don't know that everyone feels that way (which is always the problem)09:59
cdentttx should is bogus though: if you want to be relevant (for your employer or yourself) you need to be there, because other people will be, and they will be making decisions (OMG) without you!10:00
johnthetubaguycdent: I felt disconnected after not being in syd, although that wasn't strictly budget reasons, more family reasons10:00
cdentjohnthetubaguy: exactly. that disconnectedness is difficult to manage given the modes of activity in some of the projects10:01
johnthetubaguyI mean lots of people make heroic efforts to document what happened, but there is nothing like being in the discussion10:01
* johnthetubaguy nods10:01
cdentif we want to save money we need to change the modes of behavior10:01
cmurphyit seemed like a "should" before, or it still feels like a "must" now, but somehow it doesn't feel like the value of being there has changed10:01
cdentcmurphy: yeah, agree10:02
johnthetubaguy+1 both of you10:02
cdentthe old modes were based on a professionalization of openstack development. that mode is still true for some (me for example) and still true for some projects (nova for example) but is not sustainable as is10:03
cdentOr rather, in order for it to be sustainable, contributing companies need to step up with $$10:04
* cdent checks on chickens10:06
*** rosmaita has joined #openstack-tc10:29
* persia ponders the effect of having PTG in China: reverses the visa requirements, which may offer perspective11:52
cdentwould be interesting. But I'd hope that if were exercising any kind of political attitudes in our PTG destinations we'd avoid China (and the US too)11:54
cmurphyI think there are countries that are not China but also easier for Chinese residents to travel to, Singapore for instance looks like it has an easier visa process for Chinese passport holders12:06
persiaI object to your use of "political" in that sentence, but agree with the intent I read into the words.  Also, US tax codes make it hard for US entities to pay for conference attendance unless they can demonstrate that the conference is as likely to happen inside the US or outside the US.12:07
persiacmurphy: Meeting in a neutral country has value, but meeting in a country with a complex visa process for many of the folk who often attend PTG may help build shared understanding of the issues.  I know of one person whose inconvenience by snow in Dublin was related to a requirement to leave the country no later than Saturday, adding more stress than for many who might just need to rebook flights or hotels.12:08
cdentpersia: how did you interpret my use of the term?12:10
cmurphyI can agree in principle on the benefits of reversing perspectives (Sydney was great for that) but practically I think that's a hard sell12:11
persiaSydney was terrible for nearly everyone: nearly as much hassle for most folk in asia as for folk in the americas.  Excellent for australians.12:12
persiacdent: I read your statement as encourgaging reduction in economic incentives as a means to express opinion about the practices of specific sovereign states.  In my glossary, "political" is reserved for things related to policies that apply to polities.  As many of us are not properly members of a polity involved with either of the sovereign states you mention, I don't think our economic expression of opinion should use that term.12:14
cdentah, hmm. I wasn't really thinking of it in terms of economic incentives or expressions more as a (mostly ineffectual but still symbolic) vote of no confidence, thus an expression of power (albeit limited), thus "politics".12:16
persiaFor those of us that are properly within the polity for those sovereigns, it is very likely that our personal economic influence is directly related to inflows, thereby causing us to be personally wounded by such economic action.12:16
cdentI tend to use politics as an overriding term for anybody's expression of power, not just polities as polity, as you say, are non-inclusive12:17
persiaFor me, politics is the art of compromise.  Power is an expression of might.  In practice, one can have (limited) power by controlling the policies by which might is expressed, which can be done through discussion and compromise with those to whom power has been delegated.12:17
persiaI do not believe we can effectively practice politics if we do not appreciate this distinction.12:18
cdentI expect my interpretation is overly informed by critical theory12:18
persiaAnd, as a collaborative distributed community who compose both code and policy regarding how the world consumes our output, I think it is unfortunate when we don't practice politics.12:18
persia(but most of the time we seem to do reasonably well, and most of our policies support active political engagement by anyone in the community, which is promising)12:19
cdent(and in that context, I'm a radical in the "get to the root of" definition)12:19
persiaMy definitions are etymologically defensible, but yes, most theory is written from the perspective of those attempting to cause change, which implies they seek power, so it is convenient to conflate the terms.  Broadly speaking, in a policy-controlled environment (follows the rule of law), politicians are more effective at providing minor change (serving constituents), which makes the narrative "politicians are the problem" useful for those who12:23
persiaare more practiced in managing segmented communications to multiple audiences than in politics, as it provides them a base from which to develop sufficient constituency to overthrow the prior power brokers.12:23
dimsEmilienM : awwwww12:40
*** cdent has quit IRC12:44
*** cdent has joined #openstack-tc13:12
*** cdent has quit IRC13:33
EmilienMdims: :) (not mine though)13:37
dims:) good to practice!13:50
*** cdent has joined #openstack-tc13:52
fungiseems i missed another excellent office hour, but i do not regret sleeping14:04
cdentgood life choices14:06
* dtroyer finally enjoyed a sleep cycle that matches the sun cycle14:14
dtroyerI think one of the things we need to keep in mind is the balance of the complaints for any given decision (such as PTG vs Summit or release cycle length) is that good compromise will have nearly everyone unhappy about something.  And those that are happy aren't as vocal14:15
persiaBeing unhappy with the status quo is not necessarily the same as having a constructive opinion towards effective change.  At least for me, cancelling PTG would avoid making people feel excluded, but at the cost of avoiding making people feel included.14:20
mugsieAlso, on the PTG, if we cancel it, I would bet that a large amount of projects will start midcycles again, which will be just as exclusionary as the PTG.14:26
mugsieand adding a week to the forum is probably a non starter for most people14:26
dtroyermugsie: generally I agree, but for those with visa complications that is one event rather than two and may be a better situation.14:28
persiaI actually like that idea.  I'm not sure I have the stamina for two weeks, but it simplifies scheduling.14:28
mugsiedtroyer: yeap, for visas it is probably a win win14:28
cdentI barely have the stamina for 1 week14:28
cdentbut I'm a delicate flower14:28
dtroyerI've wondered if we could do 3 days of non-overalpping dev-sessions and a 3 day conference14:29
mugsiebut 2 weeks away from home / family / $responsibilities (and companies paying for staff to have a weekend off in $city) is a lot to ask14:29
dtroyerbasically make 2 4-5 day trips and 2 6-7 day trips into 2 8-10 day trips?14:29
dtroyerit is a lot14:30
dtroyeror maybe we do the combined once a year?14:30
mugsiecdent: you are not alone14:30
dtroyerand then 2 separate events14:30
mugsieI think that would cause us to look at the length of a cycle again, wouldn't it?14:30
persiamugsie: Companies paying for weekend in $city can often be negotiated into companies not providing time-in-lieu for weekend flights.14:31
mugsiepersia: I know my company tries to do that anyway, regardless of the situation14:31
* mugsie had to negotiate that out of his contract14:32
*** mriedem has joined #openstack-tc14:43
*** hongbin has joined #openstack-tc14:44
TheJuliagood morning everyone14:46
zanebmuch scrollback. so jetlag.14:47
mugsiezaneb: yeah, the jet lag is killing me14:52
zanebmugsie: :P14:52
pabelangerOur polling for S release names closed yesterday. I'm going to be looking this morning on the next steps15:17
pabelangerttx: fungi: I think the foundation looks over the suggestions first, but not sure who or how to do that step15:17
zanebmugsie: thanks for updating the interop testing resolution. I have comments :)15:20
cdentpabelanger: there are some excellent choices in there15:20
* cdent is shocked, SHOCKED, by zaneb 15:21
* zaneb fears he is becoming typecast15:21
pabelangercdent: yah, it seems to have went well15:22
cdentzaneb: I jest. I, at least, very much appreciate your comments15:23
zanebpabelanger: how does "Words that describe the feature should not be included" apply when all of the words describe a feature? :D (e.g. Seestraße == Lake Street)15:24
cdentShelhaus makes me giggle15:27
pabelangerzaneb: indeed15:28
ttxzaneb: separate words that describe the feature should not be included ?15:28
ttxBasically that rule was so that you would not include "Street" is "Icehouse Street"15:29
ttxI think we said ASCII set though15:30
cmurphyin german the words all run together15:30
cmurphyso we'd have to chop off straße even though it's part of the word15:30
cmurphyß can be converted to ss though15:31
ttxIch spreche sehr gut Deutsch15:32
ttx(Ich glaube)15:32
zanebttx: schön15:33
* cmurphy will lol if S-Bahn is chosen15:34
ttxthat '-' will likely disqulify it15:35
ttxName must be composed only of the 26 characters of the ISO basic Latin alphabet15:35
SamYaplei missed the PTG chats above... but everyone ive talked to prefers the ptg to the design summit, and a large porition of them only go to the PTG not the summit (unless they have a talk)15:37
SamYaplei also love the PTG because we get so much accomplished. both talking about new ideas and coding15:38
SamYaplei would be sad to see it go back to the old way15:38
cmurphythe keystone team gets a lot out of all four events actually15:40
cmurphybut the PTG more so15:40
mugsiezaneb: thanks for the comments - they all make sense15:42
mugsieBut overall it looks like what we talked about right?15:42
*** cdent has quit IRC15:46
fungipabelanger: in nthe past we've run the election first and then foundation legal/marketing have crossed out the first n choices as unworkable, leaving is with the n+1 most consensual choice from the ranked poll15:53
pabelangerfungi: okay, that makes sense.15:53
fungibasically, we have one poll either way, but the research needed to rule out names is expensive so polling first cuts down that cost15:54
fungias they only have to research the top picks rather than every single option15:55
pabelangerokay, I'll now look into public polling software over CIVS15:57
dhellmannpabelanger : I think we can still use civs as long as we make the poll public instead of feeding it a list of foundation member emails15:58
dhellmannI thought that's what we said we'd do, for simplicity15:58
ttxyes, that was the suggestion, use CIVS public polls15:58
pabelangerokay, that makes sense15:59
ttx"A Condorcet election is held to rank the names. The poll will be public, with the voting URL communicated through OpenStack mailing-lists..."16:00
ttxSee https://governance.openstack.org/tc/reference/release-naming.html16:00
pabelangerAck, see that now16:00
zanebmugsie: yes, +1 for the general direction16:03
dimsoff-topic : fyi, https://landscape.cncf.io/16:30
mugsiehttps://landscape.cncf.io/selected=zuul :'(16:33
pabelangerseen that16:34
mugsiehttps://github.com/Netflix/zuul/issues/315 made me even sadder16:35
*** ykarel has quit IRC17:14
*** cdent has joined #openstack-tc17:22
*** ykarel has joined #openstack-tc17:43
*** dtantsur is now known as dtantsur|afk18:00
*** rosmaita has quit IRC18:16
*** ykarel has quit IRC18:18
*** harlowja has joined #openstack-tc18:39
*** rosmaita has joined #openstack-tc19:20
*** rosmaita has quit IRC19:23
*** portdirect has quit IRC19:41
*** portdirect has joined #openstack-tc19:41
*** david-lyle has joined #openstack-tc20:08
*** david-lyle has quit IRC20:15
dmsimardyeah it's not like we didn't try20:17
dmsimardmugsie: oh wow I didn't see Netflix's Zuul on there though20:18
*** david-lyle has joined #openstack-tc20:39
*** david-lyle has quit IRC20:52
-openstackstatus- NOTICE: The infrastructure team is aware of replication issues between review.openstack.org and github.com repositories. We're planning a maintenance to try and address the issue. We recommend using our official supported mirrors instead located at https://git.openstack.org.21:19
*** david-lyle has joined #openstack-tc21:24
*** bmace_ has joined #openstack-tc21:33
mordredmugsie: https://github.com/cncf/landscape/pull/315 https://github.com/cncf/landscape/pull/316 https://github.com/cncf/landscape/pull/31721:40
*** david-lyle has quit IRC21:41
*** david-lyle has joined #openstack-tc21:51
*** bmace_ has quit IRC21:57
dmsimardRe: PTG/Summit split: something I haven't seen mentioned here is that prior to the split we had a design summit *and* an ops summit. Having devs and ops meet has a lot of value and I feel we kind of lost that with the PTG.22:02
dmsimardOps are not really incentivized to go to the PTG and devs aren't incentivized to go to the (now split) ops meetup.22:03
persiaFor me, ops summit is largely replaced with the expanded and formalised "ops midcycle".22:04
persiaAnd the ops<->dev stuff seems to be scheduled at forum, in parallel to the product tracks.22:04
persiaWhereas my memory of the old model was that ops summit was just before design summit, and ops would provide feedback into devs at that time.22:05
persiaI also tend to see a good mix of ops, devs, product folk, and others at the larger Days, when I manage to attend.22:05
cmurphythere were ops at the PTG, I'd like to see more of that22:06
cdentOne option could be to make the PTG the TG (as technical gathering) and have it be "people who hack on openstack"22:08
cdentthat addresses one of the main reasons for creating the PTG (at least as I recall it): stop making me split my attention with marketing22:09
persiaI like representatives of operator orgs at PTG, but the vast majority of such representatives I encountered were also devs, which I think is appropriate.22:09
persiaWhereas when I go to ops events, there are also representatives of orgs that have no dev component (so might be lost at PTG), who talk about other things.  Often these conversations enable those who don't attend PTG to successfully argue for funding to be devs.22:10
*** ykarel has joined #openstack-tc22:10
persiaI would be opposed to having folk at PTG who represent promotional or business interests of operator organisations: I think that would change the conversation from "two people are working on something and sit down and do it" to "my company and your company want something: how do we partner".22:11
persiaNote that I think all the above applies to vendor organisations, although I think the model changes haven't caused them to be as far from the rest of us as may be described for operators.22:12
mriedemwe need operators at the ptg22:13
*** david-lyle has quit IRC22:13
mriedemfrequently, "sure, we could do x, but how are operators doing/using foo today? if we did x, what is the pain to ops or the upgrade strategy?"22:13
mriedem^ comes up22:13
mriedemmy guess is, ops need devs at the ops meetup22:14
mriedemi sat in the public cloud wg meeting on monday(?) at the ptg and i was the only dev i think, the rest were mostly operators, and i think it really really helped to chug through their big spreadsheet of doom that they've pushed for the last 18 months22:14
dhellmanncdent : the attention split wasn't just between hacking and marketing for me.22:15
mriedemfewer devs are going to the summit22:15
dhellmannI thought ttx said it well when he said the PTG is for teams to look inward and the Forum is for teams to look outward22:16
mriedemfirst 2 days at the ptg are totally outward looking things for teams22:16
mriedembeing cross-project22:16
dhellmannmriedem : only if you consider cross-project teams not teams22:16
mriedemthursdays have become the defacto cross-project vertical days at the ptg too22:16
mriedemdhellmann: not following22:17
dhellmannmriedem : if their focus is on things they are doing, they are looking inward22:17
dhellmann"what are we doing this cycle?" vs. "what are all of the other demands and inputs coming our direction?"22:18
mriedemas far as i can tell, monday and tuesday at the ptg is nearly the exact same as the "ops summit" first 2 days of the design summit22:18
mriedemexcept less structured since we don't do 40 minute blocks22:18
persiaI think 90 minute blocks are better than 40 minute blocks for most of the discussions that we want to have anyway.22:19
* mriedem realizes he has stepped into the age old ptg quagmire and tries to get out22:19
persiaEspecially as projects can elect to schedule two (or more) short items in a block if they fit.22:19
persiamriedem: It's sticky for a reason :)22:19
dhellmannI think we could have both types of focus in a single event, but we would have to be very careful with scheduling22:20
dhellmannwe could probably even have it concurrent with the marketing stuff, but that would likely result in spending less time on any of the things we do at the PTG or Ops meetups now22:21
persiaI do not believe having it concurrent with Expo would work for folk funded by vendors.22:21
persiaWorks *great* for operators, second-tier support folk, consultants, etc.22:22
mugsiemordred: cool. I was wondering about splitting up OpenStack components on that diagram, but figured it might be too much22:22
mriedemdhellmann: what you just said sounds like you described the summit before the ptg happened22:23
persiaWhereas Forum+Expo mostly works because when vendor-funded folk have to go talk up product, it doesn't mean the entire project in which they are involved goes in a direction they didn't expect (at least not without another chance to be involved in the discussion a couple months later).22:24
cdentLet's have the old summit but without presentations, the marketing floor, customer meetings or managers22:24
cdentand call it "PTG"22:24
dhellmannmriedem : yeah, I'm thinking back to San Franciso (I think?) where we had a couple of days of marketing, 1-2 days of overlap, and a couple of days of just design summit22:24
dhellmannthat wasn't ideal, but it was better than 100% overlap22:24
persiacdent: +122:24
mriedemi believe i was in diapers when that happened22:25
mriedemATL was my first summit22:25
dhellmannfolsom was a lot smaller in terms of # of people, too22:25
dhellmannI forget the argument for changing the schedule. Maybe teams felt like the number of days they had weren't enough?22:26
persiadhellmann: I think we tried to follow that model until Paris.  After that, there was too much demand for time to do the workshops, give the presentations, and keep the expo open longer for more meetings.22:26
dhellmannthat seems likely22:26
persiaExpo+Forum needs 4 days, which makes the entire event much more than a week to do user discussions, then marketing, then developer discusions22:27
persiaI think it doesn't quite need two weeks, but it is close.22:27
dhellmannhaving to meet with customers and partners privately (vs. in the design summit or forum sessions) is the biggest drawback I see to combining the events22:27
persiaUnavoidable if we seek funding that way, and we're unlikely to upset the economic model in the next year enough that customers just hire devs to do stuff directly.22:28
mriedemif the ptg is killed, i'll be giving talks, sitting with customers and managers at the summit (as i already have to do today) and then whatever forum sessions i can attend (with only videos later for the talks i actually *want* to attend), and then no deep dive on things to actually get done for a cycle22:28
mriedemand midcycles are likely dead as a result of the ptg killing them22:28
dhellmannyeah, I think a lot of our high-level contributors will have that same issue22:28
persiamriedem: I strongly suspect that would be true for enough of your team that someone would suggest you all fly to $city for a few days (meeting rooms provided by $org), and sort it out.22:29
dhellmannfwiw, we need to make sure our managers hear these arguments from us, not just the foundation22:29
persiaFor those of you funded by vendors, if you have trusted customers who are *also* contributors, having those folk pass the message through professional services can also be helpful.22:30
*** david-lyle has joined #openstack-tc22:30
persiaAlong the lines of "We were delighted to work with $person at PTG: they really helped us get some of our core concerns understood by $team.  We're looking forward to the next one, and hope you can send more folk."22:30
* persia may have used such testimonials to fund travel in the past, and hopes the same model may be useful to others22:31
dhellmannpersia : good idea22:36
smcginnisFWIW, I was just encouraging a couple of actively involved operators last night to attend at least the first two days of the PTG. Assuming we still have them.22:37
smcginnisNot that I want it, but if we did have to kill the PTG, having a summit with 3 days for presentations and marketing type activities and 3 days for forum/design summit with a day of overlap would be better than nothing.22:39
smcginnisThe key part being trying to avoid as much of the overlap as possible.22:39
smcginnisHaving a 3 day summit already seems strange. Especially when your travel to get there and back takes 3 days.22:39
*** david-lyle has quit IRC22:40
smcginnisSo even if we don't kill the PTG, I wouldn't mind an extended Forum.22:40
*** mriedem is now known as mriedem_afk22:41
dimsright smcginnis22:42
cdentsmcginnis for exalted leader22:45
smcginnisHah :P22:48
cdentoh my, look at the time22:50
smcginniscdent: It is awfully late for you. And you can't even claim jetlag.22:52
cdentI was writing actual code and got distracted22:53
cdentbut yeah, nighty night22:56
*** cdent has quit IRC22:56
openstackgerritGraham Hayes proposed openstack/governance master: Clarify testing for interop programs  https://review.openstack.org/52160222:56
mugsiezaneb: ^ should have incorporated all your comments22:57
*** ykarel has quit IRC23:07
*** david-lyle has joined #openstack-tc23:26
*** david-lyle has quit IRC23:42
*** hongbin has quit IRC23:45

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