Monday, 2021-05-24

*** timburke has joined #openstack-tc01:26
*** gmann_afk is now known as gmann01:30
*** timburke has quit IRC02:31
*** jamesmcarthur has quit IRC03:52
*** jamesmcarthur has joined #openstack-tc03:53
*** jamesmcarthur has quit IRC03:58
*** timburke has joined #openstack-tc04:18
*** jamesmcarthur has joined #openstack-tc04:23
*** jamesmcarthur has quit IRC04:40
*** jamesmcarthur has joined #openstack-tc04:53
*** freefood_ has quit IRC04:56
*** jamesmcarthur has quit IRC04:57
*** freefood_ has joined #openstack-tc04:57
*** jamesmcarthur has joined #openstack-tc05:10
*** jamesmcarthur has quit IRC05:15
*** jamesmcarthur has joined #openstack-tc05:27
*** ralonsoh has joined #openstack-tc05:28
*** jamesmcarthur has quit IRC05:33
*** timburke has quit IRC05:35
*** jamesmcarthur has joined #openstack-tc05:47
*** e0ne has joined #openstack-tc05:55
*** jamesmcarthur has quit IRC05:59
*** e0ne has quit IRC06:04
*** jamesmcarthur has joined #openstack-tc06:13
*** jamesmcarthur has quit IRC06:19
*** slaweq has joined #openstack-tc06:33
*** tosky has joined #openstack-tc07:20
*** andrewbonney has joined #openstack-tc07:31
*** jamesmcarthur has joined #openstack-tc07:32
*** slaweq has quit IRC07:32
*** slaweq has joined #openstack-tc07:35
*** jamesmcarthur has quit IRC07:36
*** vishalmanchanda has joined #openstack-tc07:42
*** pojadhav|rover is now known as pojadhav|lunch09:07
*** jamesmcarthur has joined #openstack-tc09:34
*** jamesmcarthur has quit IRC09:45
*** pojadhav|lunch is now known as pojadhav|rover09:49
*** lpetrut has joined #openstack-tc10:43
*** e0ne has joined #openstack-tc10:57
*** jamesmcarthur has joined #openstack-tc11:41
*** e0ne has quit IRC11:45
*** jamesmcarthur has quit IRC11:46
*** e0ne has joined #openstack-tc12:08
*** jamesmcarthur has joined #openstack-tc12:11
*** jamesmcarthur has quit IRC12:15
*** jamesmcarthur has joined #openstack-tc12:15
*** thiago__ has quit IRC12:32
*** tdasilva_ has joined #openstack-tc12:32
*** e0ne has quit IRC12:57
*** akahat|ruck is now known as akahat13:00
*** pojadhav|rover is now known as pojadhav13:12
gmanno/14:22
yoctozeptoo/14:22
yoctozeptoso, how are we approaching the move? I believe we've seen enough of the drama14:41
*** e0ne has joined #openstack-tc14:42
fungithe opendev sysadmins have asked for feedback from openstack's leadership on whether we should enact our long-standing evacuation plan to start connecting our service bots to oftc instead of freenode14:48
*** lpetrut has quit IRC14:50
*** dklyle has joined #openstack-tc14:51
yoctozeptofungi: yup, that's also why I brought it up on this channel right on Monday ;-)14:53
yoctozeptoon that note14:54
yoctozeptoI think I am subscribed to all mls you posted that message14:54
yoctozeptowere there any direct replies to you?14:54
yoctozeptoI saw only some movement on zuul14:54
yoctozeptoiirc14:54
gmannI thought we decided to hold it for now and monitor the situation more ?14:54
fungithere was a reply on the kata-dev ml14:59
yoctozeptoah, that means I am missing that one subscription15:05
yoctozeptochecking it out15:05
yoctozeptogmann: yeah, but it only seems to be getting worse; should we wait till it starts to get ugly directly in the openstack garden?15:05
gmannanything change from last week?15:12
yoctozeptogmann: yeah, for example this funny story: https://www.devever.net/~hl/freenode_abuse ;-)15:13
yoctozeptoand this stuff: https://github.com/freenode/web-7.0/pull/513/commits/2037126831a84c57f978268f090fc663cf43ed7a#diff-0e382b024f696a3b7a0ff3bce24ae3166cc6f383d059c7cc61e0a3ccdeed522c15:14
yoctozeptoTheJulia wrote about it on the ml15:14
yoctozeptoI'm just sharing further15:14
TheJuliaI didn't want to paste them in irc, because at this point I have zero trust for freenode15:14
yoctozeptoyeah, I feel you15:15
TheJuliaAnd the way the policy is worded now, basically every channel in our community could be taken over15:15
TheJuliaas-is *without* us moving.15:15
yoctozeptoyeah, and I believe our redirect topics idea is at a loss now ;p15:16
TheJuliaThe policy seems written to hold projects hostage over recognition of the channel names.15:16
TheJuliaAt least, that is my take, others may interpret it differently15:17
TheJuliaErasing the very last line of the policy also makes my blood boil as I'm sure it does for every trans and non-binary community member that we have.15:18
yoctozeptoyup, I scratched my head hard as I don't see a point in taking down this particular one except when one is either very naive or wants to actually serve some invectives lol15:19
yoctozeptoI mean, the folk is pretty inclined to dominate the irc world15:20
clarkbits an odd change for them because the rest of the document continues to indicate they are a UK entity that follows UK laws. UK laws ban all manner of hate speech. Feels like this is their way of saying we'll overlook violations even if still technically against our rules due to technical reasons15:20
yoctozeptobut that does not align with letting people be offensive15:20
dansmiththe rest of the section below the fold seems to provide plenty of coverage for that stuff, IMHO15:22
dansmithI dunno why they re-wrote that section specifically, but if you haven't already made up your mind about it, you could assume that it's because of all the libera spam and hassling people to move,15:23
dansmithclaiming channels have already moved, which haven't, etc15:23
yoctozeptowell, seemingly on libera spambots claim that channels are still on freenode even if they moved15:25
yoctozeptoso it's one big joke15:25
dansmithright, spamming both ways it seems15:25
gmannyeah https://github.com/freenode/web-7.0/blob/main/content/pages/policies.md#off-topic-use15:25
yoctozeptoyeah, good catch; so presumably that was just a part of cleanup not to repeat oneself15:27
yoctozeptostill, it does not really make me feel better about new freenode ;p15:27
dansmithto me, this indicates continuity of maintainership at least.. last week several people claimed that freenode was now completely without staff to maintain anything, which this seems to contraindicate :)15:28
yoctozeptoyup, that is true15:28
yoctozeptothe new staff is definitely there15:28
yoctozeptoI wonder if it's new staff that attacks libera15:29
yoctozeptoI would really vote on some third parties loving chaos15:29
yoctozeptoas the situation is quite ridiculous15:29
TheJuliayoctozepto: ++15:30
*** e0ne has quit IRC15:30
JayFI mean, one network (libera) has a DoS attack on staff just through more usage. The other (freenode) just lost the majority of it's experienced staff. If that's not catnip for IRC trolls, IDK what is.15:31
TheJuliaI kind of feel like it is entirely just too much drama. Look at all the wasted thoughts and energy. The angst of the unknown driving us. We shouldn't continue to expose ourselves to such a situation.15:31
TheJuliaJayF: Add in bad blood between parties, and it may go on for a very long time.15:32
JayFRight now; OpenStack is creating its own drama by not being decisive about making an urgent move :|15:32
TheJuliaJayF: absolutely agree.15:32
TheJuliaI was hoping ironic would basically have enough of a quorum this morning for us to discuss alternative platforms that maybe were not IRC.15:32
TheJuliabut alas, holidays.15:32
dansmithchoosing to wait for drama to settle down is ... creating drama? :)15:33
JayFThe lack of making a decision is forcing15:33
JayF** OpenStack contributors to continue to participate in a network they no longer trust.15:33
JayFI don't care about freenode/libera drama if I can just not connect to freenode anymore because I am not required to for work.15:34
TheJuliaJayF: ++15:34
TheJuliaIf the community leadership chooses not to make a whole project decision, then individual projects will make their own decisions.15:35
JayFI have already said, personally (and I mean it) that this is the last week I'm going to be connected to Freenode.15:35
TheJuliaJayF: Are you on efnet, oftc, or gimpnet by chance?15:36
JayFno, yes, yes15:36
TheJulia\o/15:36
dansmithTheJulia: if the community leadership decides to stay, will you accept that? or does it only work if we make the decision you want? Honest question...15:36
* TheJulia now knows where to find JayF after this week.15:36
clarkbisn't efnet already worse than freenode?15:36
fungiand let's not even mention undernet ;)15:37
*** tdasilva_ has quit IRC15:37
TheJuliadansmith: at this point, it would come down to a project team vote. And I have a very strong feeling the project team is for departing freenode.15:37
*** thiago__ has joined #openstack-tc15:37
JayFdansmith: I'm gone regardless of community decision. Part of why I push to participate in, and make time to, contribute to OpenStack upstream is because I think it's doing a good thing for the world. Being connected on Freenode, now, is counter to those values.15:37
dansmithTheJulia: so with people pulling towards different networks and different technologies, fracture is pretty much inevitable then yeah?15:37
dansmithJayF: good to know, thanks15:37
gmann community leadership is not saying we will use freenode forever, its 'let's wait to take any final decision at least during this dramatic time which has both side of it'15:38
JayFI think fracture is the default choice for as long as a choice isn't made.15:38
TheJuliadansmith: possibly. Only more certain each day the TC does not reach a consensus. The bottom line also is many are connected to multiple networks. Example JayF, and I. Maybe because we're just old IRC users who have been on some of these networks for ages.15:39
dansmiththe consensus thus far has been to wait and see.. Unless you want us to commit to something without sufficient data, I'm not really sure how else we can do anything other than make a decision to leave just for the purposes of signaling15:40
dansmithand I think it's clear that has a large cost15:40
gmannyes15:40
TheJuliadansmith: I'd prefer we remove ourselves from the toxic situation so we don't become toxic.15:41
yoctozeptoI see it like this: the freenode cesspit has overflown (again) and it's the right time to skip the drama and go OFTC as we are mostly prepared for and dreamed of doing before15:42
JayFEvery day I use freenode since it's been stolen; I am contributing to the toxicity. That's not tenable. And I'm not the only contributor who feels that way, obviously. Maybe one of the only ones free enough to be able to leave freenode even if Ironic doesn't :(15:42
yoctozeptowhat are we *really* waiting for?15:43
TheJuliayoctozepto: maybe not dreamed. I at least didn't hope for change, but sometimes change is necessary.15:43
TheJuliayoctozepto: TC to reach consensus, which I'm convinced at this point won't happen.15:43
JayFThe TC won't even take up the agenda item on their own unless someone else wants to argue it at the next meeting.15:43
yoctozeptoTheJulia: with "we" I really meant the TC so it was implicit ;d15:43
TheJuliawhich means, this is an academic argument at best, and the community will fracture.15:43
TheJuliayoctozepto: fair :)15:44
yoctozeptomaybe let's rephrase the question15:45
yoctozeptodoes anyone disagree OpenStack would be better off on OFTC?15:45
dansmithit's not the being here or there that is the primary concern, it's the move15:46
TheJuliadansmith: how so?15:46
yoctozeptobut we know how to move15:46
dansmithso if you rephrase the question as "if we had started on OFTC in 2010, would that have been better" then .. that's legit :)15:46
yoctozeptofungi is almost ready to press the button15:46
TheJuliayoctozepto: I think the policy changes complicate things.15:46
toskydansmith: when you see "the consensus", is it the consensus of the TC? Because I think the community disagrees15:46
JayFI've had nobody surface a list of things we have to do to move, or ask for help, or publish any concerns beyond "how many non-active contributors will wake up tomorrow in an empty IRC channel"15:46
clarkbJayF: fungi has posted about it15:46
dansmithtosky: yes, I meant the TC, and15:47
JayFclarkb: ah, I've been following the maillist and haven't seen anything like that come across. I don't have time to read scrolback in all openstack channels :|15:47
dansmithtosky: unless there are a ton of people so angry that they can't even reply to the ML thread, I think you're overstating the vast consensus about moving15:47
gmannthere are lot more work in term of advertising and each project contributors guides or so15:47
*** thiago__ is now known as tdasilva15:47
clarkbJayF: its on all the mailinglists15:47
yoctozeptoTheJulia: what policy changes do you mean?15:47
TheJuliatosky: of course, the TC is also supposed to represent their community. But at the same time they don't know if the community members don't make their voices heard.15:47
clarkbJayF: not on IRC15:47
toskydansmith: then there is not even consensus about staying either15:47
toskydansmith: do we want to run a condercet vote?15:48
toskythat's how debian would solve it15:48
tosky(or non-solve it)15:48
dansmithtosky: documented, definitely not, it's just the default :)15:48
clarkbJayF: http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022654.html from openstack-discuss which poinst to the main thread on service-discuss@lists.opendev.org15:48
dansmithtosky: sure, we could, and set some minimum bar for participation so we know it's a reasonable sample15:49
yoctozeptoah, this is the time when I wish IRC supported threads because I got lost in who answers whom15:49
toskyabout that, I understand there are other stakeholders in the community, but that also mean I should subscribe to another list just to discuss this topic15:49
TheJuliayoctozepto: the freenode policy changes linked earlier15:49
gmannbtw how many projects are strongly disagree with TC's current decision15:49
JayFclarkb: interesting, the linked thread doesn't any any specific todos or asks for help. That's what I was looking for. Folks saying moving is hard there are some of us who care enough to try and help fix it :)15:49
clarkbJayF: yes it links to a thread that does becauwe we're trying to keep all the discuss on one thread15:49
JayFI mean even the service-discuss thread is anemic15:49
clarkband i can't type this early in the morning15:50
JayFunless I'm missing something?15:50
yoctozeptoTheJulia: ah, yes, I mentioned that already; but we can advertise that externally and reach out to people here best-effort15:50
toskyI just hope this is not the last big FLOSS community which is going to decide15:50
yoctozeptoTheJulia: I bet irc lurkers read our mailing lists15:50
TheJuliayoctozepto: some do :) Some don't. Some of us will continue to straddle for a little while until we can fully disconnect15:50
toskyKDE is discussing and it's blocked on the (at the moment) missing matrix bridge on libera, but I kind feel what the outcome will be15:51
clarkbJayF: I disagree. It says we believe oftc to be a better option (have for years, but also sidesteps all the current drama), we have parked our channels there to erserve names, we need to update bots to switch and people may lose their nicks15:51
yoctozeptoTheJulia: yeah, I will squat (oh no, I am against the new policies!) around for a bit as well15:51
clarkbJayF: and it specifically asks for your feedback if you feel that is insufficient that would be a great place to voice that concern15:51
yoctozeptoare we worried that there is no "move champion" perhaps?15:52
TheJuliagmann: I can tell you every active leader in the ironic community has been voicing a desire to depart freenode given the whole situation. The fact we all seem to agree on something is freaky in itself as we almost *never* agree with that level of uniformity.15:52
JayFclarkb: I'm honestly confused right now. I was trying to find a place where I could technically contribute, if needed, to help prepare for a potential move. Did I miss something in those emails that enumerated any of that?15:52
yoctozeptowe on kolla also receive negative feedback from the community about us staying on freenode15:52
yoctozeptothough I believe it's not the most representative sample as we target sysops which would prefer to use something other than irc in the first place15:53
gmannack, I am adding Ironic, Kola in that list.15:53
clarkbJayF: yes, 4th paragraph details the issues with moving and 5th says "this will entail a bit of development effort in order to accommodate the differences mentioned above."15:53
yoctozeptobut ignore I even mentioned that non-irc, just don't start the matrix discussions, let's do that later...15:53
gmannalso adding it in weekly meeting agenda to -check the current decision of 'let's wait'15:54
clarkbJayF: if you are interested in helping with that work certainly responding to the thread indicating that would be appropriate?15:54
yoctozeptogmann: did you start any etherpad?15:54
JayFI don't generally participate on service-discuss, and don't want to commit to some unknown set of work :)15:54
gmannyoctozepto: composing.15:55
yoctozeptoJayF: can you commit to planning what is needed?15:55
yoctozeptogmann: ack; we could use it to plan the move as it's 99% we are going to do it15:55
JayFyoctozepto: bluntly, most of my time spent on openstack is beg/borrow/stolen from specific other priorities, so I am not OK to committing to unknown quantities/quality of work15:55
gmannyoctozepto: that ways, we can get the each projects wise feedback also if community think TC is not making right decision for them and accordingly we can discuss in TC further15:57
TheJuliaI suspect or perhaps fear that it is viewed as change a config file, open other window and done by some. Yet by others it involves everything down to doc changes, communication plans, emails, outreach, etc.15:57
dansmithwe could also just decide that projects that really don't want to be on freenode are free to go to OFTC where we've reserved the channels15:57
dansmithI assume that we can straddle both networks, once the OFTC-having work is done to the bots or whatever15:58
gmanndansmith: yeah15:58
clarkbI think opendev is trying to avoid needing to support multiple networks15:58
clarkba decision along those lines may involve opendev only supporting one of those networks. fungi has probably thought about this more than I thave though15:58
TheJuliadansmith: we've always been "free to go", the point is we don't want to fracture the community which is why you've got non-tc members in here calling for change.15:59
gmannclarkb: but if projects (infra) openstack or kata have different preference then ?15:59
dansmithclarkb: yeah, so we could also say "and you may not have infra support if you do but at least the channel is registered"15:59
dansmithTheJulia: I understand that15:59
clarkbya I expect it will be along those lines. basically you get the bots and help over in $location. If you go elsewhere here are some things to consider like registration16:00
*** tdasilva_ has joined #openstack-tc16:00
gmannthat is we have for some cases also like we have few projects wechat channel or so16:00
* clarkb needs to pop out now16:00
gmannalong with infra supported IRC16:00
TheJuliagmann: but there is only so much that can be done in those cases, and that is already some fragmentation I guess.16:01
gmannyeah, i am saying 'non infra supported tooling ' are already being used so it would not be very new things16:02
TheJuliaahh yeah16:02
*** tdasilva has quit IRC16:03
gmannlet me compose the etherpad for more projects feedback and we will be happy to change the TC decision ('let's wait') if that is what community want.16:04
TheJuliaThat sounds like a plan.16:06
fungitosky: debian already "solved it" by moving from freenode to oftc in 2006, yeah https://www.debian.org/News/2006/2006060416:10
fungiJayF: i expect the service-discuss thread is "anemic" for now because i only started it on friday, and the projects we've asked to get feedback from are trying to determine what feedback to provide (cf thread on zuul-discuss ml, ongoing openstack tc discussion in here and threads on openstack-discuss, et cetera)16:15
fungialso that thread is specifically about moving the irc bots managed as part of the opendev collaboratory, and our desire to connect them to whichever network seems to wind up with the majority of our communities on it16:16
JayFfungi: I was mainly just looking for the answer to the question "is there something more constructive than chatting in IRC that I could do to help a move happen?"16:16
JayFI think the answer is no?16:16
toskyfungi: yeah, but my comment was about the general way of solving problems in debian (by GRs)16:17
fungiJayF: sure, there absolutely is, for example we need to work out how to rejigger https://opendev.org/openstack/project-config/src/branch/master/tools/check_irc_access.py and https://opendev.org/opendev/system-config/src/branch/master/docker/accessbot/accessbot.py so that they work with oftc, but i'm struggling to wrap my head around the irc module's state machine16:20
JayFack; I'll take a look at it if I get a chance. Feel free to ping me if you want a review if you get there first :D16:20
fungii didn't want to get into the technical weeds in that thread, but am happy to discuss an exact to do list for readying our services (the others are likely pretty much ready to go)16:20
fungitosky: actually there was no gr to decide the debian project's move to oftc: https://www.debian.org/vote/16:24
toskyfungi: I know, but generally complex issues are handled through GRs16:25
fungiit has less to do with complexity and more to do with contention, but yeah i understand what you're trying to say16:25
*** jamesmcarthur has quit IRC16:29
*** jamesmcarthur has joined #openstack-tc16:42
fungifollowing discussion on #python-dev, it seems freebsd also hasn't decided what to do yet: https://wiki.freebsd.org/IRC/16:47
*** andrewbonney has quit IRC17:05
dansmiththe majority of the projects in that list that have already moved have gone to libera, which I think seems to have the least support from TC members as a target, at least according to my gut17:18
yoctozeptofungi: but they registered on libera already17:22
*** ralonsoh has quit IRC17:23
fungiyoctozepto: sure, much like opendev has registered channels on oftc already17:23
yoctozeptofungi: ack, I thought you were wondering whether it's more likely they choose libera or oftc ;d17:24
fungino, i meant just what i said, freebsd hasn't decided what to do yet17:25
yoctozeptoyeah, they did not17:27
*** timburke has joined #openstack-tc17:37
clarkbfungi: I too can take a look at the access stuff if you point me at what is causing you trouble17:49
clarkbfungi: off the top of my head the first thing may be to make sasl optional in our bots ( I think we force it on now?))17:50
fungiclarkb: it's just generally the service bots and flags being different, and me having to stumble through the state machine. i'm most of the way to having check_irc_access.py working now17:54
fungibut have a ton of debug code to clean back out17:54
clarkbfungi: ok, ping me if I can help (reviews or debugging etc)17:55
fungii should have something up for that first script a little later today17:55
fungibut we can discuss in #opendev17:56
*** jamesmcarthur_ has joined #openstack-tc19:40
*** jamesmcarthur has quit IRC19:43
*** vishalmanchanda has quit IRC19:59
*** slaweq has quit IRC20:14
*** jamesmcarthur_ has quit IRC20:28
*** jamesmcarthur has joined #openstack-tc20:48
*** openstackgerrit has quit IRC22:05
JayFIn case it hasn't been posted here, https://github.com/freenode/web-7.0/pull/513/files freenode updated their AUP recently to allow non-project members to take over former/moved project channels, and removed the language that banned hate speech on the network. Material changes are happening :|22:21
fungiit was included in a recent post on one of the relevant openstack-discuss ml threads, yeah, and got talked about some in here around 15:14 utc today22:31
*** jamesmcarthur has quit IRC22:48
*** tosky has quit IRC23:18
gmannyeah that is what we discussed in morning. off-topics are not removed but added with extra line/reworded. if you scroll down, you can see the text added below comments23:22
*** openstack has joined #openstack-tc23:50
*** ChanServ sets mode: +o openstack23:50
*** jamesmcarthur has joined #openstack-tc23:57

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!