2026/05/31

Newest at the top

2026-05-31 23:18:54 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2026-05-31 23:13:38 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-05-31 23:13:35 +0000 <davean> janus: it has nothing to do with employees
2026-05-31 23:02:43 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2026-05-31 23:02:21 +0000marinelli(~weechat@gateway/tor-sasl/marinelli) marinelli
2026-05-31 23:01:55 +0000marinelli(~weechat@gateway/tor-sasl/marinelli) (Remote host closed the connection)
2026-05-31 22:55:35 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-05-31 22:53:31 +0000tusko(~uwu@user/tusko) tusko
2026-05-31 22:48:48 +0000marinelli(~weechat@gateway/tor-sasl/marinelli) marinelli
2026-05-31 22:48:21 +0000marinelli(~weechat@gateway/tor-sasl/marinelli) (Remote host closed the connection)
2026-05-31 22:48:21 +0000tusko_(~uwu@user/tusko) (Remote host closed the connection)
2026-05-31 22:44:42 +0000merijn(~merijn@62.45.136.136) (Ping timeout: 252 seconds)
2026-05-31 22:40:03 +0000merijn(~merijn@62.45.136.136) merijn
2026-05-31 22:38:35 +0000 <janus> sorry, that is a bit inexact, the rules are in the document, but the point stands that it could pass even if José becomes unavailable
2026-05-31 22:37:46 +0000 <janus> it only needs a 2/3 ratio to pass, so even if José stays on and doesn't reply, it could still get passed
2026-05-31 22:35:37 +0000 <janus> davean: so why does the HF restructuring have to influence the TWG?
2026-05-31 22:35:20 +0000 <janus> davean: but José is the only HF employee on the TWG according to https://github.com/haskellfoundation/tech-proposals/blob/main/proposals/PROPOSALS.md and the employee list on https://haskell.foundation/who-we-are/
2026-05-31 22:31:11 +0000 <davean> I ahve OH SO MANY comments on that proposal but not the will or spoons to write it all up as one coherent thing for people to actually discuss
2026-05-31 22:30:47 +0000Pozyomka(~pyon@user/pyon) pyon
2026-05-31 22:30:39 +0000 <davean> Well thats not the process thats currently happening I think. I know a bunch of people on the TWG are aware of it, but HF is being restructured
2026-05-31 22:29:11 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds)
2026-05-31 22:24:18 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-05-31 22:24:17 +0000 <janus> davean: ^^
2026-05-31 22:23:46 +0000 <janus> It would be a shame if the deadline approaches and then somebody says they didn't have time to review it
2026-05-31 22:23:21 +0000 <janus> tritlo: do you think the TWG is aware of the hackage rewrite proposal? I just noticed that there is a three month deadline on getting it reviewed by the TWG
2026-05-31 22:23:01 +0000__monty__(~toonn@user/toonn) (Quit: leaving)
2026-05-31 22:18:46 +0000target_i(~target_i@user/target-i/x-6023099) (Quit: leaving)
2026-05-31 22:13:38 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds)
2026-05-31 22:09:56 +0000skum(~skum@user/skum) skum
2026-05-31 22:08:31 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-05-31 22:06:18 +0000Square2(~Square@user/square) Square
2026-05-31 21:57:31 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2026-05-31 21:53:39 +0000Pozyomka(~pyon@user/pyon) (Quit: brb)
2026-05-31 21:52:59 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-05-31 21:51:50 +0000tristanC(~tristanC@user/tristanc) tristanC
2026-05-31 21:51:50 +0000tristanC(~tristanC@97-113-129-157.tukw.qwest.net) (Changing host)
2026-05-31 21:51:50 +0000tristanC(~tristanC@97-113-129-157.tukw.qwest.net)
2026-05-31 21:42:16 +0000vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2026-05-31 21:41:59 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds)
2026-05-31 21:37:28 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-05-31 21:34:12 +0000weary-traveler(~user@user/user363627) user363627
2026-05-31 21:26:03 +0000merijn(~merijn@62.45.136.136) (Ping timeout: 252 seconds)
2026-05-31 21:21:56 +0000vanishingideal(~vanishing@user/vanishingideal) (Ping timeout: 266 seconds)
2026-05-31 21:19:25 +0000merijn(~merijn@62.45.136.136) merijn
2026-05-31 21:16:49 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2026-05-31 21:11:38 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-05-31 21:07:26 +0000synchromesh(~john@2406:5a00:247e:1500:6c73:518b:be6f:ed81) synchromesh
2026-05-31 21:07:21 +0000tristanC(~tristanC@user/tristanc) (Ping timeout: 248 seconds)
2026-05-31 21:06:22 +0000bitdex(~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 252 seconds)
2026-05-31 21:06:10 +0000synchromesh(~john@2406:5a00:247e:1500:9a0:33e6:ebb2:ef41) (Read error: Connection reset by peer)