-
Notifications
You must be signed in to change notification settings - Fork 308
Let teams decide for themselves how money is split. #1660
Comments
I'm not sure how this is a helpful observation, because any algorithm for splitting team money within Gittip is going to encode an ideology (more or less), and is going to be complicated (more or less). We tried one method ("everyone votes on everyone else") and then we moved to the current method ("kids eat first").
The obvious workaround is to simply not handle team splits within Gittip. Withdraw the money to a bank account and distribute it from there however you like.
This would address your ideological concern, though not your complication concern. :-) We've got a 0, 1, infinity problem here. Right now we're at 1. Going to infinity is a lot of work, and does it add sufficient value over the available workaround? |
I should add that with the writeable tips.json API, another workaround would be to update the project's giving based on whatever algorithm the project would like (cf. how Khan does it). This approaches ideas that surfaced somewhere on #449 (iirc), though transparency might be an issue. |
Allowing the team owner or manager to set a weekly payout for each team member seems like a pretty good way to deal with whatever system anyone comes up with. They can implement a spreadsheet, or just type the numbers in manually. You can already redirect some of your own funds. Just make that process optionally more transparent, and make it more obvious who's part of a team. I tried to address the ideology thing here. |
I think in the future we should put more effort into making gittip into a platform so that the infinity of the solutions is made by someone else. Writable tips api is a first (partial) step in that direction. We should try to design the rest so that the money stays within gittip (thus recommend sending it off and split elsewhere as a last resort). |
👍 to all @traverseda points. I've noticed that this is only a one star issue. This issue should be given more stars as teams are likely to become the key differentiator between Gittip and other funding platforms. Also @whit537 :+1 the throttling algorithm is a real pain especially for new teams. I can see myself having to constantly remind my team members to increase their takes every week to ensure that they get up to the desired level. Self managed take it is also easier to implement than than algorithmic approaches as I see it as a primarily as a user interface change. On the team page we could have a section called Pay Out Method for now this could be check box with (for now) two options
If [Self Managed] is selected, then only the team account owner can set the the take of members. The Team account owner enters the relative take (the percentage) for each team member. |
👍 |
|
I had to remind each team member to up their take when we started with $1. I didn't mind that too much... that it took 6 weeks to get to $64 per week... Letting each person take less is cool. Not everyone in the team needs as much as the next. But right now, we want to evenly distribute the money, and I had to ping several people several times to reduce to $32 from $64. Some people were on vacation (which is cools). ! So... I dont need to control how much each person takes... but I would like, as an admin of our group to set a max each person takes. |
A "evenly distribute" would work too. (as long as each person could still set their own max. So people are not forced to take more money than they want. But they also would not need reminders to keep it even as the amount per week changes up or down.) |
+1 @elliottw at #3480 (comment):
|
Closing in light of our decision to shut down Gratipay. Thank you all for a great run, and I'm sorry it didn't work out! 😞 💃 |
Right now you've got a lot of very ideological and complicated code in how teams get paid out.
That's simply not practical for a lot of projects.
I'd suggest having a bunch of different methods for managing team payments, including what you have now and completely central management by the team owner.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: