15:57:57 #startmeeting tor anti-censorship meeting 15:57:57 Meeting started Thu Jun 29 15:57:57 2023 UTC. The chair is meskio. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:57:57 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:58:09 hello all!! 15:58:11 here is our meeting pad: https://pad.riseup.net/p/tor-anti-censorship-keep 15:58:13 feel free to add what you've been working on and put items on the agenda 15:58:19 hihi! 15:58:28 I'll give some minutes so people can update the pad 15:59:10 hi~ Hi~ 16:02:02 hi 16:04:04 I think we can start 16:04:13 first an announcement: 16:04:30 after last weeks discussion rdsys is ignoring the running flag now (is already deployed) 16:04:42 so people can host bridges without a public ORPort 16:04:59 yeah! 16:05:27 at some point we should think on updating documentation and our docker images, but I would wait a bit to see how it goes as people experiments with it 16:05:34 nice :) 16:05:54 the first discussion point is on me: 16:06:02 do we want to activate renovate bot in snowflake? 16:06:09 What is the short messaging? Is it just "Add `ORPort 127.0.0.1:auto` and `AssumeReachable 1`"? 16:06:34 ohh, I didn't know about 'auto', nice 16:06:38 yes, that should work 16:07:35 I think activate renovate bot should be fine, I don't have any reason against it 16:08:16 renovate bot will automatically open merge requests every time there are new versions of used libraries in snowflake 16:08:27 we are already using it in rdsys and conjure happily 16:08:37 (some times it does open a bunch of merge requests, but is not too bad) 16:08:51 I can take care of enable it, I just wanted a confirmation that we are happy with that 16:10:08 great, I'll go ahead with that 16:10:55 another bot I'm wondering if we want to enable is the support for stalled issues in the triage bot 16:10:56 yes... 16:11:05 thise are the rules that TPA is using: 16:11:14 https://gitlab.torproject.org/tpo/tpa/triage-ops/-/blob/main/common/02-stale.yaml 16:11:42 basically pokes you if you don't update an issue in 14 days and the issue is in 'next', 'doing', 'wneeds review' or 'needs information' 16:12:12 and moves issues that are in needs information to icebox 14 days after that if they still don't get updates 16:12:25 will something like that help us? or be too noisy? 16:12:43 can be configured per repo if we want 16:13:06 that was my question. Might it be more appropriate for some repos rather than others? 16:13:29 I'm not sure 16:14:04 I (or gaba) get once in while around poking people in issues that are staying for too long in those categories, so I wanted to automatize that 16:14:16 could we trial it for a bit and then reassess? 16:14:25 sure 16:14:40 yes, we might have a lot of issues stalled 16:14:57 and if it generate too much issue, we can disable it later 16:15:20 It might be fine if stalled issues are automatically marked as such and moved to the icebox though. 16:15:37 It seems like this would be helpful, but may initially increase stress XD 16:16:03 ok, let's try it out, I can enable it for a first run just for snowflake and rdsys that are the projects with more movement and we'll see how it goes 16:16:33 yes, let's try it 16:16:39 good 16:16:44 anything more about bots? 16:17:01 EOF 16:17:18 let's move on then 16:17:29 conjure call for testers 16:17:32 ggus: is that you? 16:18:03 yes 16:18:30 so, 28 days later, can we wrap up/close the call for testers? 16:18:42 or do we want something else from our community? 16:18:48 i think we're good for now 16:19:01 we got a lot of good feedback and some testers found bugs we didn't find before 16:19:15 oh that's great :D 16:19:21 we have some work to do now on reliability and testing from our vantage points 16:19:45 yeah... testing from vantage points... 16:20:29 I will try to place it in my pipeline... 16:21:20 cool! i'll update the forum tomorrow :) 16:21:31 nice 16:21:35 thanks! 16:21:44 thanks ggus! 16:22:19 anything more on that? 16:22:58 not from me 16:23:09 all good 16:23:17 in two weeks many of us will be at PETS, I think we should cancel this meeting that week 16:23:22 I mean July 13th 16:23:36 yes, I agree 16:23:51 and the week after many of us will also be AFK, so maybe we want to cancel two weeks here 16:25:15 ok, I write it down also in the announcements, so we remember next week to remind it 16:25:28 there will be meeting next week as usual 16:26:00 sgtm 16:26:19 webtunnel soft release update 16:26:21 ggus: ??? 16:26:57 not from me, but I would like to comment I have already send to email to tor-relay mailing list 16:27:10 not from me, but I would like to comment I have already send the email to tor-relay mailing list 16:27:18 :) 16:27:23 if you didn't saw it, that is because it is in moderation queue 16:27:29 yes, very soon the user support team will start asking some folks to test the webtunnel 16:27:31 (it got delivered) 16:27:43 yeah! 16:27:58 nice 16:28:00 i'll get the feedback collected in a confidential ticket 16:28:07 (thanks arma2) 16:28:29 and thank ggus for helping me with improving the email 16:28:57 maybe i'll have some feedback for the next week ac-team meeting, but probably i'll have it for the end of month 16:29:17 thanks for presentation and for attedning the meetup, shelikhoo and meskio ! 16:29:29 ^~^ 16:29:40 no problem 16:29:48 sounds great 16:30:59 then we can start thinking to create a public call for users to test, like we did for conjure 16:32:34 yes 16:32:49 anything more on this topic? 16:32:54 EOF 16:33:06 all good! 16:33:37 there is no more points in the agenda 16:33:57 any last topics? 16:34:54 nothing from me 16:35:22 good, then let's grap it up 16:35:30 i wish you all a good PETS! :) 16:35:35 #endmeeting