Add NixCon sponsorship tiers and process #95
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -43,3 +43,74 @@ Organisers are using: | |
| If the organisers cannot reach consensus on important decisions, | ||
| they are escalated to the Steering Committee. | ||
| Decisions relating to sponsorships are always escalated to the Steering Committee. | ||
|
|
||
| ## Sponsorship tiers | ||
|
|
||
| This should be displayed on the website. | ||
|
|
||
| ### Non-sponsorship donation (0+ EUR) | ||
| - Supporting the conference and official Nix projects | ||
| - Confirmation of donation via OpenCollective | ||
|
|
||
| ### Bronze (1024+ EUR): | ||
| - Linked logo on the website | ||
| - Linked shout-out or repost from official social media accounts | ||
| - Possibility to distribute your own stickers/swag/merch at the venue | ||
| - Tickets: 1+ corporate tickets[^1] | ||
|
|
||
| [^1]: One corporate ticket per 1024 EUR. Only corporate tickets come with company name/logo recognition on the badge. Corporate tickets can also be bought individually when ticket sales open. | ||
|
|
||
| ### Silver (2048+ EUR) | ||
| - Everything from Bronze | ||
| - Shout-out in the opening | ||
| - Slot on break slideshow (provide a slide in advance) | ||
| - Possibility to distribute flyers (provide them in advance) to all attendees in bag | ||
| - Tickets: 2+ corporate tickets[^1] | ||
|
|
||
| ### Gold (4096+ EUR): | ||
| - Everything from Silver | ||
| - 5 minute lightning talk slot | ||
| - Dedicated space for a booth[^2] | ||
| - Tickets: 4+ corporate tickets[^1] | ||
|
|
||
| [^2]: These perks may be limited in availability. | ||
|
|
||
| ### Diamond (8192+ EUR): | ||
| - Everything from Gold | ||
| - Logo on some official conference swag[^2][^3] | ||
| - 1 minute presentation slot (provide the slides in advance) in the conference opening | ||
| - Intro of all recordings show your name/logo | ||
| - Possibility to distribute items (provide them in advance) to all attendees in bag | ||
| - Tickets: 8+ corporate tickets[^1] | ||
|
|
||
| [^3]: These perks require production and cannot be guaranteed if too late. | ||
|
|
||
| ### General info | ||
| - Sponsors can be tier-limited or rejected by the Nix Steering Committee for any reason. | ||
| - The outline of all sponsor content must be disclosed in advance. We reserve the right to reject content. | ||
| - Visibility priority is given according to tiers and donation amount. | ||
| - The sponsor can selectively abstain from perks. | ||
| - Surplus funds will be used to support official Nix projects. | ||
| - Reach out if you'd like to sponsor in a more custom way, such as food, drinks, services, equipment, or only specific perks. | ||
|
|
||
| ### How to sponsor | ||
|
|
||
| Send an email to [email protected] (which will forward to both the Nix Steering Committee and the NixOS Foundation board) with: | ||
|
There was a problem hiding this comment. Would it make sense to use There was a problem hiding this comment. Could be done, both domains are official, but I wouldn't know how that's configured, and we already have a working process for There was a problem hiding this comment. (An aside: maybe now that NixCon is officially official, we can start using There was a problem hiding this comment. The NixCon domain is managed by CloudFlare. We use Cloudflare's email forwarding to forward |
||
| - Company name and website | ||
| - Desired tier, amount and perks | ||
| - Any other details | ||
|
|
||
| ## Sponsorship process | ||
|
|
||
| The following is internal documentation and should not go on the website. For 2025 it involves the following respondents: | ||
| - Board respondent: @ra33it0 (deputy: @infinisil) | ||
| - SC respondent: @tomberek (deputy: @winterqt) | ||
|
|
||
| 1. After receiving the email, board respondent replies that the email was received and that they will hear back within about 2 weeks. | ||
| 2. SC respondent ensures the SC internally rejects or provisionally approves the sponsor within 1 week. | ||
| - If rejected, SC respondent replies to the sponsor with the rejection message. | ||
| 3. If provisionally approved by the SC, SC respondent forwards the name and website of the sponsor to the NixCon orga Matrix room for organiser approval. | ||
| 4. Within 1 week, the SC respondent checks whether organisers are okay with the sponsor, and if not, ensures that the SC internally reevaluates final rejection or approval of the sponsor. | ||
|
There was a problem hiding this comment. What does the second part mean? There was a problem hiding this comment. if organizers are not OK, SC has to reevaluate and either accept that veto or ignore it (although ignoring it would be not good :)) There was a problem hiding this comment. In other words: The organisers have a chance to give input to the SC before a sponsor is approved. It's still the SC's final call, which can depend on how strong the disagreement is among organisers. There was a problem hiding this comment. |
||
| - If rejected, SC respondent replies to the sponsor with the rejection message. | ||
| 5. If accepted, SC informs the board respondent and the organisers in the NixCon orga Matrix room of the sponsor being accepted. | ||
| 6. Board respondent sends follow-up instructions to the sponsor and tracks the status of payment and perk delivery. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Lassulus Note that we also have this line here, though this is meant for companies that can provide benefits directly instead of funding.
Iirc the reason for not having tiers specifically for e.g. meals was that it's tricky to figure out the right balance between amount and perks. With standard tiers, the entire amount will be available for the organisers to make the best use of. But for a sponsored meal in comparison, most of the amount will need to be spent on the food itself (~10k for a fancy one), removing some of the organisers freedom to choose the best use of the funds. As a consequence, for the same amount as the standard tiers, perks should be reduced, or for the same perks as standard tiers, the amount should be increased.
That said, I think we could make it work and I would be in favor of a good proposal, but for now would like to defer this to not delay sponsoring further. There's nothing stopping us from proposing more tiers later on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I'm fine with going forward with the current proposal, but as soon as we have some prices for the actual food we should amend the sponsorship tiers to include some kind of food sponsorship, display that more prominently and try to get that covered first?