-
Notifications
You must be signed in to change notification settings - Fork 308
Conversation
af9aeae
to
a900c45
Compare
fe1f3f2
to
e034b3a
Compare
a900c45
to
66441f3
Compare
e034b3a
to
be2d97a
Compare
66441f3
to
ca05a1d
Compare
1a2ad56
to
52b0413
Compare
I'm looking at baselines (#3994 (comment)) here. ~owners can claim takes just like any other ~user. Should we just depend on that instead of implementing the baseline? |
I like that, although maybe it should be set up so that no other takes are available until the owner takes at least one? (Temporal dependency rather than set initial $ dependency) |
52b0413
to
013a505
Compare
Since takes are proportional rather than absolute, there's no need for a temporal consideration; cf. point 2 under benefits. The problem with this is related to what @Changaco identified in terms of volatility in income for participants. Based on the user examples I cited in benefit (3), I think team owners will appreciate the stability of an absolute rather than a proportional baseline. |
This goes for Team Gratipay, even. We need ~$150/wk just to keep the lights on. If income dips down to $120 in a given week, then it should all go to ~Gratipay for operations. No? |
|
That's the best argument for an absolute baseline. |
This frees us up to implement additional logic in mixins rather than running away with the team.py file.
Time to let go.
Fits the new nomenclature
What remains is user-facing in the about pages, etc.
ca05a1d
to
9db9e1a
Compare
9db9e1a
to
064c0f4
Compare
The updated one fails, but the fix needs to happen upstream
f4b9b7b
to
9fec3b6
Compare
on
|
687481b
to
91a9ca1
Compare
Scrapping for parts. #3994 (comment) |
Redo: #4102. |
⬑ #3994
← #4024 — #4026 →
Punchlist
process_takes
process_baselines
beforeprocess_takes
get_ready_payout_routes_by_network
take_over
in plumb takes #4023)master
once plumb membership #4024 lands