Conversation
| The most common form of individual contribution to the Flux project is | ||
| time and effort. Thus, the project recognises people who reported | ||
| issues, fixed bugs, wrote documentation, reviewed pull requests, and | ||
| so on, by thanking them on the Flux website. |
There was a problem hiding this comment.
| so on, by thanking them on the Flux website. | |
| so on, by thanking them [on the Flux website](https://fluxcd.io/#:~:text=Made%20possible%20by%20our%20contributors). |
There was a problem hiding this comment.
These are contributors, not sponsors. Sponsors would e.g. have a dedicated page or other place where they would be highlighted.
Ah, misread. I think we should either add a ref to the section or just refer to "the contributor section on the homepage of the Flux website".
There was a problem hiding this comment.
👍 Yeah I could be more precise here
There was a problem hiding this comment.
Do we need to specify this in the doc?
I would suggest adding a sponsored by section on the homepage of fluxcd.io, We already have an adopters section now, featuring adopters logos. I think it's fair to add a similar section for sponsors too. Also probably easy since we have the code for adopters. Note that helm.sh has sponsor logos on the home page too.
| as an organisation, and we would like to be generous in expressing | ||
| gratitude to anyone that helps. | ||
|
|
||
| Here are other kinds of contribution that could be recognized: |
There was a problem hiding this comment.
This document should include details on the ways we will recognize such contributions. A dedicated section on the website near the individual contributors' avatar gallery is one option. A dedicated page is another one.
There was a problem hiding this comment.
See #321 (comment)
But again, I suggest we don't need to specify the exact details of this in this doc. This would allow us to merge as-is, whereas now this PR has been open since last year. We can always give more specifics if we really feel we need to spell it out here.
| sponsors' money will be put to the benefit of the project. | ||
|
|
||
| There is an initial exchange in which the program organisers and the | ||
| Flux maintainers agree what benefits are being provided and how |
There was a problem hiding this comment.
I wonder whether we need or should weave this into the GOVERNANCE.md document so that sponsorship is more tied into the overall governance of the project and doesn't live a life in isolation from everything else.
The least this document should do is make clear what it means by "Flux maintainers". I suppose this should mean core maintainers.
There was a problem hiding this comment.
@makkes do you agree we should include all Flux maintainers - automated from the source of truth here - not only core (fluxcd/flux2)?
|
@squaremo I'd love to help getting this merged asap. There's only 2 comments open that sound like they're pretty quickly addressed. wdyt? |
These are for two related purposes: 1. recognise help from people and orgs (mainly orgs) that isn't time and effort; like, free CI accounts 2. make room for sponsorships, which opens up another way for people and orgs (mainly orgs) to help the Flux project I expect these will need a few iterations. I just wanted to get them in view. Signed-off-by: Michael Bridgen <mikeb@squaremobius.net>
Co-authored-by: Hidde Beydals <hiddeco@users.noreply.github.com> Signed-off-by: Michael Bridgen <mikeb@squaremobius.net>
kingdonb
force-pushed
the
recognition-and-sponsorship
branch
from
1858baa to
bc4ae5e
Compare
5 participants
These are for two related purposes:
recognise help from people and orgs (mainly orgs) that isn't time and effort; like, free CI accounts
make room for sponsorships, which opens up another way for people and orgs (mainly orgs) to help the Flux project
I expect these will need a few iterations. I just wanted to get them in view.
Also see the discussion in fluxcd/flux2#4335 -- comment where you are most comfortable :-)