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
{{ message }}
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.
If Teams had a withdrawal route attached to them, that should dampen the confusion of having to create a ~user account in order to create a Team account: ~Gratipay is the owner of Gratipay, but ~whit537 (and possibly others) ought to be the manager.
On the other hand, Teams are surely going to want to give on Gratipay as well. Options:
They create a ~user account that is separate from the Team, and use that just for giving. It's not connected to the Team within Gratipay.
We enable Teams to give directly. This brings us back within sight of the old implementation of Teams as a particular kind of participant: they can do everything normal ~users can do, plus distribute payroll.
If we go for (2), then think about what a ~user can do that a Team can't: make voluntary payments to Teams, and take payroll from a Team. At some point we need to enable Teams of Teams, to enable growth beyond the Dunbar circle. Teams taking payroll from other Teams could address that.
Reticketing from #3399 (comment).
If Teams had a withdrawal route attached to them, that should dampen the confusion of having to create a ~user account in order to create a Team account: ~Gratipay is the owner of Gratipay, but ~whit537 (and possibly others) ought to be the manager.
On the other hand, Teams are surely going to want to give on Gratipay as well. Options:
participant
: they can do everything normal ~users can do, plus distribute payroll.If we go for (2), then think about what a ~user can do that a Team can't: make voluntary payments to Teams, and take payroll from a Team. At some point we need to enable Teams of Teams, to enable growth beyond the Dunbar circle. Teams taking payroll from other Teams could address that.
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: