Tuesday, 2018-07-03

*** edmondsw has joined #openstack-tc00:23
*** edmondsw has quit IRC00:28
*** dklyle has quit IRC00:55
*** ricolin has joined #openstack-tc02:09
*** diablo_rojo has quit IRC02:29
*** diablo_rojo has joined #openstack-tc02:44
*** diablo_rojo has quit IRC03:01
*** edmondsw has joined #openstack-tc05:48
evrardjpmnaser: yes I will05:51
*** edmondsw has quit IRC05:53
evrardjpmnaser: I thought this had to stay for releasing on existing stable branches though, so let me double check05:54
*** openstackgerrit has quit IRC06:49
*** edmondsw has joined #openstack-tc07:36
*** edmondsw has quit IRC07:41
*** ricolin has quit IRC07:55
*** jpich has joined #openstack-tc08:03
*** ricolin has joined #openstack-tc08:27
*** cdent has joined #openstack-tc08:56
ttxtc-members assemble09:00
ttx#startmeeting tc09:01
openstackMeeting started Tue Jul  3 09:01:01 2018 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.09:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:01
*** openstack changes topic to " (Meeting topic: tc)"09:01
openstackThe meeting name has been set to 'tc'09:01
ttx#chair cdent09:01
openstackCurrent chairs: cdent ttx09:01
* ttx copies fragility analysis top results to the health tracker for further analysis09:04
*** cdent_ has joined #openstack-tc09:04
TheJuliaOddly enough I am awake at the moment...09:05
cdent_Looks like my previous message didn't make it through: "My main topic of concern recently is how to make sure that we extract something useful from, and actually do something with, the various threads of discussion on adapting openstack to "now""09:05
*** cdent has quit IRC09:05
*** cdent_ is now known as cdent09:05
cdentThis is not still jetlag is it TheJulia ?09:06
cdentgood luck?09:07
cdentmy sleep sadness story is Hayfever09:08
TheJuliaIt might be the same actually, no rain to knock allergens from the air09:08
TheJuliaI guess one thing i wonder is given "now", how do we also foster an environme t where those discussions take place outside of our circle with effect and outcome.09:11
cdentyes, that's an excellent point09:11
cdentIt's something I've really been struggling with a lot lately. Feeling very en-bubbled, but not sure how to get out given the constraints of existing obligations.09:12
TheJuliaTrust with ahared purpoae is one way, but if you trust one person and their corporate overlords change their focus... There is not much that can be done.09:13
TheJuliaShared purpose09:14
TheJuliaSo setting the stage or environmenr where rhose discussions of directions taken are the resulting outcomes of our tuning, not our direct actions. If that makes sense.09:15
cdentIn my mind that translates to getting people to believe in something (the shared purpose)09:17
persiaTo me, getting the existing openstack community to believe in a shared purpose would harden the walls of the bubble.09:18
persiaRather, I suspect new, fresh input is needed from a wider group that the current smaller group needs to also consider part of "us": those folk probably have new/different purposes09:18
cdentperhaps people != existing openstack community09:18
persia(but me calling them "those folk" is an example of the problem, really)09:19
TheJuliacdent: what about shared context instead of purpose09:19
cdentI guess it depends on what you mean by those terms but in my head the first is a requirement for the second, but only the second is something that results in action09:20
cdentthat is one people have a shared context they may be able to recognize a shared purpose and choose to collaborate09:21
persiaIn another context, I'm currently dealing with a small project (tens of developers) that has started to suffer from velocity issues, both in terms of review bandwidth and in terms of progress on shared features (as interest groups start to choose to have "feature branches" as operational forks).  This isn't the same problem as OpenStack, but it feels similar in some ways.09:22
persiaOne of the things we're doing there is removing the authority of those who have previously been responsible for guiding the main "upstream" direction, and instead just merging everything that passes CI, with the obligation on the interest groups to write tests for anything they care about.09:23
persiaThis has caused a number of interesting flame wars, but one of the most interesting aspects to me is that those whose authority was removed seem to be more active in reviews than before their authority was removed.09:24
cdentTheJulia: my feelings these days is that more us need to take a more active role in nudging what the shared purpose might be, by sharing (random) ideas. Which half the time sounds like so much noise, but if any of them land, that's good.09:24
cdentpersia: that is interesting09:24
persiaAlso, the teams that had been slowly moving towards forks seem to be more active about getting tests for their use cases into "upstream", and getting their features landed.09:24
TheJuliapersia: was it that they found new purpoae in trying to assert authority in code review?09:24
persiaIt's early days with the transition, but it seems to be working so far.09:24
*** edmondsw has joined #openstack-tc09:25
persiaTheJulia: No, that those responsible for their time allocation suddenly saw a lot more value in them preemptively reviewing things :)09:25
TheJuliaI see09:26
cdentttx: I think we need to start thinking in terms of optionally breaking existing users. Things like "people can choose to use nova-compute or if they want they can choose to upgrade to nodelet the all-in-one compute node agent"09:27
TheJuliaSo i do agree with you cdent in thay we all, community collectively need to better share our xontext, not purpose. With that in the open, it hopefully becomes easier to negoriate and plan09:27
persiaWhile the details differ, I think the audience is similar to the "now" issue: the important bit is making sure that things happen visibly to an audience that is able to allocate the resources to accomplish the desired goals.  Just getting all the developers excited about things, with shared context and purpose, may not allow progress.09:27
ttxok, I dropped nuggets of fragility facts onto the Health tracker for TC liaisons to further investigate09:27
cdentttx: if we don't provide options for "different from how it always was" there's little to perceive as change09:28
* cdent looks at tracker09:28
*** edmondsw has quit IRC09:29
ttxusing data from https://etherpad.openstack.org/p/rocky-2-bus-factor09:29
ttx(which was generated by the script at https://review.openstack.org/#/c/579142/ )09:29
TheJuliaI'm not sure excited is the desirable target, in the grand state machine of the universe. Excited implies that we convinced them on shared vision instead of ahared context where we understand each other.09:30
*** e0ne has joined #openstack-tc09:33
* cdent smells brake dust09:34
cdentand there's ringing in my ears from the way that conversation seemed to come to a screeching halt09:35
* cdent sighs09:35
ttxsorry, was still dealing with wiki edits09:36
ttxAlso about to propose diversity tag removals -- how well do you think that will fly ?09:37
TheJuliacdent: sorry, i didnt mean to hit the breaks09:38
persiacdent: random changes is probably more confusing than useful.  An unfiltered firehouse of proposals from all and sundry may provoke better debate.09:38
persiaTheJulia: the implication was unintentional.  I think it would be good if participants were excited.  I think it would be better if that was organic, rather than directed.09:39
TheJuliapersia: i do agree tbay excitement mighr lead there, but the key is to be excited about the same thing.09:41
ttxcdent: On the "optionally breaking existing users" it should definitely be something that is on the table... Although in that specific case i see no reason why the nodelet would not be a natural evolution of nova-compute :)09:41
cdentttx: I'm +many on diversity tag removals and I think many people feel the same way: they are at best not meaningful, and at worst damaging09:42
ttx(taken over by a nodeSIG-like entity)09:42
cdentright "natural evolution of nova-compute" is too slow. that's why I think there needs to be concurrent advancement09:42
cdentpersia: not random changes. random sharing of ideas from which to discover useful change09:43
persiaAh, yes, that makes more sense09:50
cdentIn other, potentially less controversial news, I updated a story on storyboard related to communication notes in the project team guide to add a few more detailed tasks of things to clarify. There were fewer issues than I feared09:51
cdent#link https://storyboard.openstack.org/#!/story/200171009:51
ttxlgtm -- I did a pass on currentness on that guide but missed the weekly cross-project meeting mention09:53
cdentwe've reached the end of the hour and seem fizzled out so...10:01
*** openstack changes topic to "OpenStack Technical Committee office hours: Tuesdays at 09:00 UTC, Wednesdays at 01:00 UTC, and Thursdays at 15:00 UTC | https://governance.openstack.org/tc/ | channel logs http://eavesdrop.openstack.org/irclogs/%23openstack-tc/"10:01
openstackMeeting ended Tue Jul  3 10:01:27 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2018/tc.2018-07-03-09.01.html10:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2018/tc.2018-07-03-09.01.txt10:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2018/tc.2018-07-03-09.01.log.html10:01
*** flwang1 has joined #openstack-tc10:01
flwang1@tc here, greetings, do we have any plan to create a slack workspace and then having channel for each project? cheers10:02
cdentflwang1: there's been discussions about using slack in the past, and the general consensus is that using a non-free solution is not aligned with openstack's principles10:04
flwang1cdent: why LF & CNCF don't have such concern?10:05
flwang1i think if we can have a slack workspace for openstack, which could be very handy for our contributors10:07
flwang1because I think the contributors are overlaping between openstack and k8s10:08
cdentI agree there is definitely some overlap10:09
cdentI don't know why LF and CNCF don't have the same concerns. I personally wish they did.10:10
ttxwe believe in using free tools to build free software10:10
flwang1ttx: fair enough10:11
ttxAlso SlackWe also like to be able to archive messages10:11
ttxwithout paying Slack $160k/year10:12
flwang1ttx: can't we ask for non-profit account?10:12
*** dtantsur|afk is now known as dtantsur10:14
ttxthat would not make it free. Slack does not work so well when you want to allow anybody to sign up10:14
flwang1cdent: ttx: anyway, thanks for answering my question. at least now I know there are some reasons why we don't want to use it, cheers10:15
cdentflwang1: thanks for asking. any you do make a valid point: by not using it we are separating ourselves from the communit of people who do. That's a cost that we need to more consciously manage10:16
ttxAlso Slack is not that awesome... I prefer Zulip. At least it does not encourage information overload10:17
cdentawesomeness of the tech doesn't have that much to do with anything. It's who is there that matters.10:18
cdentThat's somewhat unfortunate but true.10:19
flwang1i prefer slack is not only because it's handy than IRC, but also it can help group the openstack contributor and k8s contributors(a lot of them moved from openstack)10:19
ttxWell, "there" does not apply so well for Slack... since Slack workspaces are completely separated10:19
cdentAnyway, I must attend to some of the internet stuff, will be back later in the day. Good luck and good day to everyone.10:19
* ttx lunches10:20
flwang1thank  you10:20
cdent(that's not quite the "there" I meant, ttx. Rather "who is already using it". App inertia is a big deal.)10:20
* cdent waves10:20
*** cdent has quit IRC10:25
cmurphyif we added slack, with the purpose of attracting the people who overlap with kubernetes, we'd only be fragmenting our own community by splitting into separate synchronous mediums.10:38
persiaIt is not so much the medium as the tooling.  When one has a consolidated client for multiple protocols, there is less cognitive dissonance.  Sadly, consolidated clients are not in vogue this decade.11:30
fungicdent: flwang1: the argument could also be made that lf and cncf choosing to move to slack separated them from others in their broader community who cared about free tools11:34
fungii hesitate to view our choice not to follow them into that abyss as a failing on the part of our community11:36
cmurphyI don't think "hesitate" is a strong enough word here :)11:37
fungicould just as well ask whether lf/cncf should move to irc11:39
fungii'd rather not see us abandon our principles just so that we can gain more contact with other people who abandoned theirs11:40
fungittx: i think the diversity tags factor into the project maturity calculations in the project navigator, don't they? if you haven't already, should we give the foundation webdev team a heads up so they can recalibrate?11:47
cmurphyfungi: we're paired up on keystone for health tracking, I went ahead and chatted with lbragstad and left some notes in https://wiki.openstack.org/wiki/OpenStack_health_tracker#Keystone12:07
fungiTheJulia: in that vein, i confirmed with hogepodge that refstack is indeed holding their irc meeting today (1700z in #openstack-meeting-alt)12:09
ttxfungi: there is no maturity score anymore those days. Only the diverse-affiliation tag shows if reached12:39
fungiahh, thanks for confirming12:41
fungiin that case i can really see why we need to just drop it12:42
EmilienMhello (back for real)12:48
*** mriedem has joined #openstack-tc12:51
*** edmondsw has joined #openstack-tc13:01
*** edmondsw has quit IRC13:06
*** mriedem is now known as mriedem_afk13:09
*** hongbin has joined #openstack-tc13:25
lbragstadcmurphy: thanks13:39
lbragstadfor writing that stuff down13:39
*** mriedem_afk is now known as mriedem13:44
scasi like slack for what it is, but it has extreme drawbacks being a pay-to-play freemium service. the lack of archiving until money is ponied up is the most concerning. there would have to be a majorly altruistic thing by slack for me to feel okay with that being a viable option for openstack in its current state13:48
scasmoving to a free instance would be more detrimental than staying on irc and languishing under the weight of barrier to entry13:49
scasanother community i frequent has their communities' chats on slack. it's fine for emojis and gifs, but the utility of it is largely locked behind credit card barriers. the same questions come up and there's no "just search the logs"13:50
scasunfortunately, there is no good replacement for irc. even irc itself isn't that great in 2018 because its trajectory is being redirected by people behind the scenes13:53
scasincluding this very network on which i emit typing noises13:54
*** openstackgerrit has joined #openstack-tc13:56
openstackgerritThierry Carrez proposed openstack/governance master: Remove team diversity tags  https://review.openstack.org/57987013:56
fungiscas: the infra team has pushed in the past to consider moving to oftc. if you dislike freenode's politics, more voices could help revive that effort13:57
* smcginnis is (happily?) ignorant13:57
scasfungi: it's not freenode's politics i'm concerned about, but their masters' motives13:57
mugsiefor those of us who don't follow the politics of freenode, whats the issue?13:58
scasmaybe it's just me, but when i see an entity taking over a space, it gives me cause for concern13:58
mugsieoh, this is the irc.com thing>13:58
scasmugsie: related, yes13:58
fungii feel like oftc's mission is better aligned with ours, but we ended up on freenode mostly i think because ubuntu was here14:00
scasof course, it's network effect. but that doesn't preclude changing things if the alignment is better. oftc, on-paper, looks like a better fit. hell, even efnet14:01
smcginnisYeah, it looks like oftc has a pretty good philosophy.14:02
*** mriedem has quit IRC14:04
*** mriedem has joined #openstack-tc14:04
*** annabelleB has joined #openstack-tc14:09
*** ianychoi has quit IRC14:18
scasthe non-profit associated with oftc made my beard twitch ever so slightly in a positive manner. usually the beard knows things before i know them14:18
*** ianychoi has joined #openstack-tc14:19
TheJuliaI guess the one thing we should keep in mind is fragmenting communication channels is that they are already fragmented, and that a portion of the larger community can't even reach IRC unless they have a VPN or somehow pay for a service like irccloud...14:22
mugsieTheJulia: is slack the same as IRC for them, or is it allowed?14:29
persiaOften slack is allowed (due to port choices).  There are IRC-on-port-80 solutions, but they cost money for the user, typically.14:29
mugsiepersia: yeah, for corp firewalls that is true14:31
persiaNot just corporate firewalls.  Some interchange gateways have similar port-based limitations.  Remember, the internet extends to places where telecoms are not a private concern.14:32
mugsiesure - but places like that tend to block unmonitored chat services as well14:33
mugsieironically, I can get on IRC from the office, but not slack :)14:33
*** dmsimard has left #openstack-tc14:47
*** edmondsw has joined #openstack-tc14:51
fungiscas: well, network effect and affiliation. we had a lot of ubuntu folk and services involved in the very early days. if we'd been more close with the debian community then oftc would have been a much more natural choice at the time since that's where all their channels are14:53
*** edmondsw has quit IRC14:55
scasi wasn't here in the very early days, essex was where i picked it up. but it makes sense14:56
scasi thought it was odd to sign up for lp, but didn't give much more thought to it14:57
fungibefore git, openstack source code was managed using bzr in launchpad15:03
fungiit moved to using git in a gerrit server managed by members of the community, but bug tracking stayed behind in lp15:07
*** AlanClark has joined #openstack-tc15:09
TheJuliamugsie: afaik, china blocks slack as well15:20
TheJuliamugsie: I'd love a magical solution to provide one place for community to discuss, but I just don't think that it is possible in this current day and age15:22
*** e0ne has quit IRC15:29
*** AlanClark has quit IRC15:40
*** AlanClark has joined #openstack-tc15:41
*** dklyle has joined #openstack-tc15:41
scasthat basically leaves the code review tool as needing to stand in for the communications platform15:46
scasi dislike the notion, but there are few options to avoid fragmenting the channels further15:47
fungiand as far as communications channels go, i can think of worse options when most of what we need to communicate about is developing software16:03
fungithe other communications channel is task tracking/defect reporting16:03
fungiand we _do_ have mailing lists and a q&a site16:06
*** jpich has quit IRC16:06
fungiso while real-time chat may be problematic from some places, we actually have a lot of other asynchronous communications channels16:07
fungitoo many, some might argue ;)16:07
scasthe real-time part is what most people miss or look for, because of that very point. too many asynchronous communications channels, so the feedback loop is harder to close. beyond the bikeshedding aspect irc fostered, "hey, can you review my change?" is an important part. sometimes i need to get your attention sooner than later16:10
scasfor some reason, due to imaginary lines in imaginary sand, not everyone can use the traditionally developed means. in those cases, there almost needs to be an intermediary bridging those parts of the community across various real-time chat methods. feels like work, though.16:14
*** AlanClark has quit IRC16:22
*** AlanClark has joined #openstack-tc16:23
fungiyeah, i agree that having _a_ real-time communications channel sort of acts as the glue which binds the various asynchronous channels together16:23
fungihaving _multiple_ real-time communications channels is likely to fail at that purpose16:24
fungiunless, as you say, they're all just windows opening into each other so communication flows freely between them16:25
*** ricolin has quit IRC16:41
clarkbignoring freeness of tools like slack there are also logistical problems like https://github.com/rauchg/slackin16:52
*** dtantsur is now known as dtantsur|afk17:09
fungii like how the description in their readme says "like freenode" not "like irc"17:16
*** annabelleB has quit IRC17:27
*** annabelleB has joined #openstack-tc17:28
* dhellmann notes that the wiki has stopped emailing him page updates, again17:37
fungidhellmann: for all pages, or just ones you didn't follow the links to while logged in?17:39
dhellmannfungi : the health tracker page in particular. I was receiving updates but did not for the edits ttx and others have made very recently17:39
fungii think mediawiki avoids spamming you on multiple page updates by only notifying you on the first modification to a page since your last authenticated visit17:39
dhellmannthat's unfortunate17:40
dhellmannthat makes it sound like I need to make sure to login every day or something17:40
*** e0ne has joined #openstack-tc17:45
smcginnisIt seemed like I only got notifications on the first edit after I had made an edit.17:50
smcginnisEven if I flagged a page to watch it.17:50
*** dklyle has quit IRC17:53
dhellmanntc-members: we should do something to move the adjutant application ahead. Please take a look and express your opinion so we can tell where we stand: https://review.openstack.org/55364317:57
fungidhellmann: smcginnis: yes, the link basically takes you to a view of all new changes to the page since your last visit17:58
fungion the assumption that you don't want to get 20 notifications if someone makes 20 small edits to a page in a span of an hour17:58
dhellmannfungi : ok. I have missed a few days of edits. It sounds like you're saying I have to login and visit the page to refresh the instructions to send me updates between logins?17:58
fungidhellmann: right, the notification is basically letting you know that you should expect there has been at least one edit since the last time you viewed the page history and/or edited the page17:59
fungiwith the expectation that you then follow the link to look at the full list of edits since your last visit17:59
dhellmannok. but I'm not getting those. at all. I visit the page, someone edits, I don't get email.18:00
fungiit only knows you've viewed the page/history if you're logged in18:00
dimsack dhellmann18:00
dhellmannperhaps my mental model of "since your last visit" does not match its18:00
*** chkumar|ruck has joined #openstack-tc18:01
dhellmannfungi : is there some way to just make it email me all the time?18:02
dhellmannit logs me out so quickly, I would basically have to login and review every page every day it seems18:02
fungii'm not seeing options for that under watchlist or notifications preferences tabs18:11
dhellmannyeah, I have it set to send me every update and have all the little email check boxes checked18:11
dhellmannoh, well18:11
fungialso notifications and watchlist seem to be separate features18:11
*** cdent has joined #openstack-tc18:13
fungiahh, reading https://www.mediawiki.org/wiki/Manual:Watchlist#What_happens_when_a_page_is_edited it looks like it might rely on the notifications implementation though18:14
fungihttps://www.mediawiki.org/wiki/Help:Watchlist#Email_notifications matches my recollection18:16
fungi"After receiving an email notification for a page, you have to visit the page while logged in if you want to be notified of further changes to the same page."18:17
fungithey don't mention any more verbose option to not require an authenticated visit between notifications for the same page18:17
* smcginnis just discovered http://gerrithub.io/18:18
fungithat's been around for years18:18
smcginnisYeah, I'm slow. :)18:18
fungioperated by gerritforge.com18:19
zanebsmcginnis: coincidentally, gerrithub is also really really slow :D18:20
smcginnisLooking at all the junk projects that are registered, I'm not surprised.18:20
zanebRDO used to be on gerrithub until it moved to softwarefactory18:21
fungilooks like gerritforge goes all the way back to 2010, but i can't remember how long ago they started calling it gerrithub18:22
cdentdhellmann: on your report, the tech vision discussion very much rooted on zaneb too18:26
*** edmondsw has joined #openstack-tc18:27
dhellmanncdent : oh! please do follow-up and mention that.18:28
dhellmannsorry, zaneb18:28
dhellmannsomehow I missed that in my notes18:28
zanebcdent: maybe try to use a different turn of phrase ;)18:29
cdentzaneb: I shall watch my phrasing18:29
zanebdhellmann: I don't actually care who gets credit, so no worries :)18:31
*** mriedem has quit IRC18:31
cdentzaneb: I've blamed it all on you18:31
dhellmannzaneb : part of the reason for mentioning names is to show that TC members are actively working on these initiatives, so I want to mention the folks who are doing the work as an acknowledgement18:32
*** edmondsw has quit IRC18:32
zanebcdent: maybe I can offload some blame on jaypipes18:34
*** mriedem has joined #openstack-tc18:39
cdentzaneb: that seems fair18:46
openstackgerritJill Rouleau proposed openstack/governance master: Add ansible-role-tripleo-* roles to governance  https://review.openstack.org/57995218:56
openstackgerritDoug Hellmann proposed openstack/governance master: add check_review_status.py  https://review.openstack.org/57995319:02
fungidims: TheJulia: i've added some initial info for the interop wg and refstack team to https://wiki.openstack.org/wiki/OpenStack_health_tracker19:09
openstackgerritMerged openstack/governance master: Add team fragility analysis script  https://review.openstack.org/57914219:09
TheJuliafungi: awesome19:11
dimsthanks fungi !19:11
fungii caught them in their channel since they ended up not having their meeting today19:12
fungitldr is that interop wg is probably business as usual, refstack is winding down activity for positive reasons19:13
TheJuliasmcginnis: updated watcher on the the wiki based on current information19:21
smcginnisPerfect, thanks TheJulia19:22
* cdent is far behind on many things19:23
jaypipeszaneb: I'm too busy responding to kfox1111.19:26
cdentdood is prolific19:27
cdenthe also seems sane19:27
cdentwhich is nice19:27
* jaypipes declines further comment.19:32
dimshahaha cdent jaypipes19:33
* cdent laughs19:34
*** e0ne has quit IRC19:40
dhellmannfungi : re "refstack is winding down" -- does that mean it isn't needed? or it's "done"? or something else?19:48
fungidhellmann: feature-complete19:48
dhellmannwe don't hear that very often around here :-)19:49
fungiit's nearly at the point where it implements the features its "customer" (the interop program) requested19:49
fungiand they don't foresee asking for it to do more19:49
fungiso it may need bug fixes from time to time, but new features aren't considered in scope19:50
fungihowever the python-tempestconf deliverable may take on a life of its own19:50
fungisince it's useful for a lot of other cases19:50
fungibasically, where you want to perform an autodiscovery to generate a tempest configuration19:51
fungirefstack needed that functionality, but apparently so do other people19:51
dhellmannI can see that for cases where folks want to run tempest outside of refstack19:54
notmynameI'm sure people in here will fine http://ivory.idyll.org/blog/2018-how-open-is-too-open.html interesting20:09
*** edmondsw has joined #openstack-tc20:16
*** edmondsw has quit IRC20:21
cdentthanks notmyname , goo drea20:22
cdentoops: good read20:22
cdentnotmyname: the post following has a good title, will have to read it too20:23
*** annabelleB has quit IRC20:29
*** gcb has joined #openstack-tc20:31
clarkbOne implied hypothesis (and sometimes is presented explicitly) is that open source is a direct cause of burnout. And yet studies seem to show it is an industry problem not a FOSS problem. https://www.bleepingcomputer.com/news/technology/57-percent-of-tech-workers-are-suffering-from-job-burnout/ we can tackle it iwthin FOSS but seems like a bad approach to blame FOSS20:44
cdentclarkb: I suspect that corporate supported open source presents some specific challenges with regard to burn out, as there are multiple and ofen conflicting audiences that a "proud" person will try to satisfy20:45
clarkbcdent: one of the common responses is "I'm not doing open source anymore" which won't fix the problem though20:46
clarkb(this author doesn't present that argument though)20:47
cdentno, not at all20:47
* cdent adds it to the queue20:47
*** annabelleB has joined #openstack-tc20:49
fungithe article resonates with my experiences, though the last paragraph doesn't do much to tie it to the headline. i think the author just wanted a punchy headline20:55
clarkbfungi: if you read the next one it is a setup for we need to change (and here is a proposed framework) because open source causes burnout20:56
clarkband I think the danger with those conclusions is that open source is the problem and that fixing it fixes the problem20:56
* cdent blames (poorly managed) capitalism20:59
fungiyeah, haven't read the second one yet, but i too don't think free software is what's causing software developers to burn out. software is20:59
jaypipesnotmyname: I particularly like the content about "extractive contributors".21:05
fungisometimes less complimentarily referred to as "vampires"21:07
fungior just "leeches"21:07
zanebI was hoping the article would end with solutions, but it didn't really21:08
fungi"Luckily very few people use our software..."21:11
fungialso back to clarkb's point, comments like "the constant need to maintain our open source software" makes it sound like they've never worked on commercial/proprietary software either21:13
fungiall software has bugs, not all software has to be maintained by the same people (or at all) forever, nor do bugs necessarily have to be fixed the moment they're reported. if you're on a research kick and look at bug reports once a month, you're still doing better than the majority of the projects out there probably21:15
notmynamefungi: at the end of that post (the most recent one), I like the change in perspective from "big happy family and all work together" to one more focused on sustainability, including the realities of finances21:18
fungiyep, again no real solutions but sounds like our approaches are fairly similar wrt documenting governance models and trying to work out what messaging to potential contributors/investors should be21:32
fungiin lighter news, google wants to build an "open cloud" https://cloudplatform.googleblog.com/2018/06/why-google-believes-in-open-cloud.html21:34
notmynamecompletely honestly, one of the reasons I like these few posts is because it's examining how people work together, but not in the context of openstack. sometimes I get a bit tired of just hearing our own experiences of community building, so its nice to see other perspectives21:34
fungiyep, i completely agree21:35
*** annabelleB has quit IRC22:01
*** lbragstad is now known as lbragstad_50322:02
*** edmondsw has joined #openstack-tc22:05
scasas distasteful as it is to bring it up, the licensing of the software itself has not been kind to the notion of fostering work out in the open. i can take any of the openstack projects out there, from nova to chef, productize it and 'sell the crap out of it'. all the while not giving back a single line of code. that's great when you've corporations tying team/company goals to supporting a subset, but22:08
scasit does not help when those coffers eventually lumber away because something a little shinier caught their gaze22:08
cdentindeed. I don't get why people are so congratulatory about openstack's licensing.22:09
*** edmondsw has quit IRC22:09
*** mriedem is now known as mriedem_explosio22:14
*** mriedem_explosio is now known as mriedem_burnmark22:14
scasmy gut suggests dollar signs on a grand scale are why the glad-handing is even a thing22:14
dtroyerre licensing: I've seen in a couple of organization Fear of the GPL overrule all logic.  corporate lawyers don't really know how to handle it.22:22
cdentFear of the GPL is my next album22:22
dtroyerquote: "we don't allow using busybox because they sue people"22:22
* cdent goes to bed22:23
dtroyergnight cdent22:23
* cdent waves goodnight22:23
*** cdent has quit IRC22:23
* dtroyer goes to dinner22:23
smcginnisbon apetit dtroyer22:24
*** hongbin has quit IRC22:25
*** dtruong has quit IRC22:30
*** AlanClark has quit IRC22:45
*** mriedem_burnmark has quit IRC23:30
*** edmondsw has joined #openstack-tc23:53
*** edmondsw has quit IRC23:57

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