Skip to content

Instantly share code, notes, and snippets.

@Danack

Danack/words.md Secret

Last active March 5, 2024 10:34
Show Gist options
  • Save Danack/f99f417a43fc8258babc26704b28f72f to your computer and use it in GitHub Desktop.
Save Danack/f99f417a43fc8258babc26704b28f72f to your computer and use it in GitHub Desktop.
Appropriate sponsor levels.

Apropos of everything; I have strong feelings about how sponsorship levels are described.

Too many maintainers are asking for people to 'buy a coffee' or 'show you're a fan'.

This is folksy nonsense that suggests that individuals are those who should be sponsoring open source.

Companies are the entities that profit from open source, they are the ones who should be funding it. Phrasing it more 'professionally' avoids putting pressure on individuals, and can lead to larger sponsorship arriving.

The sponsor levels I have are:

$1 a month - This tier is appropriate if you are a solo developer.

$5 a month - This tier is appropriate if you are a solo developer, but can spend more than $1 a month.

$10 a month - This tier is appropriate if your company is tiny (<5 employees).

$50 a month - This tier is appropriate if your company is small (<10 employees).

$100 a month - This tier is appropriate if your company is medium (<50 employees). Priority will be given to your bug reports and issues.

$250 a month - At this tier, priority will be given to your bug reports and issues.

$500 a month - At this tier, high priority will be given to your bug reports and issues.

$1,000 a month - This tier is appropriate if your company is large or you are a hosting company. At this tier, priority will be given to your bug reports and issues. You will also be able to suggest what work items should be worked on.

$2,000 a month - At this tier, priority will be given to your bug reports and issues. You will also be able to suggest what work items should be worked on. If you wish, you can also have a monthly call to discuss the roadmap of work items to be focused on.

$6,000 a month - At this tier, priority will be given to your bug reports and issues. You will also be able to suggest what work items should be worked on. If you wish, you can also have a monthly call to discuss the roadmap of work items to be focused on, and priority will be given to items you think should be worked on.

I realise that I'm in a lucky position as the main lib I look after is unforkable (due to PHP pecl being one of the worst distribution methods), but having >$1000 sponsor tiers should be done by all projects.

@merlox
Copy link

merlox commented Feb 14, 2023

This is wonderful I love how you managed to equate money to actual value to big companies. How has it worked out for you?

@Danack
Copy link
Author

Danack commented Feb 14, 2023

@merlox good, but only because the main library I maintain is distributed through PHP/PECL which is completely terrible.....and it means that forking the library is difficult. When PHP 8 was released, I refused to release a version of Imagick that supported PHP 8, until I had a decent amount of funding. A few companies (Automattic, dreamhost and wpengine) stepped up with non-trivial amounts of funding.

Of course many individual developers were dicks, Imagick/imagick#358, as is usual when they don't get what they want.

@utybo
Copy link

utybo commented Feb 14, 2023

Random thought that popped in my mind while reading: this is somewhat similar to VB-Audio's approach (which, mind you, is proprietary donationware, not OSS). For reference, this is how they put it:

image

website

(this is obviously not 1-to-1 compatible with open-source projects as the license would "override" the resell parts)

Thanks for your post! Really interesting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment