Friday, 2018-09-28

persiaTheJulia: You're joking, but there was chat earlier about one of the candidates maybe not making it to summit.  Had the election results been different, suddenly that would have been more important.00:01
TheJuliaThat is true00:02
TheJuliapersia: I was more referring to there being a bootcamp or something, but it really is initiation by fire00:03
mnaserhehe00:03
scasi do have a side project called, among other names, universidad del fuego00:05
openstackgerritKendall Nelson proposed openstack/governance master: Stein TC Election Results  https://review.openstack.org/60589600:20
persiaItem for a future office hours: with changes to cycle length and timing, do we want to shift TC term lengths?00:23
*** jamesmcarthur has quit IRC00:28
*** jamesmcarthur has joined #openstack-tc00:29
*** jamesmcarthur has quit IRC00:34
TheJuliaI was pondering that earlier...00:42
TheJuliathen again, there is value in consistency00:48
*** jamesmcarthur has joined #openstack-tc00:55
*** jamesmcarthur has quit IRC00:59
*** annabelleB has quit IRC01:00
*** diablo_rojo has quit IRC01:05
zanebpersia: I'm not sure the bylaws technically allow us to mess with it even if we wanted to01:26
*** jamesmcarthur has joined #openstack-tc01:28
persiazaneb: https://www.openstack.org/legal/technical-committee-member-policy/ suggests to me that we need to have an election at least every six months, and that a term cannot exceed a year.  If we want to change things, that means a transition with shorter terms and more frequent elections.01:28
persiaFrustratingly, we seem to have historically done the opposite: terms used to run march-to-march and september-to-september.  They currently run april-to-april and october-to-october.  I don't want to investigate the rationale for that transition, because I suspect it contravenes the bylaws.01:30
zanebah you're right, we could make it shorter01:30
persia*but* if we want to run summit-to-summit or something, we could probably make that happen.01:30
persiaAlso, last I heard, the Foundation was considering some bylaws changes.  Personally, I feel it would make sense to make the TC have an election within at least 7 months, for terms not to exceed 13 months, just to handle the special cases that have appeared in the past, where we needed a couple extra weeks here or there.01:33
persiaBut this is properly a topic for when more folk are present :)01:33
fungii personally will push for getting the tc member policy removed from the bylaws in the rewrite, to put the openstack tc in charge of the remaining details currently hard-coded in a foundation bylaws addendum02:07
fungithis would put us on more equal footing with the other osf projects in regards to controlling the nature of our project's governance02:08
fungiit seems silly to me to have multiple osf projects, but community governance details of only one of them detailed in the foundation bylaws02:09
fungiin fact, this is something worth bringing up in the joint leadership meeting02:10
dtroyerfungi: thanks, I think that makes sense.  the pilot projects (will) have some freedoms that OpenStack (the project) doesn't in this regard, I agree that bit of refactoring needs to be done.02:18
fungii guess i can start with a change to copy the tc member policy (verbatim) from the bylaws appendix to the governance repo03:06
fungithat'll give us a good talking point03:06
*** jaypipes has quit IRC04:27
*** jamesmcarthur has quit IRC04:57
*** jamesmcarthur has joined #openstack-tc05:01
*** jamesmcarthur has quit IRC05:06
*** e0ne has joined #openstack-tc05:52
*** e0ne has quit IRC06:24
*** mtreinish has quit IRC06:24
*** mtreinish has joined #openstack-tc06:27
*** jamesmcarthur has joined #openstack-tc06:29
*** jamesmcarthur has quit IRC06:34
*** e0ne has joined #openstack-tc06:52
*** jamesmcarthur has joined #openstack-tc07:07
*** jamesmcarthur has quit IRC07:11
cmurphy> But this also means that folk who chose not to stand for reelection aren't magically off the hook just because the election concluded.07:21
cmurphyaw dang07:21
*** jamesmcarthur has joined #openstack-tc07:29
*** jamesmcarthur has quit IRC07:34
*** tosky has joined #openstack-tc07:50
*** jamesmcarthur has joined #openstack-tc07:56
*** jpich has joined #openstack-tc07:58
*** jamesmcarthur has quit IRC08:01
*** bauzas is now known as PapaOurs08:03
ttxfungi: although... the appendix is the only thing that prevents us from self-appointing us as dictators-for-life08:04
ttxIt's been useful in giving us a couple of red lines we are not allowed to cross08:05
ttxI agree it goes in slightly too much details and stricter timings than we can practically handle08:06
ttxbut I'm not convinced we should throw away the whole baby with the bath water08:07
ttxzhipeng: sorry you could not make it. I think until we get more people from China to actually vote, it will be a difficult challenge.08:08
ttxI'm working with horace to see how we can fix that08:09
ttxIn the mean time, I think everyone here would appreciate if you worked with the TC on those questions, to represent that view even if not elected.08:10
cmurphy++ it is really critical that zhipeng and ricolin continue to lend their perspectives, I'm a bit frustrated that we yet again missed the chance to make it official08:16
zhipengthx folks :)08:17
*** tosky has quit IRC09:02
*** tosky has joined #openstack-tc09:03
*** cdent has joined #openstack-tc09:58
*** jamesmcarthur has joined #openstack-tc10:12
*** e0ne has quit IRC10:16
*** jamesmcarthur has quit IRC10:16
*** e0ne has joined #openstack-tc10:25
cdentseems like turnout was relatively good10:28
*** dtantsur|afk is now known as dtantsur10:57
openstackgerritThierry Carrez proposed openstack/governance master: Inherit openstackdocstheme for TC site  https://review.openstack.org/60493511:03
dims+1 ttx "everyone here would appreciate if you worked with the TC on those questions" (towards zhipeng)11:19
dimscdent : compared to previous elections?11:20
cdentdims: My memory may be faulty, but the %age of potential voters who did vote seems higher. I haven't confirmed my memory with reality, though.11:26
dimscdent : you are right. Rocky was 384 out of 2025. Stein was 403 out of 163611:28
dimscomparing https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_f773fda2d0695864 and https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_98430d99fc2ed59d11:28
cdentwow, that's quite a difference11:28
dimselectorate shrunk but more folks voted!11:28
dimsQueens : 420 out of 2430 ( https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_ce86063991ef8aae )11:30
cdentbiab11:37
*** cdent has quit IRC11:37
fungittx: i agree i wouldn't want to lose the tyranny barrier, but we could for example bake into the extracted tc member policy that changing it requires a special vote of the technical contributors11:46
* cmurphy tries to imagine ttx or fungi as tyrannical dictators11:47
fungimostly i want to make sure that as governance of other projects begins to solidify, openstack isn't the only one stuck without a way to evolve its own without lawyers and permission from the osf board of directors11:47
fungisimply getting a glaringly confusing typo fixed in the existing tc member policy has dragged on for years now11:49
*** Bhujay has joined #openstack-tc11:58
*** EmilienM is now known as EvilienM12:00
*** mriedem has joined #openstack-tc12:29
persiacmurphy: My read is that you are free from 31 October.12:39
cmurphypersia: ah thanks for clearing that up12:40
fungithough if you need to resign early, we would likely just seek to temporarily appoint one of the recently-elected folks to fill your spot until their term officially takes effect12:41
cmurphyI'm not actually in a rush :)12:42
*** jamesmcarthur has joined #openstack-tc12:45
lbragstadthanks mnaser :)12:58
*** jaosorior has quit IRC13:00
*** cdent has joined #openstack-tc13:06
fungicdent: dims: i think we're still witnessing the after-effects of dropping the requirement for joining the foundation to be able to push changes. we now instruct people to join and maintain their membership in the osf if they want to vote in technical elections, so the overall percentage of qualified voters who are interested in voting rises as a result13:07
dhellmannfungi , persia : if we want to change the bylaws, we need to start now. the other proposed changes will be approved by the board at the JLM in berlin, so if we wait to start then we'll have to wait another year for the next ballot13:09
smcginnisI do think in general, as the number of people involved in the community has shrunk, those still around are the ones that are more engaged.13:09
persiadhellmann: Excellent point.13:09
smcginnis+1 for moving the OpenStack project governance bits out of the OSF bylaws into our own domain.13:09
fungidhellmann: well, i gather the board is being asked to entertain a significant rewrite of the bylaws to handle the new scope and possible rename of the osf too13:10
fungiso, yes, i'm going to put a bug in the ear of the people who are driving that process to figure out how we can avoid ending up with the openstack project singled out as the only one with a significant chunk of its governance baked into the new bylaws13:12
dhellmannfungi : right, that's my point. those are the changes they'll be voting to approve for the ballot. we should get any tc-related changes into that same set13:12
dhellmanncool13:12
dhellmannI'd be happy to help with that, too13:12
dhellmannit would be nice if we could just come up with project leadership rules that apply to all groups. that should encourage us to keep them nice and vague.13:12
fungiright, that's my hope with it13:13
fungii basically need to start by finding out what's going to get proposed13:13
fungithere's a bit of a chicken-and-egg situation since the board is being asked to vote on a change to then get the community to vote on, but we don't necessarily have a community input phase for what's going to be proposed (other than at the public board meeting where it will be presented)13:14
mnaserdhellmann: i think asking Alan to help us draft up something would be very useful13:16
dhellmannfungi : that does feel a bit rushed13:16
dhellmannmnaser : yeah, I think there's a subcommittee doing that work, so if fungi and I can get involved we will13:17
fungii'm asking around about 1. whether there's a public comment phase planned before berlin and 2. the odds of swinging something along the lines of this particular change13:20
openstackgerritMatt Riedemann proposed openstack/project-team-guide master: Fix typo in stable branch maint guide  https://review.openstack.org/60607013:26
mriedemsmcginnis: ^13:26
ttxre: formally onboarding new members closer to summit... in the past we did that just after the election (basically starting by selecting a new chair the week after).13:28
ttxI'm not sure why we'd change that... tradition13:28
ttxpersia: any particular reason to change ?13:29
persiattx: Historically it seems we onboard at summits, but documentation is lax.  Sometimes reference/members has terms starting in October for November summits.13:30
ttxWe always updated the roster immediately after election fwiw13:30
persiaI think it might be nice to 1) be explicit that onboarding is at summits, and 2) provide a bit more flexibility in term length so that this is actually permitted by the rules.13:30
ttxand had members cast their vote the week after13:30
cmurphythat's what i thought i remembered13:30
ttxpersia: re: "Historically it seems we onboard at summits" I'm not sure where you got that feeling13:31
persiaI'm fine if we're doing that, but it doesn't match the records I found yesterday.13:31
persiaI may not have found the right records :)13:31
cmurphynot all tc members necessarily go to summits13:31
ttxalso summit is not exactly tomorrow13:32
ttxAs past chair I always inducted new members the week after the election.13:32
ttxpatches like https://review.openstack.org/#/c/605896/ are immediate and change the official roster.13:33
*** david-lyle has joined #openstack-tc13:34
smcginnisDoes that match what the bylaws state? Don't know (haven't had a chance to check myself) but based on earlier comments that might not align.13:34
smcginnisSeems fine to me, just wondering if as we make changes to where those things live if we need to also update it to align with actual practice.13:35
ttxsure, if there is text that says I've been misbehaving in the past, we should align13:35
ttxBut as the author of most of those documents, that would surprise me :)13:36
*** dklyle has quit IRC13:37
dhellmannI don't see anything in https://www.openstack.org/legal/technical-committee-member-policy/ about summits, just at least every 6 months13:37
dhellmannpersia : can you share whatever documents you found?13:38
dhellmannI would prefer not to wait until November to start the new TC term13:39
ttxhttps://review.openstack.org/#/c/565432/ shows immediate votes by new members last time13:39
dhellmannI know in the past the elections did come closer to summits, but I always thought that had more to do with the date of the development cycle than the summit itself13:39
dhellmannfor the same reason we used to do PTL elections close to summits13:39
mnaseryeah, last time for me it was right away..13:40
persiadhellmann: git history of openstack/governance:reference/members, bylaws appendix 4, various "intro" emails at summits (which I now read differently since ttx's comment)13:40
dhellmannwhen we changed the cycle start to create the PTG, we moved the PTL elections but kept the TC elections staggered13:40
persiaAt least currently TC elections are scheduled to be a certain number of weeks from summits.  That might be in error.13:40
dhellmannwe want the elections held early enough that new TC members can update their travel to make the joint leadership meeting13:41
*** annabelleB has joined #openstack-tc13:41
dhellmannso we did that on purpose13:41
smcginnisThat's what I recall too.13:41
*** cdent has quit IRC13:41
dhellmannit seems we should write some of this down :-)13:42
ttxWe say we elect new members every n months... it seems normal to me that without any other precision that takes effect immediately13:42
smcginnisI don't see any problem with the way we've been doing things, I just want to make sure what we state in documentation actually reflects reality.13:42
ttxthere is nothign in doc that says that the elected members need to wait for anything13:43
persiasmcginnis: That is my goal with suggesting we discuss "change" in the office hours next week.13:43
dhellmannneither the bylaws nor charter say anything about the summit13:43
ttxwe just say elections take place x weeks before summit. Not that the term starts at summit.13:44
ttxit never did, so i see no reason to change that interpretation13:44
dhellmannoh, we do say that, I missed that bit13:45
dhellmannyeah, so we just need diablo_rojo to update https://review.openstack.org/#/c/605896/1 to remove the chair flags and we're good to go13:46
ttxdhellmann: FWIW at past elections I immediately updated the Gerrit group to contain new members.13:48
ttxthat way they can vote on the patch13:48
* ttx will propose new patchset13:49
openstackgerritThierry Carrez proposed openstack/governance master: Stein TC Election Results  https://review.openstack.org/60589613:49
ttxoops missed the vicechair13:49
openstackgerritThierry Carrez proposed openstack/governance master: Stein TC Election Results  https://review.openstack.org/60589613:50
ttxdone13:50
dhellmannttx: thanks for the reminder13:52
dhellmannevrardjp, gmann, lbragstad : I have added you to the tech-committee group in gerrit13:52
persiaOne concern about the "start immediately" choice is that the terms are not to exceed one year, and I'm not sure we're tracking that sufficiently carefully.13:52
lbragstaddhellmann ty sir13:52
persiaOf course, if the bylaws change before the year is up, that's a different story :)13:53
ttxyeah, that's definitely a thing we've interpreted liberally.13:53
dhellmannpersia, ttx : I agree. Let's see if we can get the bylaws loosened so we can rewrite that in our charter in a form that is easier to track.13:53
ttx"every 6 months" was interpreted "every summit"13:53
cmurphyif my term didn't end until november that would be over a year13:53
ttxsince that's a more convenient alignment mechanism13:54
persiaYep, which likely contributed to my understanding that summits were important.13:54
ttxI support changing the wording to be more... flexible there :)13:54
dhellmanncmurphy : stop trying to get out of completing your term ;-)13:55
cmurphy:P13:55
openstackgerritLance Bragstad proposed openstack/project-team-guide master: Add section on what to do with tox_install.sh  https://review.openstack.org/60387513:55
*** cdent has joined #openstack-tc14:05
fungiyeah, if we're looking at the possibility to get some/most of https://www.openstack.org/legal/technical-committee-member-policy/ moved into openstack project control then there are definitely some other obligations outlined there which we aren't necessarily tracking14:05
fungifor example it says "The Technical Committee shall meet at least quarterly." and while we do tend to get together at ptgs and the forum we haven't really taken official rollcall or confirmed quorum that i'm aware. and with the next ptg occurring coincident with the forum...14:06
dhellmannwe used to meet weekly, so I'm sure we didn't worry about it for that reason14:07
persiaVery likely, but this makes it more important to fix the bylaws.  Noncompliance with bylaws can be considered actionable.  We have lots of members.14:11
ttxfungi: yes I would remove the "elections for the Technical Committee shall be held at least every six months" language and just keep "Each Technical Committee member shall hold the seat for a term not to exceed 14 months, but may be re-elected to the Technical Committee."14:11
fungi"Upon completion of the election, the Technical Committee shall give notice to the Board of Directors and the Secretary. [...] Any member of the Technical Committee may resign by delivering notice in writing or by electronic transmission to the Secretary." i'm not even sure i know who the current secretary of the board of directors is and https://www.openstack.org/foundation/board-of-directors/ doesn't14:11
fungisay... are we sure we've been doing that?14:11
ttx(14 months will give us the flexibility we need)14:12
ttxfungi: the secretary is JB14:12
ttxI've been communicating the results to Alan at elections, yes14:12
fungiaha. thanks14:12
ttxalthough posting publicly to a list could count as "communicating"14:13
fungii guess someone communicates resignations (we've only ever had one or two right?) to jonathan as well14:13
ttxfungi: I don't think we had formal resignations14:13
ttxonly "I won't run again" types ?14:13
ttxat least JB never communicated any to me :)14:14
fungithere was at least one where we ended up needing to appoint dtroyer to finish out someone else's term, right?14:14
fungior did i imagine it?14:15
ttxI think we did it by a proxy delegation mechanism14:15
fungiyeah, just trying to remember why we had a sudden vacancy for him to fill14:15
dhellmannevrardjp : please subscribe to the tc-members mailing list14:16
dhellmannlbragstad : please subscribe to the tc-members mailing list14:16
lbragstaddhellmann done14:17
*** jamesmcarthur has quit IRC14:18
*** jamesmcarthur has joined #openstack-tc14:18
*** jaypipes has joined #openstack-tc14:21
*** edmondsw_ has joined #openstack-tc14:26
dhellmannok, I have formally notified Alan of the election results: http://lists.openstack.org/pipermail/openstack-tc/2018-September/001552.html14:28
*** edleafe has quit IRC14:29
*** edmondsw has quit IRC14:29
*** edmondsw_ is now known as edmondsw14:29
openstackgerritDoug Hellmann proposed openstack/governance master: add Doug Hellmann as chair  https://review.openstack.org/60609814:31
fungithanks dhellmann! technically he's not the secretary, but i guess notifying the chair of the board also suffices14:34
dhellmannoh, ttx said he emailed alan14:36
dhellmannI'll forward that to jbryce14:36
ttxIn the past I waited until we had a chair, since in theory we have no chair right now to transmit the results yet :)14:37
ttxI guess past chair"14:37
ttxalso works14:37
dhellmannwe haven't formally approved the patch that removes the chair flag either14:38
*** jamesmcarthur has quit IRC14:38
dhellmannyay, limbo!14:38
*** jamesmcarthur has joined #openstack-tc14:38
toskyshouldn't there be a rule to avoid a "lack of power"? Like "the member which have been more time on the TC" or "the most voted one", or something like that?14:39
tosky(ok, ok, it's just for few days, but still)14:39
dhellmannin the past we've just said the current committee continues to serve until the new one is approved14:39
dhellmannthat's probably something else we should write down14:40
toskythat makes sense14:40
*** jamesmcarthur has quit IRC14:41
*** jamesmcarthur has joined #openstack-tc14:42
persiaWhen selecting chairs, I'd like to recommend that the chair be selected from those who were just elected, so that there isn't a gap of time without a chair (like we have now)14:42
persia(or would have if the election results were merged)14:42
*** annabelleB has quit IRC14:42
persiaAlternately, perhaps if the chair is subject to reelection, it makes sense to have the vice chair (if not also subject to reelection) be chair from when election results are posted until the chair is selected?14:43
*** annabelleB has joined #openstack-tc14:46
*** jamesmcarthur has quit IRC14:46
*** annabelleB has quit IRC14:49
ttxIn the past the previous chair would organize chair selection as first matter of business.14:51
dhellmanndone: http://lists.openstack.org/pipermail/openstack-tc/2018-September/001554.html14:52
persiaThat's good practice, but if we're writing down how to think it should work, we should allow for the case where the prior chair is not a member of the new TC: does the prior chair still organise in that case?14:52
persiadhellmann: Excellently written email, except I thought we were trying to use -dev for TC communications :)14:53
dhellmannpersia : this is one of the few reasons for this separate list to exist14:53
*** jamesmcarthur has joined #openstack-tc14:55
persiaAs someone who feels the separate list has value (and would like to see it used more for explicitly direct-TC comms unrelated to the wider community), I'll add that to the list of arguments against merge :)14:55
dhellmannI'm still torn on that one. I like not having to manage my own email alias for 13 people. OTOH, that's not *really* that big of a deal. And we're pretty good about not using that list for discussions already.14:56
zanebpersia: the defining characteristic of the -tc list isn't that only TC members read it, but that only TC members can post to it14:56
*** e0ne has quit IRC14:58
*** Bhujay has quit IRC14:58
*** jamesmcarthur has quit IRC14:59
cdentdhellmann: I think the question really comes down to: under what circumstances would you need to write to just the tc in a way that is different from say the keystone team want to write to just the keystone team?14:59
persiazaneb: as a non-TC member who has posted to that list, I think the definition is a little different :)15:00
cdentIf either of those things are common, then different lists make sense but if we insist that keystone team should be in public, then so too should the TC15:00
*** jamesmcarthur has joined #openstack-tc15:00
persiadhellmann: I think it isn't for discussion, more for specific contact announcement, etc.  I think it makes sense to use it on cc: for formal notice form the TC to other bodies, and as From: for formal notice to the TC.15:00
zanebpersia: I mean, you can but it's subject to moderation15:00
persiaWhereas any informal notice probably belongs on -dev (or -discuss)15:01
persiaMind you, that would probably work better were -owner not blackholed due to continuing spam attacks (who keeps spamming a dead email address for years consistently?  DOesn't that get expensive?)15:02
*** e0ne has joined #openstack-tc15:02
persiaAlso, I think an email alias for 13 people is fundamentally different.  I want to be able to read mail sent to the TC (even by the TC), even if I'm not properly supposed to act on it.15:02
persia(and, no, I don't want to do that by convincing specific ISPs to let me install packet replication devices)15:03
*** jaypipes is now known as leakypipes15:06
*** cdent has quit IRC15:18
mnaserdhellmann: i think your email to add jonathan never went through fyi (for tc members update)15:37
openstackgerritMerged openstack/project-team-guide master: Fix typo in stable branch maint guide  https://review.openstack.org/60607015:38
*** lbragstad is now known as elbragstad15:38
dhellmannoh, indeed, it went out from the wrong address so it's stuck in moderation15:38
dhellmannthanks mnaser15:38
dhellmannhmm, no, the one in moderation is from mnaser15:38
mnaseri just see that you resent the second email to jonathan but he's not in the to:  list15:38
dhellmannmnaser : http://lists.openstack.org/pipermail/openstack-tc/2018-September/001553.html15:39
dhellmannoh, he's in the CC list on my end15:39
dhellmannI wonder if the mailing list discards the CC list15:39
mnasermaybe!15:39
cmurphyi see evrardjp and alan on the cc list but not jonathan15:42
elbragstadi assume chair and vice chair titles will be added into https://review.openstack.org/#/c/605896/3/reference/members after the selection in a couple weeks?15:44
elbragstadadded back into*15:44
dhellmanncmurphy : there was a 2nd email15:45
dhellmannelbragstad : http://lists.openstack.org/pipermail/openstack-tc/2018-September/001554.html15:46
elbragstadoh - so that applies to vice chairs as well?15:46
elbragstadi just noticed that mnaser's name was shuffled in that that patch due to sorting.. and {vice chair} is missing15:48
elbragstadi assume that applies to both, then?15:49
smcginnisI forget, do we do election to election? Or should they be term based with the chair and vice chair alternating with overlapping terms?15:50
elbragstadaccording to 972c5c0ee57f473abc35ef49e01875882156725a that was added in July15:51
smcginnisAnother idea continuing on that would be to have the vice chair become the chair at the mid-point of their term so there is continuation.15:51
smcginniselbragstad: Vice chair is a new thing.15:51
elbragstadthat makes sense15:51
smcginnisIt was the "Doug wants to be able to go on vacation" addendum. :)15:52
elbragstad+115:52
persiasmcginnis: I think vice-chair becoming chair at midpoint is an excellent model.15:54
smcginnisIt would address the earlier concern mentioned of there being a gap.15:54
persiaThat means potential chairs get ~6 months of training.15:55
smcginnisAnd provide a nice pathway for more rotation.15:55
smcginnis+1 exactly15:55
persiaEffectively forced rotation, which is probably also good.  The sheer number of things needing to be done in handover (and continuing to be done) indicates that this is an area that could benefit from improvement.15:55
smcginnisIt would mean chair-ship would only be 6 months, but no reason someone couldn't keep going as chair-vice chair-chair-etc.15:57
*** cdent has joined #openstack-tc15:58
mnaseram I being signed up for more work?16:00
mnaser:p16:00
cmurphymnaser: we don't think you have enough to do16:00
mnasercmurphy: :D16:00
mnaserfwiw: just a heads up i'll be in europe starting OSDN till berlin, so i'll be in a different timezone for a while16:02
mnasernot that i dont think i'll probably always end up being here for all times anyways but just a heads up :)16:02
*** mriedem is now known as mriedem_lunch16:21
*** ianychoi has quit IRC16:39
*** ianychoi has joined #openstack-tc16:44
*** dtantsur is now known as dtantsur|afk16:45
*** jpich has quit IRC16:52
*** annabelleB has joined #openstack-tc17:00
*** edleafe has joined #openstack-tc17:31
*** e0ne has quit IRC17:44
*** jamesmcarthur has quit IRC17:48
*** mriedem_lunch has quit IRC17:52
*** diablo_rojo has joined #openstack-tc17:52
*** mriedem has joined #openstack-tc17:54
*** david-lyle has quit IRC17:56
*** e0ne has joined #openstack-tc18:02
*** TheJulia is now known as needssleep18:02
*** e0ne has quit IRC18:05
*** e0ne has joined #openstack-tc18:25
*** david-lyle has joined #openstack-tc18:41
*** david-lyle is now known as dklyle18:42
*** mriedem has quit IRC18:44
*** e0ne has quit IRC18:50
eanderssondhellmann, looks like glance hasn't been reserved yet on pypi?18:57
dhellmannhow did I  miss that one18:57
dhellmanneandersson : the pypi api reports that our ci system has permission to upload to the name glance18:59
eanderssonah sweet - maybe just showing up as 404 because nothing has been uploaded19:00
dhellmannyeah, I suspect that's the case19:00
eanderssone.g. magnum looks untouched since 2012 and the dev looks active19:02
eanderssonShould we try to reach out to take over that name?19:03
eandersson*Is it worth reaching out to him, or are we happy just keeping using openstack-magnum?19:03
dhellmanneandersson : I've contacted them19:04
dhellmannor at least tried19:04
dhellmannthat was yesterday, though, so I don't expect a response back yet19:05
dhellmannwhen I found the openstack-magnum name I figured it would be just as easy to keep using it19:05
eanderssonYea - I honestly like openstack-<project>19:05
dhellmannthere's something to be said for consistency19:06
eanderssonIt's just a little unfortunate that we mix19:06
dhellmannalthough then you have the renaming problem for new projects19:06
eanderssonNot a task to take lightly that is for sure19:06
dhellmannover the lifetime of the project it's probably better to not have to use the prefixed name, since it's one less change for everyone to keep up with19:07
*** elbragstad has quit IRC19:10
*** elbragstad has joined #openstack-tc19:10
*** e0ne has joined #openstack-tc19:29
*** e0ne has quit IRC19:34
*** annabelleB has quit IRC19:39
*** mriedem has joined #openstack-tc19:50
*** annabelleB has joined #openstack-tc20:03
*** openstackgerrit has quit IRC20:07
*** openstackgerrit has joined #openstack-tc20:55
openstackgerritMerged openstack/project-team-guide master: Add section on what to do with tox_install.sh  https://review.openstack.org/60387520:55
*** PapaOurs is now known as bauzas21:05
*** mriedem has quit IRC21:37
*** EvilienM is now known as EmilienM22:20
*** jamesmcarthur has joined #openstack-tc22:36
*** jamesmcarthur has quit IRC22:40
*** tosky has quit IRC22:42
*** elbragstad has quit IRC22:48
*** elbragstad has joined #openstack-tc23:01
*** elbragstad has quit IRC23:11
*** cdent has quit IRC23:22
*** jamesmcarthur has joined #openstack-tc23:34
*** jamesmcarthur has quit IRC23:39
*** annabelleB has quit IRC23:50

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