forked from Fediversity/meta
29 lines
1.4 KiB
Markdown
29 lines
1.4 KiB
Markdown
---
|
|
title: NixOps Initial location
|
|
attendees: [ Robert, Koen, Théophane ]
|
|
---
|
|
|
|
How/where do we develop NixOps4?
|
|
- Initial idea was to just develop it in the `NixOS/nixops` repository
|
|
- Community members generally against that
|
|
- The previous iterations of NixOps didn't hold their promises
|
|
- Now NixOps still appears like the way-to-go for NixOS deployments, while it's generally not a good solution. → Bad impression of the Nix project as a whole
|
|
- Fear that a new version will not be successful either, and just increase the problem.
|
|
|
|
- Possible solutions:
|
|
- Give the project another name to reduce the confusion
|
|
- Probably won't help that much
|
|
- Use [nix-community](https://github.com/nix-community/) as an incubator
|
|
- This is what the organisation is made for
|
|
- Wouldn't bring nearly as much visibility as the `NixOS` org though, while still adding constraints to the development
|
|
- Develop it internally and then donate it to the community?
|
|
- Can make a big bang once we announce it, will give leverage to move it to the NixOS org
|
|
- Most likely solution
|
|
- Roberth would still like to have it on GitHub for convenience for contributors
|
|
|
|
- Decision:
|
|
- Work in a dedicated `NixOps4` GitHub org
|
|
- Mirror the repository (with metadata?) to <https://git.fediversity.eu>
|
|
- Make the project LGPL to conform with the original NixOps licence
|
|
|