NixOS / NixOS/foundation

Define sponsorship tiers

Open
#78 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
141
Forks
17
PR merge metrics
No merged PRs in 30d

Description

Sponsorship needs exposure.

Since there is limited space for directing attention towards supporters of the Nix ecosystem, it seems worthwhile to define sponsorship tiers (or levels). One example is how the Haskell Foundation does it.

Proposal

(Drafted together with @mightyiam and @imincik).

Idea: Instead of listing all supporters indiscriminately, show the most impactful ones in tiers. Instead of determining a particular range for each tier, categorise by support volume.

Show the top supporters most prominently in a way that is discoverable for observers of the NixOS Foundation's activities.
A support tier is valid for a year.

Community tier

Top 4-8

As in community tier, but show medium size logo, also

  • in reports by the NixOS Foundation (we don't have them yet, but probably should)
  • in acknowledgements in public appearances (e.g. conferences) by board members

Top 3

As in Top 4-8, but with large size logo.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the acknowledgements page on nixos.org/donate.html and the Haskell Foundation donations example linked in the issue. The proposal covers tier visibility, support-volume categorisation, annual validity, and placements in reports or public appearances, but names no repository files or tests. Done would require an agreed sponsorship-tier design and an implementation plan.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.