You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The intended effect of these is to open up and encourage ways for organisations to materially help the project.
The first really just expands the understanding of contribution -- it's more generous, and with no particular downside, to be conspicuously grateful to e.g., organisations for granting their employees time to work on Flux, and for donations of free service accounts and cloud platform credits, and so on.
The second sets out some ground rules for sponsorships. These are more difficult to account for because it's not a direct relationship: a sponsor gives a sponsorship program money, and they use that money to do .. something, probably employ people .. for the benefit of the project. The guide leans on assuming good faith; but aside from that, we don't have the time or resources to conduct audits, and anyway fraud is not really anticipated. Being generous with thanks and being fair are more important than being bulletproof.
For transparency: running a sponsorship program is something Weaveworks would like to do, and this motivates my proposal. I have been careful to make the guidelines non-exclusive and fair in principle. It's possible only Weaveworks ever tries running such a program, but it's also possible there's more than one. As it was (initially) with the Flux ecosystem page, this situation of maybe having many entries eventually, but only one to show now, can be tricky territory.
I think let's keep discussion here on the principles (why and how), and comments in the PRs about the specific wording, spelling mistakes, etc..
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've posted a PR in fluxcd/community which adds a couple of files with guidance on
The intended effect of these is to open up and encourage ways for organisations to materially help the project.
The first really just expands the understanding of contribution -- it's more generous, and with no particular downside, to be conspicuously grateful to e.g., organisations for granting their employees time to work on Flux, and for donations of free service accounts and cloud platform credits, and so on.
The second sets out some ground rules for sponsorships. These are more difficult to account for because it's not a direct relationship: a sponsor gives a sponsorship program money, and they use that money to do .. something, probably employ people .. for the benefit of the project. The guide leans on assuming good faith; but aside from that, we don't have the time or resources to conduct audits, and anyway fraud is not really anticipated. Being generous with thanks and being fair are more important than being bulletproof.
For transparency: running a sponsorship program is something Weaveworks would like to do, and this motivates my proposal. I have been careful to make the guidelines non-exclusive and fair in principle. It's possible only Weaveworks ever tries running such a program, but it's also possible there's more than one. As it was (initially) with the Flux ecosystem page, this situation of maybe having many entries eventually, but only one to show now, can be tricky territory.
I think let's keep discussion here on the principles (why and how), and comments in the PRs about the specific wording, spelling mistakes, etc..
Beta Was this translation helpful? Give feedback.
All reactions