Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

decide what is an official project in the Nix ecosystem #39

Open
fricklerhandwerk opened this issue Jun 30, 2022 · 8 comments
Open

decide what is an official project in the Nix ecosystem #39

fricklerhandwerk opened this issue Jun 30, 2022 · 8 comments

Comments

@fricklerhandwerk
Copy link
Contributor

fricklerhandwerk commented Jun 30, 2022

There is no clear definition of what firmly belongs to the Nix ecosystem, what is "official" or merely "associated", and what is considered third-party.

Tasks

  • decide on criteria
  • define processes for state transitions
  • take inventory
  • update status

Proposal

  1. Mentioned (third party): Code that works and solves a known problem
  2. Endorsed (third party): Significant user base; software is usable and approachable (don't have to read the code to work with it)
  3. Recommended (community project): Large user base; maintained and accepting contributions
  4. Official: Vital to the ecosystem; actively developed by at least two people and with enough resources in the long run; high standards of code quality, collaboration, and documentation
@fricklerhandwerk fricklerhandwerk changed the title decide what is an project in the Nix ecosystem decide what is a project in the Nix ecosystem Jul 4, 2022
@fricklerhandwerk fricklerhandwerk transferred this issue from NixOS/nix-book Jul 28, 2022
@fricklerhandwerk
Copy link
Contributor Author

  • @infinisil at the point where "everyone" relies on it, it should be made official
  • @domenkozar this should be a topic for the board
    • @fricklerhandwerk agree. does the board have the capacity to deal with that and decide in a reasonable amount of time?
      • @domenkozar we have a lot in the backlog, currently focusing on administrative issues such as having and accountant and secretary
        • @fricklerhandwerk great to hear!
        • still need a transparent way to keep track of board work, e.g. project board

@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/2022-07-28-nix-documentation-team-meeting-6/20627/1

@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/2022-08-01-summer-of-nix-documentation-q-a/20695/1

@fricklerhandwerk
Copy link
Contributor Author

@edolstra this is for the board to answer, could you please transfer it to NixOS/nixos-foundation?

@zimbatm zimbatm transferred this issue from NixOS/nix.dev Mar 10, 2023
@olafklingt olafklingt moved this to Stalled in Nix documentation Mar 12, 2023
@fricklerhandwerk fricklerhandwerk changed the title decide what is a project in the Nix ecosystem decide what is an official project in the Nix ecosystem Jul 12, 2023
@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/2023-07-03-nix-team-meeting-minutes-68/30337/1

@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/nixcon-governance-workshop/32705/11

@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/2024-03-07-nix-teams-gathering-meeting-minutes/41208/1

@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/2024-04-11-nix-teams-gathering-meeting-minutes/43228/1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants