!djTaTBQyWEPRQxrPTb:nixos.org

Nixpkgs Architecture Team

233 Members
https://github.com/nixpkgs-architecture, weekly public meetings on Wednesday 15:00-16:00 UTC at https://meet.jit.si/nixpkgs-architecture52 Servers

Load older messages


SenderMessageTime
29 May 2023
@infinisil:matrix.orginfinisil piegames: Thanks a lot! I'm watching the thread :) 16:33:07
@piegames:matrix.org@piegames:matrix.orgGood :) Feel free to add your own experiences to this16:33:32
@piegames:matrix.org@piegames:matrix.org While writing it a lot of the raised questions have been kind of resolved, but at this point I don't want answers, I want them answered by the RFC process itself. 16:35:21
@raitobezarius:matrix.orgraitobezarius
In reply to @infinisil:matrix.org
How do you mean that?

I believe the change will be inevitably controversial because we do not have the technical means to enforce this in the repository and I imagine that RFC can be just about "formalizing something".

Nevertheless, I think the core idea is very useful to bring forward certain subjects on security, committers, etc, though, so that's what I mean as interesting dynamics, whatever happens out of it, I can only think / hope it will be good.

17:27:01
30 May 2023
@infinisil:matrix.orginfinisil @room: The next meeting will take place in ~30 minutes, if you have anything extra you'd like to discuss, please add a section to the meeting notes - meeting link - live stream 14:01:09
@infinisil:matrix.orginfinisil tomberek: John Ericson: Ping 14:35:14
@zmejblaze:matrix.orgzmejblaze joined the room.21:13:29
31 May 2023
@linus:schreibt.jetzt@linus:schreibt.jetzt
In reply to @infinisil:matrix.org
Linux Hackerman: As part of the steering committee, can you announce FCP on Discourse?
sorry I didn't get around to this before the meeting, had some issues with my laptop dying... anyway, we'll look at getting the category opened up so that anyone can post announcements there, we think it makes more sense for the shepherd team to do it than us given our meeting cadence and the shepherd team's greater familiarity with the content
13:21:12
@infinisil:matrix.orginfinisilhttps://discourse.nixos.org/t/rfc-0140-fcp-simple-package-paths/28589 🚀14:31:12
1 Jun 2023
@niknetniko:matrix.org@niknetniko:matrix.org joined the room.12:45:56
@niknetniko:matrix.org@niknetniko:matrix.org left the room.12:46:22
@raphi:tapesoftware.netraphi changed their display name from raphi to raphi (element unread channel fix when).13:03:33
2 Jun 2023
@ckie:ckie.devmei 🌒& changed their display name from ckie (they/them; limited keyboard usage, voice preferred) to ckie (they/them).22:20:35
3 Jun 2023
@syphoxy:matrix.org@syphoxy:matrix.org joined the room.16:37:29
4 Jun 2023
@p01arst0rm:pixie.town@p01arst0rm:pixie.town left the room.12:23:59
@federicodschonborn:matrix.org@federicodschonborn:matrix.org changed their profile picture.17:40:33
5 Jun 2023
@pajarove:matrix.orgpajarove joined the room.21:45:17
6 Jun 2023
@infinisil:matrix.orginfinisil Robert Hensing (roberth): Could you lead the NAT meeting on 27 June? I'll be on vacation then 14:17:58
@roberthensing:matrix.orgRobert Hensing (roberth) infinisil sgtm 👍 15:02:27
@infinisil:matrix.orginfinisil Robert Hensing (roberth): Thanks! https://github.com/nixpkgs-architecture/.github/blob/master/hosting.md should explain everything. Can you go through the one-time setup there? 15:34:39
9 Jun 2023
@piegames:matrix.org@piegames:matrix.orgSo, what do we do with RFC 140?16:17:04
@piegames:matrix.org@piegames:matrix.org Also infinisil if you want to update the alternatives section with the new ideas and arguments that came up during FCP (mainly that discussion thread with QuantenZitrone), now would be a good time 16:18:19
@infinisil:matrix.orginfinisil piegames: Yeah I'll do it this evening 16:19:10
@infinisil:matrix.orginfinisil

piegames: So, the rfc process doesn't state who decides over whether the FCP needs to be cancelled:

In most cases, the FCP period is quiet, and the RFC is either merged or closed. However, sometimes substantial new arguments or ideas are raised, the FCP is canceled, and the RFC goes back into development mode.

17:11:45
@hexa:lossy.networkhexaI would expect the shepherd team to acknowledge that17:12:21
@infinisil:matrix.orginfinisilI think it should definitely be the shepherd team, as the steering committee shouldn't be involved in deciding RFCs17:12:24
@hexa:lossy.networkhexaalso probably not a good time to mention the issue of how badly legacyPackages was named?17:14:11
@hexa:lossy.networkhexanaming things is bloody hard 😄 17:14:38
@infinisil:matrix.orginfinisil hexa: Is this rhetorical? Because that was just mentioned! See https://github.com/NixOS/rfcs/pull/140#issuecomment-1584882324 17:15:01
@hexa:lossy.networkhexauh, yes, it was rhetorical17:15:18

Show newer messages


Back to Room ListRoom Version: 9