Wednesday, 2019-02-13

*** jamesmcarthur has joined #openstack-tc00:10
*** jamesmcarthur has quit IRC00:16
*** david-lyle has joined #openstack-tc00:18
*** tosky has quit IRC00:20
*** dklyle has quit IRC00:21
fungiedleafe: (cdent is gone again, but on the assumption he also will see this) keep in mind that our new project team application process is not in any way tied to ptl election cycles. take your time and don't let looming election deadlines pressure you00:43
fungiwhere ptls are concerned, we only require that "The leadership is chosen by the contributors to the project" and "Official project teams are expected to participate in all elections held after the team is accepted as official, regardless of how recently the team leadership may have been established." https://governance.openstack.org/tc/reference/new-projects-requirements.html00:44
fungiwhether you propose placement as a new team now or next month, you still need to have your contributors agree on an initial ptl and then participate in the first official ptl election once approved00:46
fungiif the tc approves placement too late to participate in the currently-scheduled election, then you participate in the next one00:47
*** diablo_rojo_phon has joined #openstack-tc00:48
fungithere's no rush, and really nothing to be gained from urgency00:48
*** openstackgerrit has quit IRC00:52
*** jamesmcarthur has joined #openstack-tc00:53
*** jamesmcarthur has quit IRC00:54
*** mriedem is now known as mriedem_away00:57
*** mriedem_away has quit IRC01:00
dhellmanno/01:00
* fungi is around for office hour as well, if any of the community has something to raise here01:01
lbragstad\o01:01
*** ricolin_ has joined #openstack-tc01:01
gmannTC office hour started01:02
mnaser\o/01:02
dhellmannspeaking of timing, I was hoping to catch tonyb[m] to make sure I understand the deadlines for being included in the election01:02
fungi /o\01:02
tonyb\o01:02
mnaseroh lovely we have tonyb :)01:03
* tonyb wonders id diablo_rojo (or diablo_rojo_phon) is around01:03
* dhellmann fights with his cat for space in the chair while we wait to hear01:04
*** jamesmcarthur has joined #openstack-tc01:04
tonybI agree with fungi that we don't *need* to do this as a matter of urgency as it's quite reasonable for the placement team to exist with an 'interim' PTL for the majority of the cycle01:04
* diablo_rojo_phon is here01:05
fungiit is, in fact, the way we designed the application process01:05
dhellmannI guess the question is whether melwitt would be willing to do that, or if missing the election deadline means the team has to do come up with an election on their own01:05
fungiwe've allowed teams to flexibly pick their initial ptl in the past as long as they agreed to participate in the first official election once approved01:06
tonybhowever, if there is a strong desire for the placement team to participate in this PTL election cycle Feb 19th would be best for us but we can delay that by 24-48 hours withouy putting the whole process at risk01:06
lbragstadif the interim placement PTL stepped out half way through train - there wouldn't be anything stopping placement from appointing another eligible individual, right?01:06
diablo_rojo_phonYeah. We can put off generator rolls a day or two without much issue.01:07
tonybdhellmann: they don't *need* an election to appoint an interim PTL (as fungi says)01:07
dhellmannI think the 19th is the earliest possible date we could approve the application01:07
tonybnormally the interim wouldn't be a whole cycle but we can do that01:07
fungihowever an ad hoc election is certainly one means of agreeing on an initial ptl01:07
dhellmannwell the tool says the 20th, because the 19th would be the 7th day the patch is open01:07
* tonyb can run an adhoc election01:07
fungii'm hard pressed to cite specific precedents on the spot, but we've in the past had teams do one-off civs polls before applying, or just announcing and holding a #vote in their irc meeting01:09
dhellmanneveryone involved seems ready to go ahead, and if I had replied to edleafe's email yesterday I think we wouldn't have an issue with the deadline01:09
tonybI'd need fungi and diablo_rojo_phon to agree but I think we can push the deadline[1] out to 22nd without makign live any harder for the election officals01:09
fungithat's also fine with me01:09
dhellmannthis team has already documented an agreement to have the "current nova PTL" serve as interim PTL, so I'm content that the contributors have selected a leader01:09
fungiyeah, that too is reasonable01:10
tonybthe deadline is the date by wich we need the electorate to set a preferred email address in gerrit *and* the date we need dhellmann/mnaser to tag the governance repo01:10
mnaseri don't want to speak on behalf the placement team but i think part of this is looking to be their own team with their own ptl for train01:10
tonybmnaser: they can do that regardless of the review landing by the deadline01:11
mnaserokay, fair, that's what you mention by the adhoc election?01:11
dhellmannso, if we get tc-members to vote +1 on the patch quickly we can get it approved by the 20th, which is just 1 day off from the deadline currently set. how do we feel about the likelihood of approval happening in the next 3 days?01:11
tonybmnaser: more or less yes01:11
fungithere's also nothing to prevent them from changing ptls over the course of the cycle if they want (and indeed we have provisions for this even when there are traditionally-elected ptls)01:11
lbragstaddhellmann seems fine to me01:11
tonybfungi: also true01:12
lbragstadfungi yeah - that's kinda what i was asking about earlier01:12
dhellmannwe do have lots of provisions in place to handle different cases. I guess the question is, what's going to involve the least amount of extra work for everyone?01:12
fungiif the placement team are ready to proceed now and have had the prerequisite conversations they want to have already, then approving them expediently is the least amount of extra work for everyone01:13
fungibut i want to be sure they're not feeling rushed to move ahead just because we have an election in sight01:14
tonybWhat fungi says01:14
dhellmannyeah, I think if we were having this conversation last week it wouldn't be an issue and they'd go ahead01:14
dhellmannso I don't think they're in a rush, per se, but so far everyone has indicated that they're ready01:14
tonybhowever doing nothing and letting the placement team select a PTL after the dealine is pretty much the same amount of work01:14
gmannif current nova team and melwitt ok with that there is no harm to go ahead01:15
dhellmannso if we can avoid having process stand in the way of what we all want, I think that's good01:15
tonybOkay, so it seems like we want to move the deadline out a couple of days01:16
dhellmannThat's what I would like to do. I'm hearing other folks express other options, but not necessarily preferences.01:16
tonybdhellmann: can you update http://git.openstack.org/cgit/openstack/election/tree/configuration.yaml#n10 to whatever value you think is best01:17
diablo_rojo_phonWorks for me.01:17
dhellmannsure01:17
tonybdhellmann: 22nd would be as late as I'm comforable going01:17
*** diablo_rojo has quit IRC01:17
dhellmannok, let's do that then01:17
tonyband that gives the TC a little extra wiggle room01:17
dhellmannyeah01:17
dhellmannthat gives us a day for other TC members to chime in on the upcoming patch :-)01:18
tonyb:)01:18
dhellmannhmm, what change do I make there? that's currentlly set up for TC elections. is there a separate file for the PTL settings?01:18
diablo_rojo_phon#decision01:19
gmannthat means 2 day shift to every timeline ?01:19
tonybthe email_deadline is shared between TC and PTL elections01:19
dhellmannok01:19
tonybso just move it from the 19th to 22nd01:19
tonybit wont impact any of the other dates01:19
tonybdhellmann: moving it means that we have ~4days to generate the electoral rolls instead of ~601:21
dhellmanntc-members: here's the patch to shift the deadline: https://review.openstack.org/63651001:21
dhellmanntonyb : if there's any way I can help with that, let me know01:21
fungitonyb: generate *and review*01:21
tonybfungi: yes01:22
gmanntonyb: yeah that i was wondering. is 4 days ok for election official ?01:22
tonybgmann: It shoudl be okay01:22
tonybgmann: less than 4 would be uncomfortable ;P01:22
dhellmannwould the 21st be better?01:22
dhellmannthat still gives us time to get the team in place on the 20th01:22
fungi4 days is doable01:22
gmannok01:23
fungiwe've in the past left ourselves 0 days, and that's decidedly a scramble01:23
tonybdhellmann: once 636416 merges can you tag HEAD of openstack/governance with feb-2019-elections01:23
dhellmannok. thanks, tonyb, fungi, & diablo_rojo_phon for accommodating this.01:23
dhellmanntonyb : yes01:23
tonybdhellmann: thanks01:23
diablo_rojo_phonNo problem dhellmann :)01:23
fungithanks for taking time to talk it through!01:24
tonybdhellmann: you're welcome happy to help01:24
diablo_rojo_phonYeah.. I don't miss the 0 days days lol. It seemed like we were always having issues generating the electorate.01:24
dhellmannwe should, at some point, talk about where to add a reminder to a calendar or process document to make sure future teams are aware of these deadlines, so we don't have to make a habit of this :-)01:24
tonybdhellmann: Yes.01:25
dhellmannit may already be on a calendar somewhere, actually01:25
tonybdhellmann: would the 'release' schedule be the best place?01:25
dhellmannthat would make sense, I think we put other election dates there01:25
tonybdhellmann: if so we can add a couple of items there01:25
dhellmannyeah, we do have the other election dates on https://releases.openstack.org/stein/schedule.html01:26
tonybdhellmann: I'll get it done for the *next* election cycle01:26
dhellmann++01:26
dhellmannI don't see PTL election dates there, yet, so we don't have anything to update on that calendar for this change01:26
tonybdhellmann: in R-5 under project specific01:27
fungiin the future when we assemble release schedules it might be nice to just make sure we plan the elections as part of that process01:27
tonybhttps://releases.openstack.org/stein/schedule.html#ptl-elections01:28
fungisaves us forgetting to do it until almost the last minute01:28
diablo_rojo_phonfungi: we'd be so prepared..01:28
diablo_rojo_phonScary thought lol01:28
tonybfungi: Yup, now that we have a handy tool for that we can plan the election dates as soon as the summit dates are set (and ideally have a location)01:28
fungioh, right, summits01:29
tonybOh that reminds me I need to start the U release nameing process now we know where we're going01:29
fungii guess we need to know summit schedules too, but we generally know them at least as far in advance as we do our release planning right?01:29
diablo_rojo_phonYeah that sounds right.01:30
dhellmanntonyb : ah, I see it now, they're in the right column instead of the center01:30
*** jamesmcarthur has quit IRC01:30
tonybfungi: Yup, U has been a little later but we're still ahead of the scedule there01:30
dhellmann(I was looking at the table at the top of the page)01:30
tonybdhellmann: Yeah, next time we could call them out as cross-project01:31
dhellmanntonyb : so, what does this change do to the actual PTL election? does that move?01:31
dhellmannor are we just giving you less time to do work between the 2 elections?01:31
tonybdhellmann: they're until project specific because in theory an election for $project_x doesn't impact $project_y01:31
dhellmannok, that makes sense. do I need a patch to update the schedule in the releases repo?01:32
tonybdhellmann: Nope, apart from when we can generate the rolls and tag the governance repo nothin else needs to chnage01:32
dhellmannok, cool01:32
tonybdhellmann: "least impact" #winning01:32
dhellmannhuzzah!01:33
*** jamesmcarthur has joined #openstack-tc01:33
zanebo/01:35
* dhellmann is happy to see zaneb did not fall into that volcano01:36
* smcginnis wonders how difficult a U name will be with Mandarin-named locations01:36
zaneb\o/01:36
smcginnisWelcome back zaneb01:36
zanebso much scrollback though01:36
* zaneb is in a volcano of scrollback01:36
smcginnisheh01:36
diablo_rojo_phonI vote Unicorn gets an exception.01:37
fungizaneb: a veritable irc eruption01:37
tonybsmcginnis: I'm thinking quite difficult01:37
smcginnisShould be interesting.01:37
fungidiablo_rojo_phon: openstack unfortunate unicorn01:37
fungi(we can be like ubuntu!)01:38
smcginnisUnfortunate cookie? :)01:38
tonybfungi: LOL01:38
* tonyb would vote for unicorn01:38
tonybbut I'd rather not do the exception proccess for another name ;P01:38
dhellmannwe should get our Chinese contributor community to help with that one01:38
gmanntonyb: :)01:39
dhellmanndiablo_rojo_phon : if we wanted unicorn, we should have gone to scotland01:39
tonybdhellmann: true.  I'll send out a call for help01:39
dhellmann++01:39
diablo_rojo_phondhellmann: I would have rather gone to Scotland I think but we'll see :)01:41
dhellmannEuroPython was there last summer. Scotland is lovely.01:41
tonybYeah I think we missed the boat on that one01:41
diablo_rojo_phonJealous!01:42
dhellmannSwitzerland this year, but I don't expect I'll be going this time01:42
fungiscotland is indeed lovely, but i bet china is lovely too01:42
dhellmannoh, I'm sure! I didn't mean to imply otherwise.01:43
lbragstadi was lucky enough to see the terra cota army when i was there01:43
lbragstadthat was pretty incredible01:43
dhellmannnice01:43
lbragstadwe also happen to stroll by the oldest document educational facility in the country01:44
* dhellmann is being paged and has to drop off01:44
fungig'night dhellmann, and thanks again!01:46
lbragstado/01:46
*** jamesmcarthur has quit IRC01:53
*** jamesmcarthur has joined #openstack-tc01:54
*** jamesmcarthur has quit IRC02:05
*** jamesmcarthur has joined #openstack-tc02:16
*** jamesmcarthur has quit IRC02:28
*** jamesmcarthur has joined #openstack-tc02:59
*** jamesmcarthur has quit IRC03:06
*** jamesmcarthur has joined #openstack-tc03:26
*** jamesmcarthur has quit IRC03:30
*** ricolin_ has quit IRC03:48
*** spsurya has joined #openstack-tc03:54
*** lbragstad has quit IRC04:32
*** penick has quit IRC05:24
*** ricolin has joined #openstack-tc05:46
*** Luzi has joined #openstack-tc06:43
*** diablo_rojo has joined #openstack-tc06:50
*** dangtrinhnt has quit IRC07:06
*** dangtrinhnt has joined #openstack-tc07:07
*** adriant has quit IRC07:11
*** adriant has joined #openstack-tc07:11
*** ricolin has quit IRC07:19
*** ricolin_ has joined #openstack-tc07:19
*** jamesmcarthur has joined #openstack-tc07:26
*** jamesmcarthur has quit IRC07:31
*** e0ne has joined #openstack-tc07:36
*** ricolin_ has quit IRC07:45
*** ricolin has joined #openstack-tc07:46
*** diablo_rojo has quit IRC08:10
*** tosky has joined #openstack-tc08:53
*** jpich has joined #openstack-tc09:03
*** e0ne has quit IRC09:06
*** e0ne has joined #openstack-tc09:07
*** ricolin has quit IRC09:19
ttxThanks cmurphy for that help-needed thread email -- I was trying to make that "it's not the same depth of involvement" point but was a bit unsuccessful :) We need to keep the bar high enough if we want that initiative to be successful. I'd rather have a couple offers and one success, than a list of 20 with no success.09:24
cmurphyttx: ++09:27
ttxWe probably need a new term. if on-boarding and mentoring are already taken09:27
ttx(and to be clear, I think we need both, but confusing them is not helping either)09:28
cmurphyand there are clearly components of both that would be needed for this but it's not the full story, i'm not sure what the right word for it is either09:29
ttxMaybe Padawan09:31
ttx(you have the force, you just need help and perspective to master it)09:32
cmurphylol09:32
ttxAlso makes clear the type of commitment it is. You only have one padawan09:32
ttxAnd the Padawan is clearly on track to become a master and have padawans of his own.09:33
ttx(something the "internship" vocabulary is missing)09:33
* cmurphy is fully supportive of incorporating more star wars vocabulary09:34
*** e0ne has quit IRC09:34
ttxAlso I'm known for taking analogies a few steps too far, with joy.09:35
cmurphy:)09:35
*** openstackgerrit has joined #openstack-tc09:52
openstackgerritNatal Ngétal proposed openstack/project-team-guide master: Cleanup the configuration file.  https://review.openstack.org/63658009:52
*** cdent has joined #openstack-tc09:56
*** e0ne has joined #openstack-tc10:46
*** e0ne_ has joined #openstack-tc10:50
*** e0ne has quit IRC10:52
*** e0ne has joined #openstack-tc11:56
*** e0ne has quit IRC11:57
*** e0ne_ has quit IRC11:57
*** e0ne has joined #openstack-tc12:08
*** e0ne has quit IRC12:12
*** e0ne has joined #openstack-tc12:22
*** mriedem has joined #openstack-tc13:08
*** e0ne has quit IRC13:11
*** jamesmcarthur has joined #openstack-tc13:14
*** e0ne has joined #openstack-tc13:17
*** e0ne_ has joined #openstack-tc13:20
*** e0ne has quit IRC13:23
*** jamesmcarthur has quit IRC13:29
*** e0ne_ has quit IRC13:40
*** lbragstad has joined #openstack-tc13:41
fungii'm mostly seeing the variety of mentee/intern/protege options as a gradient/continuum/nebulous (dare i say) cloud of options for folks with varying degrees of familiarity and experience13:42
fungimy main concern is with the target audience of each, and whether they exist at all in some cases13:42
dhellmannttx, cmurphy : as long as we don't require the haircut, I'm ok with using the term padawan13:43
fungii semi-regularly see newcomers to the community looking for something to work on, but almost never see someone who is experienced and familiar with our culture and workflows who doesn't already have a fairly specific focus (or more often, a dozen of them)13:44
cmurphydhellmann: i can live without the haircut if we make sure to give them lightsabers13:44
*** e0ne has joined #openstack-tc13:45
dhellmannI'd like to see that awards ceremony on the keynote stage13:45
fungiconversely, i can't think of anyone with a deep knowledge in various bits of openstack who wouldn't readily engage with a prospective protege if there was some expectation that they'd stick around and lighten their own burden13:45
cdentall good points fungi. That's why I think what the help-wanted stuff is really about is encouraging corporate patrons to invest some longer term participants. They don't have to be full time participants (those are increasingly unicorns of the past).13:45
cdentbut people who sell this stuff need to inevst13:46
cdentwe can help them by pointing out where13:46
fungiwhich drives back to the earlier points, that the effective target audience in that case is the business interest or patron, not the actual mentor/sensei13:47
* cdent nods13:47
funginor the prospective trainee13:47
fungi(unless the hope is that they'll lobby their employer)13:48
cdent"lobby employer" is not an easy thing to do without some kind of ooomph making thing13:48
cmurphyI think what we're seeing with the many typofix-storm-commits is that some employers do have some policy of "do upstream" but haven't given guidance to their employees on where to focus13:49
cmurphyso directing this at those people would still be good13:49
*** jamesmcarthur has joined #openstack-tc13:50
*** e0ne_ has joined #openstack-tc13:50
dhellmannI had moderate luck with focusing some of those people on the zuul v3 shift this cycle. It wasn't completely successful, but I think it shows that doing a bit of direct outreach can go a long way.13:50
dhellmannand by "direct outreach" I mean that I emailed 2-3 people individually to ask them to help, not a blanket email to the mailing list13:51
*** e0ne has quit IRC13:51
cmurphydiablo_rojo_phon: ^ maybe a good tactic to start taking when reaching out, "I want you to help do this" instead of "help me help you help us"13:52
dhellmannI'm not sure how I would have turned those same volunteers into more knowledgeable zuul config experts, or had them dealing with bugs or a feature in a smaller code base, though. The amount of back and forth discussion we had was somewhat limited by a language barrier that made it hard for me to judge their technical ability.13:53
dhellmannObviously a big part of that issue is on my side of the language barrier. We did work together successfully at the tasks I had in mind, so I'm happy with the outcome so far, but feel like I would have had a hard time taking the team further.13:54
openstackgerritNatal Ngétal proposed openstack/project-team-guide master: [Documentation] Fix links releases.  https://review.openstack.org/63212113:55
openstackgerritThierry Carrez proposed openstack/governance master: Do not mention Extra ATCs if there are none  https://review.openstack.org/63663214:02
openstackgerritThierry Carrez proposed openstack/governance master: Add link to activity metrics to team pages  https://review.openstack.org/63663314:02
*** e0ne_ has quit IRC14:04
dhellmannsmcginnis : do you want to turn your Code-Review vote on https://review.openstack.org/#/c/636632/1 into a Roll-Call vote?14:13
dhellmannditto for https://review.openstack.org/#/c/636633/14:13
smcginnisdhellmann: Done. Figured that was more of a code change than anything else, but both works.14:13
dhellmannyeah, the tool is looking for TC member votes, and only TC can vote as Roll Call so...14:13
smcginnisAh...14:14
dhellmannI was trying to avoid confusion about whether a vote from someone "counts"14:14
smcginnisThat keeps it simple.14:15
dhellmannyeah, the alternative was doing things like looking up people's names and I'm too lazy to build that14:16
smcginniss/too lazy/too efficient/ ;)14:17
dhellmanntomato, tomato14:17
openstackgerritMerged openstack/governance master: Do not mention Extra ATCs if there are none  https://review.openstack.org/63663214:21
openstackgerritMerged openstack/governance master: Add link to activity metrics to team pages  https://review.openstack.org/63663314:21
*** jamesmcarthur has quit IRC14:26
*** e0ne has joined #openstack-tc14:29
*** e0ne_ has joined #openstack-tc14:35
*** e0ne has quit IRC14:35
*** e0ne_ has quit IRC14:41
*** e0ne has joined #openstack-tc14:50
*** e0ne_ has joined #openstack-tc14:55
*** jamesmcarthur has joined #openstack-tc14:55
*** e0ne has quit IRC14:55
*** penick has joined #openstack-tc14:59
fungiregarding ^ i'm unconvinced we should be promoting arbitrary "activity" metrics at all as it sends a conflicting message about what we should value as a community, but i suppose i'm in the minority there15:13
smcginnisI kinda had the same thought.15:13
fungiit feels like an unnecessarily competitive and divisive sort of thing to promote15:14
cdentwait, what? we're linking to stackalytics?15:14
cmurphyo.015:14
cdentI thought we had decided that was double bad?15:15
fungiclearly more of us should have weighed in on the review15:15
smcginnisIt's useful and harmful at the same time.15:15
cdentI wasn't even aware it was a relevant review, since it is in code15:16
smcginnisFrom what I understand, it's to get rid of this: https://www.openstack.org/software/releases/rocky/components/nova15:16
smcginnisSo in that respect, I think it's at least marginally better.15:16
cdenthuh15:17
cdenti suppose access to detailed information is perhaps better than summaries15:18
smcginnisNow whether no data is better than potentially misleading data, that's another relevant point that could probably use some discussion.15:19
cdentI don't actually mind metrics all that much. I'm simply confused because I thought we had decided to stop but it seems not.15:20
cmurphysomewhat relevant https://review.openstack.org/63393915:22
fungito me, at least, data on www.openstack.org is coming from the osf and not from the technical committee so we at least have the ability to distance ourselves from it. when it's hosted under governance.openstack.org/tc it becomes a lot harder to say we're just providing it for reference even though we either see minimal value in it or in some cases even consider it actively harmful15:30
* cdent nods15:31
smcginniscmurphy: I like that.15:31
fungithat change is indeed a marvellous replacement for that original placeholder bullet from the forum etherpad15:35
smcginnisSo... are folks thinking https://review.openstack.org/#/c/636633/ should be reverted? Not sure if ttx is around yet, but would be good to get his input on the overall intent.15:38
fungii at least wouldn't mind a bit more brainstorming on how we can avoid making it look like we're running a competition for which projects get the most changes/reviews15:42
fungii'm assuming some portion of our wider ecosystem finds this information compelling, i'm just unconvinced that our governance site is an appropriate place to provide them with (links to) that data15:43
smcginnisI did like that we were just providing a link and not trying to pull in and display that data.15:45
fungiyep15:46
smcginnisTho that does not help the perception the stackalytics is an OpenStack run thing and an authoritative source for all activity.15:46
fungithough also, stackalytics has ceased to be open source as best i can tell (ignoring as of yet unfulfilled responses on twitter to the contrary) so linking to it is little different than linking to a proprietary contribution tracker like ohloh (or whatever it's been renamed to recently)15:47
fungiwhy limit ourselves to just one?15:47
*** Luzi has quit IRC15:55
*** ianychoi has quit IRC16:08
dhellmannhmm, I guess I should have used formal-vote on that. Someone go ahead and propose a revert, I'll fast-approve it, then we can redo ttx's patch under different rules16:24
openstackgerritSean McGinnis proposed openstack/governance master: Revert "Add link to activity metrics to team pages"  https://review.openstack.org/63666316:25
*** diablo_rojo has joined #openstack-tc16:37
mnaserdhellmann: zuul +1'd, i can +w if you'd likee.16:38
dhellmannmnaser : thanks, on it16:38
dhellmannI'll go ahead and prep an unrevert of ttx's patch on top of sean's16:39
mnaser++16:40
openstackgerritDoug Hellmann proposed openstack/governance master: Revert "Revert "Add link to activity metrics to team pages""  https://review.openstack.org/63666516:41
*** e0ne has joined #openstack-tc16:47
*** e0ne_ has quit IRC16:48
openstackgerritMerged openstack/governance master: Revert "Add link to activity metrics to team pages"  https://review.openstack.org/63666316:49
*** jamesmcarthur has quit IRC16:51
ttxyes the general idea is to stop talking about teams in software pages and focus on... software. So move the "information" that was published there to the existing team pages (rather than do new ones)16:58
ttxBut I understand that promoting Stackalytics might be undesirable. On one hand it buries that information further down, but on the other it taints the TC website a bit16:59
*** jamesmcarthur has joined #openstack-tc17:00
fungithe message becomes a different one when the messenger changes17:16
ttxfungi: worth noting that it's not the only stackalytics dependency in the governance repo :) https://git.openstack.org/cgit/openstack/governance/tree/tools/team_fragility.py#n3717:21
ttxwe used to compile a *tag* from that17:21
*** jamesmcarthur has quit IRC17:22
ttxSo we might want to remove that remnant as well.17:22
fungiyep17:22
*** e0ne has quit IRC17:25
*** ricolin has joined #openstack-tc17:25
*** jamesmcarthur has joined #openstack-tc17:34
*** dtantsur is now known as dtantsur|afk17:37
*** jpich has quit IRC17:52
*** ricolin has quit IRC17:58
*** e0ne has joined #openstack-tc18:22
*** mriedem is now known as mriedem_away18:52
openstackgerritJeremy Stanley proposed openstack/governance master: Remove team fragility stats script  https://review.openstack.org/63672119:07
fungittx: ^ thanks for the pointer, we can discuss that too19:07
*** cdent has quit IRC19:31
*** cdent has joined #openstack-tc19:32
*** bsilverman has quit IRC19:46
*** e0ne has quit IRC19:47
*** jamesmcarthur has quit IRC19:55
*** jamesmcarthur has joined #openstack-tc20:07
*** jamesmcarthur has quit IRC20:12
*** ijolliffe has joined #openstack-tc20:16
*** jamesmcarthur has joined #openstack-tc20:16
*** jamesmcarthur has quit IRC20:35
*** mriedem_away is now known as mriedem21:04
*** jamesmcarthur has joined #openstack-tc21:25
*** jamesmcarthur has quit IRC21:30
*** whoami-rajat has quit IRC21:32
*** openstackgerrit has quit IRC22:22
*** dangtrinhnt_ has joined #openstack-tc22:31
*** dangtrinhnt has quit IRC22:33
*** eandersson has quit IRC22:33
*** gouthamr has quit IRC22:35
*** gouthamr has joined #openstack-tc22:36
*** jamesmcarthur has joined #openstack-tc22:43
*** jamesmcarthur has quit IRC22:48
*** jamesmcarthur has joined #openstack-tc22:51
*** eandersson has joined #openstack-tc22:59
*** david-lyle has quit IRC23:02
*** dklyle has joined #openstack-tc23:02
*** jamesmcarthur has quit IRC23:07
*** jamesmcarthur has joined #openstack-tc23:27
*** jamesmcarthur has quit IRC23:33
*** ijolliffe has quit IRC23:38
*** tosky has quit IRC23:39
*** jamesmcarthur has joined #openstack-tc23:49
*** lbragstad has quit IRC23:52
*** jamesmcarthur has quit IRC23:53
*** jamesmcarthur has joined #openstack-tc23:56

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