feat: propose sponsors level for opencollective and github#496
Conversation
|
@expressjs/express-tc tag to be aware before the next tc meeting |
wesleytodd
left a comment
wesleytodd
left a comment
There was a problem hiding this comment.
Generally in favor of a revamp here, I just don't think we should get so far in the weeds as this proposal goes. In fact I just stopped reading at line 48 because there was a lot of words and it seemed fairly repetitive after I raised my concern about the reward structure.
I would consider breaking this up, and just generally reducing the verbosity used to describe the tiers proposed. Maybe just a single table with the proposed levels and short list of "benefits"?
|
|
||
| ## Summary | ||
|
|
||
| Replace Express's current flat two-tier funding structure (Backer $5/mo, Sponsor $100/mo, both with no described rewards) with an eight-tier ladder — Backer, Supporter, Patron, Bronze, Silver, Gold, Platinum, Diamond — each carrying explicit, escalating recognition rewards (SPONSORS.md → README logo → expressjs.com → docs). Top tiers use limited slot counts to create scarcity, with a single-slot Diamond tier as the apex. The same tier structure is mirrored across the project's funding surfaces (OpenCollective and GitHub Sponsors) so sponsors can fund Express through whichever platform their organization prefers. This RFC complements (and does not modify) [ADR 299: Funding Use Guidelines](../adr/299-funding-guidelines.md), which governs how funds are spent; this RFC addresses how sponsors are recognized. |
There was a problem hiding this comment.
escalating recognition rewards (SPONSORS.md → README logo → expressjs.com → docs)
I think we discussed the logo/sponsors pages and explicitly did not want to do a "pay for play" scheme. We wanted sponsors who just want to support the project because it is valuable to them for it to be secure and stable.
I personally am indifferent on this topic, but I think there is merit in making sure we don't end up with a bunch of sponsors on there just to get the logo/link back. Maybe we can find a tier setup that doesn't include these types of "rewards"?
|
|
||
| ## Motivation | ||
|
|
||
| Express is the most-depended-on web framework in the Node.js ecosystem, with over **100 million weekly downloads** on npm. Despite that footprint, the project's funding surfaces are underdeveloped: |
There was a problem hiding this comment.
| Express is the most-depended-on web framework in the Node.js ecosystem, with over **100 million weekly downloads** on npm. Despite that footprint, the project's funding surfaces are underdeveloped: | |
| Express is the most depended on web framework in the Node.js ecosystem, with over **100 million weekly downloads** on npm. Despite that footprint, the project's funding is almost non-existent: |
|
|
||
| Express is the most-depended-on web framework in the Node.js ecosystem, with over **100 million weekly downloads** on npm. Despite that footprint, the project's funding surfaces are underdeveloped: | ||
|
|
||
| - Only **two recurring tiers** exist: Backer at $5/mo and Sponsor at $100/mo. |
There was a problem hiding this comment.
I would add that there are not many people at either of these tiers. Especially considering if you compared this with other larger or important projects (see below). Considering this is the section justifying work being done on a funding model, I think you should make the argument on why does the project even consider this important before focusing on the small details like this. Maybe just swapping the order of these to put this below? Like:
- we have no sponsors
- compare to other projects
- why we think this is the case
|
|
||
| A **Custom Donation** option (one-time or recurring, any amount) remains available for contributors who do not match a tier. | ||
|
|
||
| ### Reward specifics |
There was a problem hiding this comment.
This is going to be the most contentious part of this proposal. Honestly I would consider making this section more of a brainstorm idea section than a concrete proposal. That way we could discuss and land a less contentious "we want to revamp the OC levels" agreement first, then add on the specifics of the "tier benefits" (a name I would prefer over awards) later.
2 participants
RFC to define the different level of sponsoring we want to have / provide in both OpenCollective but also Github Sponsor