Monday, 2018-11-26

*** jamesmcarthur has joined #openstack-tc00:04
*** jamesmcarthur has quit IRC00:10
*** jamesmcarthur has joined #openstack-tc00:11
*** tosky has quit IRC00:39
*** lbragstad has joined #openstack-tc01:14
*** jamesmcarthur has quit IRC01:19
*** eandersson has quit IRC01:45
*** jamesmcarthur has joined #openstack-tc01:46
*** jamesmcarthur has quit IRC02:05
*** jamesmcarthur has joined #openstack-tc02:08
*** lbragstad has quit IRC02:08
*** jamesmcarthur has quit IRC02:45
*** jamesmcarthur has joined #openstack-tc02:53
*** jamesmcarthur has quit IRC03:10
*** lbragstad has joined #openstack-tc03:14
*** edmondsw has quit IRC03:34
*** lbragstad has quit IRC04:32
*** whoami-rajat has joined #openstack-tc06:21
*** Luzi has joined #openstack-tc07:00
*** e0ne has joined #openstack-tc07:46
*** jamesmcarthur has joined #openstack-tc08:05
*** jamesmcarthur has quit IRC08:09
*** tosky has joined #openstack-tc08:46
*** TheJulia_ has joined #openstack-tc09:17
*** aprice_ has joined #openstack-tc09:17
*** spsurya_ has joined #openstack-tc09:17
*** csatari_ has joined #openstack-tc09:18
*** jpich has joined #openstack-tc09:18
*** bauzas_ has joined #openstack-tc09:23
*** mgagne_ has joined #openstack-tc09:23
*** spsurya has quit IRC09:25
*** csatari has quit IRC09:25
*** bauzas has quit IRC09:25
*** jroll has quit IRC09:25
*** EmilienM has quit IRC09:25
*** mgagne has quit IRC09:25
*** TheJulia has quit IRC09:25
*** aprice has quit IRC09:25
*** ildikov has quit IRC09:25
*** bauzas_ is now known as bauzas09:25
*** spsurya_ is now known as spsurya09:25
*** csatari_ is now known as csatari09:25
*** aprice_ is now known as aprice09:25
*** TheJulia_ is now known as TheJulia09:25
*** jroll has joined #openstack-tc09:32
*** ildikov has joined #openstack-tc09:34
*** jaosorior has joined #openstack-tc09:38
*** cdent has joined #openstack-tc10:13
cdentI have spun up some energy at $work to get a few more people interested in paying attention upstream, but there are the usual fears about the amount of time and energy required to be "relevant". We may need some kind of PR.11:32
cdentby which I public relations, not pull request11:34
*** jamesmcarthur has joined #openstack-tc12:05
*** e0ne has quit IRC12:09
*** jamesmcarthur has quit IRC12:10
*** EmilienM has joined #openstack-tc12:57
*** dtantsur|afk is now known as dtantsur|mtg12:59
evrardjpcdent: habits are tough to beat13:00
evrardjpcdent: what do you mean by PR there, and what do you really mean by 'be relevant'?13:01
evrardjpI thought there was a guide on the works on benefits of upstream involvments13:01
cdentthe public relations is "making it more visible that we are working on making contribution to openstack easier". The benefits aren't the issue. It's the challenges that individuals face "getting noticed"13:02
cdentrelevance == "getting significant code merged"13:02
cdentin the larger projects, espeically nova, there's a lot of fear about that13:02
cdent"I had to prostrate myself to the nova cores for months"13:02
cdentthat kind of thing13:03
evrardjpwell that's very team dependant though13:05
*** weshay_pto is now known as weshay13:05
cdentevrardjp: yes, definitely, but given nova's size and position, it's relevant13:06
cdentand it is becoming less of an issue (nova is getting "nicer") but there are _many_ people out there who don't know that13:07
cdentand still feel like their effort will be wasted as thus will not bother trying13:07
evrardjpso you want a public message out that we're _day to day_ improving the easiness of contributing to openstack13:07
cdentI want that we are making that effort to improve things to be more visible13:08
evrardjpI think TheJulia 's initiative of anti-nitpicking and documentation like this guide (https://docs.openstack.org/contributors/index.html ) is on the right path,but I am not sure how I can raise that visibility at my level13:09
evrardjpcdent: well if you were (hypothetically) creating a big feature, that would appear in the release notes or in cycle highlights13:09
TheJuliaGood morning13:09
cdentmornin' TheJulia13:10
evrardjpI am very confused on what I can do on this level13:10
cdentevrardjp: I think being conscious of it is the first step13:10
evrardjpsorry to have removed you from sleep TheJulia , we were talking about culture13:10
evrardjpI thought your initiative was a good example :)13:10
TheJuliaI was already awake13:10
evrardjpcdent: that's fair13:11
cdentthe visibility I'm talking about is not after a feature has been merged. I'm talking about making the visibility of things like TheJulia's initiative _more_ visible13:11
TheJuliachanging culture... at least in my experience... is something that has to be done slowly and methodically... actively forcing creates resistance13:11
evrardjpcdent: to be honest, I have heard the same kind of echoes on my side of the pond13:11
cdentso that people who are generally averse to contributing (because of history) have some hope and appreciation that things are changing13:11
cdentpeople within vmware are _super_ averse because of history13:12
*** jamesmcarthur has joined #openstack-tc13:12
evrardjpI guess word of mouth (if that's the right term) helps there13:12
TheJuliaYeah, but that only spreads so far13:12
evrardjpI guess this is why cdent raised the point :)13:13
TheJulia++13:13
evrardjpsadly I have no clue on how to do that on an openstack wide level13:13
*** jaypipes has quit IRC13:13
evrardjpI don't think it stops spreading though, it's just slow13:13
evrardjp(I mean the word of mouth thing)13:14
evrardjpmaybe there are people more experienced than me on this -- experience in other communities would help -- I think kernel for example13:14
*** jamesmcarthur has quit IRC13:31
*** gouthamr has quit IRC13:34
*** gouthamr has joined #openstack-tc13:40
*** zaneb has joined #openstack-tc13:49
*** jamesmcarthur has joined #openstack-tc13:50
*** mriedem has joined #openstack-tc13:54
*** lbragstad has joined #openstack-tc14:07
*** zbitter has joined #openstack-tc14:17
*** zaneb has quit IRC14:18
*** jroll has quit IRC14:24
*** jroll has joined #openstack-tc14:25
*** zbitter is now known as zaneb14:28
*** whoami-rajat has quit IRC14:55
*** zaneb has quit IRC15:01
*** zaneb has joined #openstack-tc15:01
*** e0ne has joined #openstack-tc15:09
*** Luzi has quit IRC15:26
*** jamesmcarthur has quit IRC15:32
*** jamesmcarthur has joined #openstack-tc15:33
*** zbitter has joined #openstack-tc15:33
*** zaneb has quit IRC15:36
*** zbitter has quit IRC15:39
*** zbitter has joined #openstack-tc15:39
*** jamesmcarthur has quit IRC15:46
*** jamesmcarthur has joined #openstack-tc15:52
*** jamesmcarthur has quit IRC15:57
*** jamesmcarthur has joined #openstack-tc16:28
*** e0ne has quit IRC16:39
fungii have to wonder how many such negative experiences come from a place of developers working at vendors trying to get features added for the benefit of their employers, and failing to adequately explain the benefit to the project/community of prioritizing said features16:43
fungi"we have 10x more submissions than we can effectively review/merge, what makes yours more important than at least 90% of the backlog?"16:44
cdentfungi: I suspect that's a factor, but I also think, as zbitter has pointed out recently, we don't prioritize responsiveness to casual contributors16:46
*** zbitter is now known as zaneb16:46
cdents/don't/haven't historically/16:46
fungiyeah, i do agree that a failure to improve responsiveness (as the expense of throughput elsewhere of course) has been short-sighted and discouraged involvement from some who could in time get involved enough to help reduce rather than increase the workload16:47
fungier, at the expense16:47
fungiinvestment in the future and all that16:47
fungihopefully that's changing too16:48
cdentit seems to be16:48
cdentwhich is why I wonder if we migh benefit from talking it up a bit16:49
evrardjptbh if there was a dashboard in each project that prioritizes those 'casual contributors' reviews, I'd do my homework better. Sometimes there are just too many reviews...16:54
cdenttoo many review is definitely an issue16:55
*** whoami-rajat has joined #openstack-tc17:03
openstackgerritSean McGinnis proposed openstack/governance master: Explicitly declare Stein supported runtimes  https://review.openstack.org/61108017:24
notmynameevrardjp: FWIW, we've got a dashboard (http://not.mn/review.html) that has a "small things" section. maybe it's similar to what you're looking for?17:38
*** diablo_rojo has joined #openstack-tc17:48
*** jpich has quit IRC17:50
smcginnisnotmyname: I get a 404 on that.17:50
notmynamedoh. forgot the s17:59
notmynamehttp://not.mn/reviews.html17:59
notmyname(there's more that one review)17:59
smcginnisThat's better.18:00
cdentfungi: Did you see this https://anticdent.org/mailing-list-review.html which I published in a fit of angst about mailing list behavior. I was just reminded of it again because of the lack of reply-to list on opensack-discuss18:02
*** jamesmcarthur has quit IRC18:02
fungicdent: yeah, the main reason we aren't injecting/overriding reply-to (aside from the fact that 2 of the 4 lists we're folding into it didn't do it historically either) is that it would break dmarc/dkim signatures18:17
cdentwhich seems pretty irrelevant for emails to this kind of list. Why not break them?18:17
fungibecause then if you're a subscriber with an address on an mta which checks dkim signatures, it will reject those messages and the listserv will unsubscribe you18:18
fungithis has been a chronic issue with our earlier lists, which is also why we're not appending a footer attachment nor mangling the subject line18:19
* cdent shrugs18:20
fungisomething to add would be recommending a mailer that has a reply-to-list feature. most do. there are some unfortunately very popular web-based ones which have decided rfc 2369 support is too much trouble18:20
fungiin mutt, L does this for me18:20
fungito be clear, i think dmarc/dkim enforcement is silly. however a number of large organizations who contribute to projects using our mailing lists have 1. mailserver policies which force sign all outgoing messages, 2. mailserver policies which reject incoming messages with an invalid dkim signature, and 3. employee policies preventing them from using personal e-mail to engage on these projects18:23
cdentblargh18:23
fungiand the end result is that contributors working for a company which does at least 1 and 3 end up sending messages to the list that cause contributors working for a company which does at least 2 and 3 to be repeatedly unsubscribed from our mailing lists18:25
cdentI'm trying to decide who I want to hurt more18:26
fungi(as well as miss out on receiving those posts their mailserver rejected)18:26
cdentbut I definitely want to hurt someone18:26
jrollhurt the corporations, not the people :)18:27
cdentyessiir18:29
fungiyeah, we evaluated some half a dozen potential solutions to this problem, including do nothing, preemptively reject any dkim-signed messages received by the listserv, strip dkim signatures and mangle the from header so that it appears to originate from the ml, encapsulate every message in a mime multi-part wrapper before forwarding...18:29
fungithe "simplest" solution is to have the ml simply not modify forwarded messages in any way which dkim signatures are likely to be invalidated18:30
cdentI guess I'll just cook the incoming messages locally myself, which helps no one else, but oh well18:31
fungifairly new mm2 versions have an adaptive solution which either rewrites the from and strips dkim or mime encapsulates it (configurable choice) only for messages with dkim signatures, but that also leads to a lot of inconsistency18:31
*** e0ne has joined #openstack-tc18:41
*** eandersson has joined #openstack-tc18:54
*** whoami-rajat has quit IRC20:06
*** e0ne has quit IRC21:21
*** e0ne has joined #openstack-tc21:30
*** e0ne has quit IRC22:25
*** aspiers has quit IRC22:27
*** cdent has quit IRC22:44
*** aspiers has joined #openstack-tc22:45
*** jamesmcarthur has joined #openstack-tc23:11
*** mriedem is now known as mriedem_away23:13
*** jamesmcarthur has quit IRC23:15
*** dangtrinhnt has quit IRC23:18
*** dangtrinhnt_ has joined #openstack-tc23:18
*** tosky has quit IRC23:32
*** tosky has joined #openstack-tc23:32

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