Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

Bring back account closing #3601

Merged
merged 15 commits into from
Jul 16, 2015
Merged

Bring back account closing #3601

merged 15 commits into from
Jul 16, 2015

Conversation

chadwhitacre
Copy link
Contributor

Closes #3461.

@chadwhitacre
Copy link
Contributor Author

Alright, so we no longer have bank withdrawals as a disbursement option. Do we try to add PayPal, which would require finding a one-off API, or do we simply remove bank withdrawal and leave it at that?

@chadwhitacre
Copy link
Contributor Author

I think we just remove bank withdrawal for now. We don't have a lot of time.

@chadwhitacre
Copy link
Contributor Author

The "final gift" disbursement strategy doesn't really make sense anymore since we're moving away from indefinite escrow (#1383). Once we start charging in arrears (#3378), and not holding funds to cover next week's payments (#3475), then the only reason to have money in escrow will be pending or failed payouts.

@chadwhitacre
Copy link
Contributor Author

And that means we no longer have disbursement strategies as part of account closing.

@chadwhitacre
Copy link
Contributor Author

I mean, unless we wanted to try to implement async PayPal payouts at some point. I don't think we need to care about that though, because we now require a payout route in order to receive money, and we're moving to a system in which the only way to have escrow is if your payout route has failed. I guess we should just make sure there are no pending payouts during account closing, since a pending payout could fail, and then what?

@chadwhitacre
Copy link
Contributor Author

Anyway, ripping out disbursement strategies entirely ...

@chadwhitacre
Copy link
Contributor Author

Alright, what's next? I guess we need to clear subscriptions instead of tips. And what about team ownership now?

Users no longer receive money directly, it all goes through teams first.
@chadwhitacre
Copy link
Contributor Author

We have a couple options with teams: either we automatically close teams when the owner closes their account, or we make the owner go through a separate "close team" workflow first. We certainly want a "close team" workflow anyway. Do we want to make team owners jump through that hoop or otherwise confirm somehow that closing their account will close their team(s)? Probably.

@chadwhitacre
Copy link
Contributor Author

Do we release team slugs/names immediately upon team closing?

@chadwhitacre
Copy link
Contributor Author

Ooooh, that's right ... we don't have any team membership, only owners. :-(

@chadwhitacre chadwhitacre mentioned this pull request Jul 6, 2015
5 tasks
@chadwhitacre
Copy link
Contributor Author

Ready for review, @rohitpaulk @rorepo et al.

@chadwhitacre
Copy link
Contributor Author

Gonna go ahead and self-merge, as this has been out for 10 days and we need to start landing some 2.0 cleanup so we can stay on track for August 20.

chadwhitacre added a commit that referenced this pull request Jul 16, 2015
@chadwhitacre chadwhitacre merged commit d09d976 into master Jul 16, 2015
@chadwhitacre chadwhitacre deleted the bring-back-closing branch July 16, 2015 15:28
@mattbk
Copy link
Contributor

mattbk commented Jul 16, 2015

General question, is it supposed to work live on the site once you merge? Or is there another step? I'm not hip on how git works.

@rohitpaulk
Copy link
Contributor

@mattbk - There is a deploy step after the merge. All deploys are logged in https://botbot.me/freenode/gratipay/, you could compare the timestamps to see if a merged PR has actually been deployed :)

@mattbk
Copy link
Contributor

mattbk commented Jul 16, 2015

Thanks!

On July 16, 2015 12:42:02 PM CDT, Paul Kuruvilla notifications@github.com wrote:

@mattbk - There is a deploy step after the merge. All deploys are
logged in https://botbot.me/freenode/gratipay/, you could compare the
timestamps to see if a merged PR has actually been deployed :)


Reply to this email directly or view it on GitHub:
#3601 (comment)

Sent from a phone that, although intelligent, is not street smart.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants