-
Notifications
You must be signed in to change notification settings - Fork 308
Add "percentage to charity" like Humble Bundle has #4209
Comments
It wasn't me. The closest I can think of is when I suggested something like a giving pool, where you could give to a general pool that could be opted into by a team/project. Somewhat different than a curated bundle, this would essentially be TWYW but at the project level. |
This is now potentially evolving into a tax(!): gratipay/inside.gratipay.com#637 (comment). |
@mattbk I should have commented in your original issue, and maybe the following has been mentioned already. IMO TWYW is based on mutual respect and understanding. It might be feasible in a small circle like our own team, but I imagine it would cause more conflicts than harmony among different and maybe sometimes completing projects.
Are we considering switching our model? If there's a explict tax, will it decrease the direct giving to Gratipay? |
I'm against a tax that isn't opt-in. Could we reward people for opting in with something? Social capital? |
Yeah, I'm not sure a "tax" makes sense since this is optional giving in the first place, and that's kinda the whole point. :-) |
So how do you give to charity on here? In fact, isn't there a support ticket like this? Is there a way for charitable organizations to create teams? Or for teams to partner with charitable organizations? |
This organizations need official status, so we need to import list from somewhere. https://www.charitynavigator.org/ looks like a good start. |
|
I thought @mattbk or someone talked about this before, but I'm not finding it by searching for "charity" in this repo. Gittipay 1.0 really took off when we combined charitable giving to diversity activists with more pragmatic giving to open source projects. Can we do the same under Gratipay 2.0, adapted to our new project focus?
One implementation possibility is the Humble Bundle model, where charitable giving is tacked on as a percentage of the total bill. Diversity-focused charities are still probably a good place to start, since that is a pressing concern in the tech industry.
The text was updated successfully, but these errors were encountered: