Main proposal moved to https://github.com/nix-rfc-org/rfcs/blob/nix-rfc-org/rfcs/0000-open-org.md - Nixpkgs - Repo: github/nixos/nixpkgs - Wiki - Repo: NixOS/wiki - DNS entry: wiki.nixos.org - Owner: @Lassulus, ... Open brainstorm call next week #################################### ########## Scratch space ########### #################################### People already interested in this effort: - @danielsidhion: willing to help out - @tomberek: willing to help out - @fricklerhandwerk: positive feedback People to discuss with - @ronef - @zimbatm - @edolstra - @grahamc Past instances of pushback against something like this? - How detailed does this repo need to be? - Could be more nested, e.g. for Nixpkgs, there could be resources `lib`, `pkgs` and `nixos`. - Necessary for each "project", not necessarily root resources (e.g. github.com/NixOS/nixpkgs is its own project, even though the github.com/NixOS owners have higher permissions) - Or maybe the github.com/NixOS owners should be the people deciding over the vision of the technical project? kind of like an org chart Generate GitHub repo descriptions with owners, like nix-community. Instead of framing it as imposing additional constraints, frame it as enabling people to do more things Frame it as a service for an overview, vision to manage permissions in a uniform way? @fricklerhandwerk's concrete steps: - Write down the overview of everything (somewhere) - RFC (or any sort of broadly public discussion) for this to become official - Ensure that reality matches the description *now* - May require the repo owner to have org owner permissions (to set repo permissions, groups, etc.) - Or have a single person that delegates changing ownership to others - ...this is to be decided in an agreeable manner - With the first PR to hand out new permissions, questions of policy naturally arise and need to be resolved - "New team, shouldn't they have meeting notes?" - @tomberek: Would expected the board to do that, but it's not - @infinisil: Could ask the board to be that team instead - @infinisil: Fund somebody? - Valentin: The RFC could decide how to solve that, but needs to be considered - @infinisil: RFCSC has worked so far, seems comparable work-load - @tomberek: RFCSC doesn't have as high of a stake. Org changes would involve conflicts among people - @infinisil: Realistic/Needed?