Thursday, 2017-06-15

*** hieulq has quit IRC01:00
*** namnh has joined #openstack-tc03:22
namnhEmilienM, hi Emilien, For your comment on this patch: . Our the grenade gate was moved to voting, so could you please review the patch again. Thanks so much.03:36
namnhEmilienM, here is the patch to do this:
*** mugsie has quit IRC07:51
*** mugsie has joined #openstack-tc07:54
*** mugsie has quit IRC07:54
*** mugsie has joined #openstack-tc07:54
*** jpich has joined #openstack-tc08:11
*** mugsie has quit IRC08:59
*** mugsie has joined #openstack-tc09:00
*** mugsie has quit IRC09:00
*** mugsie has joined #openstack-tc09:00
* ttx quietly drops a few bombs to the ML09:15
*** mugsie has quit IRC09:22
*** mugsie has joined #openstack-tc09:22
*** mugsie has quit IRC09:22
*** mugsie has joined #openstack-tc09:22
*** mugsie has quit IRC10:27
*** mugsie has joined #openstack-tc10:29
*** mugsie has quit IRC10:29
*** mugsie has joined #openstack-tc10:29
*** cdent has joined #openstack-tc10:33
*** sdague has joined #openstack-tc10:48
EmilienMnamnh: ok, I'll look today11:11
EmilienMnamnh: I commented
EmilienMnamnh: +1 on - but please address my comment for the zuul layout11:15
namnhEmilienM, I see, thanks for your +1. I will push up a patch set to update the gate.12:09
*** namnh has quit IRC12:10
*** mugsie has quit IRC13:43
*** mugsie has joined #openstack-tc13:46
*** cdent_ has joined #openstack-tc14:11
*** cdent has quit IRC14:11
*** cdent_ is now known as cdent14:11
smcginniscdent: Heroine? :)14:12
cdentI'm struggling to explain to myself why infra should host everyone and everything that wants to be hosted14:14
smcginnisI had the same thought.14:15
cdentand opium kind of ends up being a good word for that level of dedication14:15
cdentas far as I can tell there isn't even agreement with the tc on what "big tent" means14:28
cdentso at least killing that is a start14:28
cdentbut unless we answer the questions, the next set of stuff will have the same issues14:28
ttxcdent: if we had a clear name to describe "what is hosted on infra but actually not officially openstack", I posit that we would have avoided the confusion around what "big tent" means14:31
cdentttx: probably true, but we'd still have the confusion over what "officially openstack" means :)14:32
cdent(or, rather, why it matters)14:32
ttxIn the end, it really means "governed by the Technical Committee"14:32
cdentwhich is a non-statement14:33
cdentit doesn't say anything about value14:33
ttxsince being in gives you voting rights, and places you under the TC oversight in return14:33
*** emagana has joined #openstack-tc14:33
ttxwell, to use the trademark, you have to be governed by the TC14:33
ttxso the value is all about the ability to say that you are "an OpenStack project"14:33
cdentbut you don't get the trademark just from that, do you?14:34
ttxside benefits (like event space) derives from that14:34
cdentyou still have to pass the tests, etc14:34
ttxcdent: for some of trademark usage, being official is enough14:34
ttxlike being able to call yourself an OpenStack project14:34
cdentwe seem to be in a tautology14:35
ttxcalled community usage of the trademark14:35
ttxbasically the TC defines the limit of what can use the openstack name and what's not14:35
ttxor rather, we define the limits of the community, which in turn defines which deliverables can call themselves openstack14:35
cdentYeah, I know all that, but I think if we want to really get this stuff right, eventually, we need to be able to enumerate (at least to ourselves) why anyone (from a project) should care about any of that.14:36
cdentsimply being able to say "I'm a part of OpenStack" is nice, but it doesn't say enough14:36
ttxI covered some of it in
* cdent remembers that14:36
ttxAt this point I think there are two issues we need to address... One is the fact that some people think "big tent" means "unregulated". The other is that a lot of projects nourish the confusion by saying they are an openstack project, when they are just merely hosted14:38
ttx1st part is easy, just remove the confusing "big tent" brand14:38
ttxSecond part is harder, you kinda need to give that "other state" a name14:38
ttx"unofficial openstack project" just doesn't cut it14:39
cdentSo I think the latter one is where we get it wrong. If you're using openstack infra (lists, irc, logging, CI) then you are an openstack project, you are part of the openstack community. Saying anything else is just mean.14:39
cdentthe thing that needs to have its name changed are not the entire suite of openstack projects, but those projects which are "governed"14:39
ttxcdent: currently we are saying that to be part of the openstack community, you need to have alignment on values, principles, tooling and mission.14:40
ttxBeing on infra just checks for tooling14:40
ttxFor the rest, you apply to the TC14:40
cdentwe _say_ that, but from the outside that's now how it looks14:40
cdentif I can find code for which the git url includes openstack...14:40
cdentanyone would conclude: this code _is_ openstack14:41
ttxfwiw I'm campaigning for removal of all prefixes14:41
*** mugsie has quit IRC14:41
ttxcdent: agree that doesn't help14:41
cdenthow do you imagine removing prefixes to work with mirroring to github?14:41
ttxespecially since we are doing it for technical reasons (pain of renaming) rather than for branding reasons14:42
ttxcdent: you would still mirror to openstack/* anything that's on OpenStack's gerrit ?14:42
*** mugsie has joined #openstack-tc14:42
*** mugsie has quit IRC14:42
*** mugsie has joined #openstack-tc14:42
ttxand make the org be about a mirror of everythign you can find there ?14:42
cdentpeople will still conclude: these repos are openstack14:43
ttxcdent: who uses GitHub anyway ? Oh wait14:43
ttxAnother tactic would be to reinstate a prefix, like stackforge/14:43
cdentI'm not trying to be difficult here, just point out one of the many different angles...14:43
ttxwe have a lot less movement between the two than we used to14:44
ttxor opium/14:44
ttxcdent: heh, I know. If the solution was simple, we would have fixed that a long time ago14:45
ttxI just fear that just removing all occurences of "big tent" in the doc won't be sufficient14:45
ttxunless we give a new catchy name14:45
cdentI have that fear too, thus the questions I posted14:45
sdagueI wonder how hard it would be to change the mirroring so that there were no prefixes in gerrit, but there were when mirrored to github14:45
sdagueand if that would help with the issue14:46
ttxwhich is why I combined the two things. Find a new name for the category, and explain, we don't say "big tent" anymore, we say X14:46
ttxsdague: true, we could still mirror to two different orgs14:46
ttxbased on projects.yaml14:46
sdaguealso, is there a reason to not have this conversation over in #dev? this impacts more folks and it's not clear that this needs to be a tc only input space14:47
ttxsdague: nope, I was just anticipating office hours14:47
ttxOffice hours now!15:01
johnthetubaguyyeah, cdent, I promised I would re-read that vision draft15:02
cdentI don't reckon there's any huge rush?15:02
cdentIt won't be 2019 for a while yet15:02
johnthetubaguyoh dear...15:03
johnthetubaguythere are no subtitles added yet, was that on purpose?15:03
johnthetubaguyin some ways it flows too well right now to add them15:04
cdentjohnthetubaguy: not really, I just didn't do that part yet as I was in the mode of "see how the paragraph transitions work out"15:04
cdentbut where they should go is pretty clear15:04
fungithis seems way more active than the last office hours15:05
ttxfungi: indeed15:05
fungi(which was me, all me, all the time)15:05
fungigot bored talking to myself pretty quickly15:06
ttxfungi: replied to your email. I see what you mean by not needing to define the negative term. Trick is, without a term, there are enough confusing signs (like the "openstack/" prefix in the git repo name) to imply that everything is an official openstack project15:06
cdentjohnthetubaguy: if you're inclined to either leave a comment reminding me, or just adding them yourself, both are great with me. I'm going to be funemployed for the next two weeks but still attending to that kind of stuff.15:06
ttxIt's actually the combination of the two that's killing us :) So we need to fix one or the other, or both15:07
ttxCurrently, "unofficial openstack project" is still seen as "openstack project" by most15:08
fungimaking gerrit mirror to different github prefixes on a per-repo basis would get messy quickly... like adding thousands of lines to its configuration and hoping it doesn't explode15:08
ttxso the negative space approach is not working15:08
sdaguenegative space only works if you are really familiar with the space in question15:08
ttxsdague: ++15:08
johnthetubaguycdent: cool, I see your TODO, I guess I can comment on that.15:08
sdaguewe're "mostly" not clarifying that part15:09
sdaguethis is about clarification for people that aren't super familiar15:09
fungimy main concern with "branding" anything is that the next step is always "promoting"15:09
ttxsdague: right, and I really think giving it a name will help15:09
ttxfungi: we didn't see that much promotion in the stackforge days15:09
sdaguefungi: what promotion are you concerned about?15:09
fungiexcept we did. for example people thought you needed to "join stackforge" before you could become incubated15:10
ttxsdague: projects clamoring that they are an opium project ?15:10
fungiand people always talked about "incubating in stackforge"15:10
mugsiefungi: did you not have to join stackforge to become incubated?15:10
fungiwe let people co-locate their software development with openstack as a measure of convenience, mainly because the board said companies wanted to be able to do that15:10
mugsieone fo the requirements for incubation was to use the infra toolds15:10
fungimugsie: you very much did not need to, no15:10
fungimugsie: yes, you could go from somewhere else to incubated. there wasn't a required stackforfge-first step15:11
mugsiedid anyone ever?15:11
ttxfungi: which is why the name should not imply incubation15:11
ttxstackforge was a bit bad in that respect15:11
ttx"hosted" projects would not have that connotation15:12
ttx"opium", maybe15:12
fungii'm starting to like the term co-located15:12
notmynamettx: based on what you said above, seems that one big concern about "what is openstack" is related to the *deliverable* not the hosting. that is, kill any notion of "openstack projects" and instead just focus on "openstack deliverables"? ie the previously-named integrated release15:13
notmynameto be more clear, "openstack is the released thing" and do away with the idea of "an openstack project"15:13
ttxnotmyname: it's tricky, because some of the deliverables produced by official projects are not openstack deliverables. Think infra tools15:13
fungii still call them "projects" when i mean "deliverables" so that seems fine to me15:13
fungibecause all our tooling calls each git repo a "project"15:14
sdaguefungi: are we mirroring directly to github from gerrit? or is it a secondary mirror from
ttxAlso we tried to kill "projects" before, but that didn't succeed :)15:14
fungisdague: we're using gerrit's replication plugin15:14
notmynamettx: no, there wouldn't be such things as an "official project" at all!15:14
ttx(currently we should only say "project teams" and "deliverables")15:14
ttxnotmyname: I would argue that's already the case (for last two years), and yet people still say "openstack projects"15:15
ttxas a way to describe a group of deliverables I guess15:15
ttxLike... glance and glancestore are the glance project15:16
ttxnotmyname: we hoped that would be seen as the canonical truth of what is openstack, but apparently people consider github pages as more canonical15:17
* fungi would still love to drop github mirroring entirely15:18
fungii suppose we could rename the github org for openstack to "openstack-and-pals"15:18
notmynamewell, if you take the thought about .5 steps farther, then you just say "openstack is a distro of cloud software" (regardless of where it's hosted/maintained). but that puts us in a place pretty far away from where we started originally15:18
fungito imply that it hosts more than just openstack projects15:18
cdentfungi: I think the problem is that they _are_ openstack projects. using openstack infra is what makes them so. not names or governance policies. that we say they are not is pretty much meaningless.15:19
cdentso we should change the name of the official projects, not the unofficial ones15:19
sdagueI would be very sad if github mirroring was dropped, given that it's the only way to be able to provide a stable url link to a specific commit that includes highlighted lines15:20
ttxWe basically removed all friction when a project joins (no change in ML, IRC channels, repository names), at the price of creating a lot of confusion in the marketplacefungi: I wonder if the on-boarding convenience15:20
lbragstadsdague: ++15:20
ttxWe basically removed all friction when a project joins (no change in ML, IRC channels, repository names), at the price of creating a lot of confusion in the marketplace15:20
ttxI wonder if that's not too much of a price to pay for on-boarding convenience15:21
cdent(highlighted lines)++15:21
ttxi wouldn't mind if things that are not official would use separate MLs and require renaming of git repo when they get in. It's not as if we converted that many recently15:21
fungii'm also fully in favor of declaring stackforge a failed experiment and asking remaining projects to either join openstack officially or relocate within some timeframe15:21
ttxfungi: that would work15:22
cdentfungi: that's an option that is certainly worth considering, although it somehow feels mean for some reason15:22
fungiwould solve all of the ambiguity right there15:22
fungistop hosting things that aren't openstack15:22
mugsiewhat about drivers for things like neutron, that cannot join openstack15:22
ttxfungi: totally.15:22
cdentI think it would help clarify (in the sense of "distill") openstack15:22
mugsiebut still get used by openstack installs15:22
fungimugsie: there are a number of them whose vendors already host them elsewhere15:23
ttxmugsie: would force us to clarify their status15:23
ttxwhich wouldn't be a bad thing15:23
ttxcurrently there is a lot riding on that grey negative space15:24
ttxeither being hurt of exploiting that confusion15:24
johnthetubaguydo we have a good point in the thread with a consolidated list of issues we are trying to fix?15:24
ttxfungi: I agree that the best way to clear it would be to get rid of it15:24
ttxThe projects (see what I did here) that would hurt the most would be those that are clearly not in our scope but still kinda want to live here15:26
ttxfungi: how many % resources would you say would you say stackforge^Wopium^Wnegative space takes those days ?15:27
sdagueso... one of the reasons we had this "other" space was because projects that are growing up from new ideas have some place to work like an openstack project from quite early (possibly commit 1)15:28
ttxfungi: having a bit of data on that negative space (how many repos, what activity, how many added recently...) would help assess the cost of getting rid of it15:28
sdaguebecause the way openstack review tools and testing works is quite different than in the rest of the world15:28
notmynamesdague: maybe that's a bug and not a feature?15:29
mugsiei think it is a feautre15:29
sdaguenotmyname: maybe. Though you really can't do the kind of testing we do on travis15:29
sdagueand having participated in code review in github for large projects.... oof is is brutal vs. gerrit15:30
fungittx: i don't think we have any real numbers around that (and would depend a lot on what we want to measure). i'll see what i can come up with15:30
ttxsdague: if we want to keep that "training ground" that points to the need for a name for it. Plus rules for culling it when things don't go anywhere15:31
sdaguettx: right15:32
sdaguejust trying to explore what's important to people15:32
*** gordc has joined #openstack-tc15:33
*** tdasilva has joined #openstack-tc15:33
cdentto continue the exploration: is the need for a training ground an indication of a bug?15:33
cdent(on the other hand, I very much like that we have been in the position to be able to provide such thing...)15:34
ttxsdague: it's a fair point. I think those are two solutions that would solve the problem. The Opium route (giving the negative space a name), or removing the space, or a mix of the two (have opium with strict rules about projects needing to move one way or another within x months)15:34
cdent(it's a huge luxury/privilege)15:34
ttxcdent: it's not that much a training ground imho. It's more a way to not force people to use github to land the first commits15:35
ttxalthough I do that15:35
fungior renaming the org on github to be more obviously not "just openstack" (while moving forward with getting rid of namespaces in our gerrit)15:35
sdaguettx: I disagree, it really is a training ground15:35
sdaguegerrit is something new to lots of folks15:35
notmynamecdent: the need for a "training ground" is more around what you said in your email: the need for marketing. that's not always a bad thing; openstack has been a place where competitors can legally cooperate, so having an openstack project enables that (whereas a separate namespace is a barrier because of the extra legal scrutiny)15:36
ttxsdague: do people in the negative space actually use that much of our unique approadch, beyond having to use Gerrit ?15:36
ttxi.e. how many projects actually use real tests15:36
sdaguettx: that's a good question15:36
sdaguewhich has a real answer that could be found15:36
ttxright, looks like choosing the right approach will call for a bit of demographics15:37
ttxI'm not attached to a particular solution. I just don't think the status quo is bearable anymore15:38
ttxBeen talking more with people outside of our usual circle, and the confusion is really gigantic out there15:38
ttxand tbh I can't blame them15:39
sdagueI do think that if projects grow up in travis world, and have to invest a bunch of time in bug-bots to manage github issues, it probably means too much investment to come over to any system we end up having15:39
sdaguettx: I agree on the confusion part, definitely happy to make a change there15:39
ttxOn another note, if anyone wants to discuss the Fuel proposal, I'm here!15:40
smcginnisttx: It would be great to get more of a voice from those outside, since that is where most of the confusion happens.15:40
notmynamesdague: I want to go back to your comment about how openstack's testing is different than "the rest of the world"15:40
sdaguenotmyname: sure15:40
smcginnisttx: Maybe that should go over to the operators mailing list and ask for input?15:40
sdaguenotmyname: where I'm defining "rest of the world" as what you'd find out on github (so it's a narrower slice of the rest of the world)15:41
sdaguebut where I think the alternative mostly will be for people not in our infrastructure15:41
notmynamesdague: my response (maybe that's a bug and not a feature) isn't a value judgement on either. what i mean is that the differences and the perception is what's adding to the confusion of "what is openstack"15:42
ttxsmcginnis: This proposal of mine is actually the result of work we have been doing on the "communicating what is openstack" workgroup from the TC+Board+UC workshop15:42
notmynamesdague: it get's back to the questions cdent was asking about why people even think the naming question is important15:42
ttxsmcginnis: it's not coming out of the blue15:42
notmynamesdague: *why* do people want to have a name for half-in-but-not-really openstack projects?15:43
ttxsmcginnis: I can probably get lsell to comment on that thread15:43
notmynamesdague: what value to people get by being "openstack"?15:43
smcginnisttx: +115:43
sdaguenotmyname: because without a label for it, everyone not deeply knowledgable in our community assumes every single thing on is openstack15:44
sdagueand like sourceforge, that include a lot of half baked rot15:44
notmynamesdague: for all practical purposes, it is! (today!)15:44
sdaguenotmyname: except it isn't, that was never the intent15:45
notmynameit doesn't matter what the intent is15:45
fungithe impression i get is that it's, say, the stereotypical clueless newb whose manager tells them they need to "install an openstack" and now they're stuck trying to figure out what that even means15:45
notmynameif it's under that URL, it's an openstack project15:45
ttxsmcginnis: the most confused are the press (but then they are easily confused), followed by analysts, followed by CxOs and random architects. Not sure asking our MLs would reach the target audience. But Lauren talks to them all :)15:45
smcginnisCool. Just thinking if we just discuss within this same group, we'll just end up in another tent.15:46
fungiand if we can't make it easy for that engineer who needs "an openstack" to discover what's part of openstack and what isn't, then there's a problem15:46
ttxsmcginnis: yep. Which is why the discussion started at that Board+TC+UC group, with heavy input from marketing :)15:47
ttxIt's no longer a technical issue15:48
ttxBut it's still a TC one15:48
smcginnisYep, get that.15:48
sdaguenotmyname: right, I think that's one of the key problems :)15:48
sdague is openstack (as an example)15:49
ttxsdague: and if you read that "openstack is a big tent" looking at that github org kinda confirms your worse fears about what that term means15:49
ttxso the combination of the two is hurting us a lot15:50
* johnthetubaguy nods15:50
* smcginnis nods too15:50
sdagueat some level perception is reality, as people are making decisions based on it about whether or not they get engaged15:50
smcginnisAnd I can say, now working for a vendor that has a downstream distro, decisions are made based on that more than I realized.15:51
ttxAlso lately, was used by... let's say... alternative organizations... as a cheap way to ditch openstack15:51
johnthetubaguysmcginnis: I believe, becuase people buy stuff that way too15:51
smcginnisjohnthetubaguy: +115:51
notmynameso when we (the internal openstack community) figure out why people want to have a project with the openstack prefix, then we can better understand what to do to reduce confusion15:52
johnthetubaguythis seems to be where we all started, but how many people would it hurt to move repos not in projects.yaml to openstack-universe or something?15:55
johnthetubaguy... so I think I am just understanding the through process you were all going through about 55 mins ago15:56
johnthetubaguygiving it a name, vs naming the official stuff better (constellations), etc.15:57
notmynameok, crazy proposal (if only to explore the limits of the solution space): what if we killed the whole idea of "openstack projects" and focused only on the deliverables? so cinder is a project that does its own thing, and it's included in the openstack distro. and maybe also the k8s distro. and maybe something else (substitute for any other current openstack project or hypothetical release packag16:00
smcginnisnotmyname: So we each get our own tent.16:01
notmynamettx: not killing "projects" as was attempted earlier, but more like the stuff that's in -infra is the *only* "openstack" there is16:01
notmynamesmcginnis: yeah16:01
notmynamesmcginnis: or hut or yurt or house or whatever you want to build, actually16:02
* smcginnis wants a hammock16:02
smcginnisnotmyname: Interesting idea.16:02
notmynamethe implication would be that "openstack" would likely directly compete with RHEL and ubuntu16:03
notmynameand there's definitely loss around the internal community16:03
cdentso "building openstack" is the sort of mission?16:03
cdentand there are things that feed that16:03
notmynamecdent: yes16:04
notmynameyou could even have "openstack" that includes k8s. or whatever else is the hotness of the month16:04
ttxnotmyname: I think that is a bit far reaching, and a bit orthogonal with the problem of the negative space creating cinfusion16:05
notmyname(I'm spitballing this whole thing at the moment) it would be a change to focus on what's delivered vs the current pattern of *how* it's delivered16:05
notmynamettx: oh, it's definitely far reaching! like I said, only trying to find the boundaries of the solution space :-)16:06
*** jpich has quit IRC16:06
ttxnotmyname: also how much different is it from sayign openstack = what's on ?16:06
johnthetubaguyif there was a *thing* to download called OpenStack that you could run on your fav distro and poke it with a stick, it would solve lots of this, but it breaks the main ecosystem we have built16:06
notmynamettx: thinking of cultural differences in our community, I might translate your statement into 'murican: "john, that's the stupidest idea ever. plese never speak of it again!" ;-)16:07
notmynamettx: I don't think it is, other than a cessation of focus on *how* the projects that make it up are doing things16:08
ttxnotmyname: no, I'm actually genuinely confused16:08
ttxnotmyname: the way i see it, the TC blesses a series of teams with a scope compatible with the openstack mission, and they produce deliverables, that are assembled in series on releases.o.o16:09
ttxand that is what "openstack" ends up being, a set of compatible building blocks for building open infrastructure ?16:10
cdentttx that's conlfating intent with perception again16:10
notmynamettx: that is true, but not complete (IMO). currently the TC also places a great deal of weight on the management of the code in the respective projects16:10
notmynamettx: if it were only what you said, then the TC would have already packaged k8s and put it on as part of the things compatible with the openstack mission of providing cloud infrastructure software16:11
ttxnotmyname: that's a fair point. In name of presenting a more... seamless experience of operating those components together, there are a number of things that are pushed horizontally16:11
notmynamettx: for the record, I find that an admirable and innovative part of this whole openstack thing we've been doing eover the past 7 years :-)16:12
ttxnotmyname: we currently primarily produce software building blocks, not really a distribution16:13
fungithe kubernetes team hasn't approached us _wanting_ to join openstack governance, have they? that seems like the key distinction to me16:13
notmynamettx: based on the external voices you've been speaking with, what's the perception? is the perception that we are producing a distro?16:13
ttxalthough the Stackube project application ceratinly pushes the envelope in the distribution direction16:13
ttxnotmyname: the perecption would be that vendros build distros on top of the framework16:14
ttxI'll have to drop from the discussion as the day ends... but I loved this talk, let's continue over various media.16:15
ttxFound that the ML was a bit dead this morning so thought i  would wake it up16:15
notmynamefungi: doesn't matter. python doesn't submit to RHEL governance to be included in that distro. I'm saying that if the TC defines openstack as just the stuff on releases.o.o, then it would have included k8s long ago. the point is that the TC *does* care about more than what's listed at that site16:15
ttxYou are right that it indirectly asks the question of "what is openstack". But I don't think the current position is that much of a problem, if we fix the branding.16:16
notmynamettx: in the interest of inclusion, I think it would be good for you (ie the tc chair) to link to this office hour's transcript for the ML thread16:16
ttxack, will do now16:16
notmynamewhat an invigorating discussion by which to start the day! :-)16:17
* notmyname goes off to get ready for the rest of the day16:17
ttxOpium does that to you16:19
funginotmyname: okay, to rephrase, nobody interested in packaging and redistributing kubernetes has asked the tc to take them under our governance16:21
notmynamefungi: I don't see how the two are related16:21
notmynameor, wait. we're not disagreeing, I don't think16:22
notmynameobviously governance and distribution in openstack today are related16:22
fungiwe can't govern nonexistent teams16:22
funginothing can be part of openstack from a governance perspective if there's nobody doing it16:22
cdentIsn't the underlying thrust here a reconsideration of what a team is?16:22
cdentand does?16:23
fungisomething other than a group of people?16:23
notmynamemy original comment is that the idea that openstack is only what is a tarball on release.o.o is an incomplete definition16:23
notmynamebecause the TC *does* care about governing the teams that have a tarball on that site16:23
fungii still maintain that openstack is not software. but maybe that's the problem, we're conflating the name of a community with the name for what that community produces16:23
notmynamethat is a very very good point16:24
notmynameopenstack (the community) said "we've got a big tent" related to who. the external perception is "you've got a very messy big tent" related to what16:24
ttxnotmyname: thought you'd appreciate:
johnthetubaguy+1 that hits on a very interesting issue vs the perception16:25
fungithe tc is governing teams of people, those people produce stuff, the tc is not governing stuff directly16:25
notmynamettx: same song, 328th verse16:25
cdentnotmyname: I demand you revise that statement, it is the 329th verse and unless you capitulate we will surely have a schism16:27
* johnthetubaguy hands cdent and ice cream16:27
*** dims has joined #openstack-tc16:48
dimsduh, sorry i forgot to join this16:49
cdentyou missed out on a party dims17:00
dimsi know!17:01
cdentso, am I missing something, or do we not even agree on the definition of "big tent"?17:45
gordccdent: it doesn't seem like it (i admittedly haven't followed big-tent stuff since conception and was confused back then as well)17:51
sdaguewell, that's the crux of the issue right?17:56
sdaguebig-tent is defined as all the projects under governance. For people steeped deeply in OpenStack, that means something.17:57
notmynamesdague: I think your proposal on the ML is a (relatively) simple and straightforward way forward without having to solve Once And For All, Again: "What is OpenStack?"17:57
sdaguefor the rest of the world big-tent means "everything I found at" which isn't the same17:57
sdaguenotmyname: thanks!17:57
notmynamesdague: namely, mirror openstack projects to two separate github namespaces based on whatever bucket we the community put them in17:57
notmynamefixes the perception problem. is actually doable, and likely in a timeframe measured less than "years"17:58
gordcsdague: is that a messaging issue or something specific to the 'big tent' name?17:58
sdaguenotmyname: yeh, I'll admit, I don't know the technical limitations there with gerrit17:58
gordcor both given 2 years of confusinos17:58
sdaguegordc: at this point we're beyond a messaging problem, because this has become a fixed pointer in people's heads and any further messaging is bouncing off of that17:59
gordcsdague: understood. personally, i'm not sure who "here's a bunch of 'cloud' stuff the18:01
gordcproprietary companies provide but from companies that fund openstack18:01
gordcbrand that is 'open'. we make no guarantees that they actually work18:01
gordc(they probably don't), this is solely to say these projects: exists, are18:01
gordcwhoops bad paste.18:01
gordci'm just not sure who this label is for ultimately. it seems ambiguous regardless.18:02
fungiit continues to sound to me like github is "the problem" here. i still don't know why we're promoting use of their proprietary service18:06
fungii mean, i know it's because there are lots of people who think github is the only place they can find software and look for us on there, and if we didn't have a presence on it then someone else would be serving up copies of our software of dubious provenance and quality18:08
cdentfungi: getting rid of it is certainly an option (I'm trying to track the several that have come across the radar today) but I think it is medicine for the superficial issues, and doesn't address the deeper stuff18:08
notmynamefungi: how do you feel about what about using that instead of our "by hand" ones?18:10
fungii just wish there were a simpler way to redirect people to the canonical locations for our software and/or that github themselves catered to their users who want to "fork" git repositories hosted elsewhere on the internet so we wouldn't need to maintain copies there ourselves to satisfy them18:10
notmynameif I look at it looks different than openstack. ie the "mirror of <>"18:11
funginotmyname: i hadn't seen that before, and it looks like a great answer potentially18:11
funginotmyname: oh, wait, that's just a description of what we're already doing18:11
notmynamefungi: well it let's us actually push code to the most discoverable place (github) and potentially sidestep your philosophical concerns about it18:11
funginotmyname: i'm not seeing what's different. just redirects to which says (paraphrasing) "here are some popular projects which automatically mirror their source code to github"18:14
notmynamesure, in the DVCS sense there's nothing magic. I wonder, though, (and I can't find much info) if there's a different bit that twiddled somewhere in github so that github treats it differents18:16
funginotmyname: or are you suggesting that we should switch from using gerrit's replication plugin to using per-repository post-receive hooks?18:16
funginotmyname: oh, right looking at the mirrors they linked to from there i don't spot anything different from how our mirrored repos look on github18:16
notmynameit's mostly a discoverability thing. be findable on github, but also marked as a mirror to something else. and the way the kernel does github PRs is something I've heard discussed (do we do it?)
notmynamefungi: the "mirrored from <somewhere.else>" is the difference18:17
funginotmyname: oh! now i see it18:17
notmynamecompare the top of with
cdenteven the icons are different18:18
notmynameanyway, if this is something interesting to our community, I think it's only part of an answer. I still like sdague's proposal of mirroring to different orgs in github for the different status of projects (and still having a common namespace in our community)18:18
fungiyeah, i was looking in the top-level list of repos in each org an dthe little "mirrored from" wasn't jumping out at me there18:19
fungithe icons might have been more of a tip-off if i dug down deeper than org-level18:19
fungiyeah, so far i haven't found any treatment of how you get that "mirrored from" status and repo type set18:20
fungiwondering if it involves reaching out to a human there18:21
fungii want to say someone already asked them about that a couple years ago and they said they stopped adding them, but i'll try and find out more18:22
sdagueyeh, would be good to know18:22
sdagueit's also notable, that has less pages of projects than
sdagueby 30%18:22
sdagueand why digging in deeper would show that doesn't mean much, that top level view does matter to folks18:23
fungiyeah, earlier discussions with them turned up that you have to e-mail their support team for each repository you want set up, and that those are actually pull mirrors github has configured on behalf of those projects18:26
cdentthe so link above confirms that18:26
fungiand not pushed via post-receive hook like the about page implies18:27
cdent(for at least the time of its writing)18:27
cdentand that they don't do that anymore18:27
fungiapparently you also needed to go to some effort to convince them it was in github's best interest to set up a mirror of your externally-hosted repository18:27
*** lbragstad has quit IRC18:28
*** cdent has quit IRC18:32
fungiso as some alternative solutions there we're brainstorming in #openstack-infra, we can renormalize all the repo descriptions to be something like "Mirrored from" and add something similar (but probably more verbose) to the org-level description we've so far left blank18:34
jeblairnotably, we can add a link to the *project navigator* from the org-level description18:36
mordrednotmyname: (didn't see anyone answer you - but yes, we have a bot that responds to PRs people send)18:36
notmynamemordred: oh, cool18:36
*** lbragstad has joined #openstack-tc18:36
jeblairwe could also somewhat tailer the repo descriptions (eg, "This is an $unofficial_terminology project..." vs "This is an $official_terminology project...")18:37
mordrednotmyname: we've gotten some angry replies to that bot too18:37
notmynamemordred: "how dare you not accept my awesome code! don't you know that your project is broken without this pull request! I'm taking my code and going elsewhere!"18:37
mordredjeblair: yah. this is true. I think we'll need to rework the jeepyb gh integration a bit - but that wouldn't be a bad idea anyway18:38
mordrednotmyname: yah. you've got it18:38
jeblairthese things may all be worth doing, but i suspect whatever underlying problems we're trying to solve may extend beyond the set of folks who learn about openstack by browsing the repo list in github.  (this may very well help with that set though)18:39
jeblairi confess, i do not know how large of a subset of "folks who are learning about openstack" that is.18:40
jeblairbut these are good, not-too-difficult things to do regardless, i think.18:40
mordredjeblair: I agree - I believe the existence of openstack/ in the git link at all is the thing that is communicating information regardless of what verbiage might be posted to any of the web ui's - but I think we can post the verbiage and maybe it helps some percentage of the issue18:41
*** gordc has left #openstack-tc18:57
*** hongbin has joined #openstack-tc19:04
fungii still like the idea of renaming that gh org to "openstack-and-pals" ;)19:07
fungihas a krofft bros. feel to it19:08
mordredfungi: :)19:23
mordredI'll go ahead and go out on a limb and say that _probably_ we'd have people just as confused if we got rid of the github mirror AND the repo prefixes and only have - since would be in the hostname19:23
mordredand "openstack the community in which people might host code" and "openstack the cloud software project" being distinct seems to be a concept that's alien to people19:24
mordredlike- nobody was confused about openstack being on launchpad and thinking it was part of ubuntu19:25
* smcginnis thinks they were already too confused by launchpad19:25
fungii wonder whether, instead of running two gerrits, we might be able to get away with two vhosts for git.o.o and something else and then put the governance-parsing logic on the git server end (maybe via a symlink farm)?19:25
fungiso continue mirroring to the git servers as usual, but make two different cgit sites and put their webroots in different directories with different sets of symlinks (or hardlinks even) built from governance metadata19:27
fungimaybe that's more of a discussion for #openstack-infra19:27
mordredfungi: well - I like it in as much as it's again a thing we could do without a ton of effort19:27
mordredfungi: HOWEVER19:27
mordredthere is a compllication19:27
mordredfungi: (actualy, still might not be terrible) - and that's that in zuul v3 repos have a "canonical_hostname" that are associated with a connection19:28
fungiyeah, i was quietly hand-wavey about the ci side of things19:29
mordredso we tell zuul that repos found in the gerrit at review.o.o are "actually" from git.o.o- so that they get checked out at src/git.o.o/projectname19:29
fungii think it gets easier with zuul v3 (people are probably long tired of hearing us say that)19:29
mordredso we'd need 2 gerrit connections each with a different canonical_hostname configured, and we'd need to move projects from one bucket to the other in the zuul tenant config if/when something moved19:30
fungibut still easier than moving projects between gerrits, or even repo renames in gerrit19:38
fungii took a stab at jeblair's suggestion of updating the org profile at to maybe clarify things some, but certainly if we tweak our manage-projects script switch the repo-specific descriptions out with mirror urls and feature the word "unofficial" in there based on a negative search against the governance projects.yaml that seems like it would help things further21:46
*** sdague has quit IRC23:28
*** hyakuhei has joined #openstack-tc23:36

Generated by 2.15.3 by Marius Gedminas - find it at!