Closed chadwhitacre closed 8 years ago
???—We just got through the Balanced Shutdown. Need to take stock and regroup.
Open | Closed | Queue | Description |
---|---|---|---|
0 | 23 | Violations | private communication amongst the safety team |
12 | 14 | Security | private communication with security researchers |
5 | 25 | Legal | private communication with our counsel |
10 | 906 | Support | private communication with users |
4 | 108 | L2 Support | escalated support issues |
20 | 69 | Team Review | public review of applications for new teams |
? | ? | Errors | production errors |
17 | 1,735 | Vendors, etc. | private communication with our vendors (also includes low-volume mailboxes: safety and security) |
20 | 116 | Pivot | a milestone |
14 | 54 | Balanced Shutdown | a milestone |
6 | 10 | Milestones | all milestones |
6 | 525 | PR Review | work in the final stage before deployment |
21 | 1,678 | PRs | all work in progress |
773 | 4,514 | Issues | public communication with contributors |
Deployment is hosed. Immediate concerns for me today are:
Deploy issue: https://github.com/gratipay/gratipay.com/issues/3821.
Deployment back on track. I've looked at https://github.com/gratipay/gratipay.com/pull/3810. We still need to refund advances on Braintree (we just did Balanced), which'll take some work. I going to take the rest of the day off (holiday here, kids are home). I'm off tomorrow, so I'll plan to pick up with Braintree refunds on Wednesday and then look at a blog post.
A well deserved break !m @whit537
Thanks, @kaguillera. Happy birthday! :-)
:birthday:
Alright! Caught up on local queues—Inbox 2, GitHub 0, Vendors 0, L2 Support 0!
Also getting pumped for Speak Freely: https://github.com/gratipay/inside.gratipay.com/issues/334. @kzisme Here's the event to promote: https://twitter.com/SpkPgh/status/652403773843841024.
Let's see about refunding advances on Braintree ... https://github.com/gratipay/gratipay.com/pull/3810.
Oh! Also ... I ran into @elliottw over the weekend, and we talked about me working from Catapult one day a week, starting maybe next week.
Posted once about the event! I'll post again tomorrow as well! Exciting!
Happy birthday @kaguillera!
@whit537 Co-working spaces seem awesome!
What is "refunding advances"? I guess I'm confused as to where we are regarding https://medium.com/gratipay-blog/140-000-97d54e6d40ed and escrow and everything...
What is "refunding advances"?
@mattbk We had two main sources of escrow:
On https://github.com/gratipay/gratipay.com/pull/3810 I've been refunding the escrow due to (2). Early returns are that our success rate with refunds on Balanced was only about 15-20%, which means that even if we had gotten around to (1) before Balanced turned off their refund API last Friday, there was no way we were going to be able to zero out our escrow.
I guess I'm confused as to where we are regarding https://medium.com/gratipay-blog/140-000-97d54e6d40ed and escrow and everything...
Once I land https://github.com/gratipay/gratipay.com/pull/3810 I'm planning to write a follow-up blog post to that one.
The short story is that we didn't make it in time (but it wouldn't have mattered anyway) and so we'll be holding money indefinitely, which is good news if you want to withdraw your 1.0 money or migrate tips to a Team.
@kzisme P.S. a finer point re: Twitter ... http://dirkhoag.com/2012/10/how-to-twitter-why-do-people-put-a-period-in-front-of-tweets-86.
Re: https://twitter.com/Gratipay/status/654529569542828032.
;-)
Started on that blog post, will maybe get to work on it again later tonight.
@mattbk @kzisme Re: tweets about "Why didn't you contact me?" ... see also: https://github.com/gratipay/team-review/issues/85.
P.S. We're building something incredibly awesome. I love working with you all. :-)
!m *
Prolly gonna need to go to two days/wk consulting, meaning down to two days/wk for Gratipay. Probably Mondays and Wednesdays for Gratipay. I'm thinking Mondays for user-facing (cowo at Catapult) and Wednesdays for Team X and admin/bureau (cowo at Blue Canary, w/ @kaguillera ideally).
:cocktail:
I want to work on infrastructure, so @rohitpaulk @rorepo @yifeiwu @fenryxo et al. can rock on actual real code.
Embarrassment Driven Development (EDD): What is the most embarrassing thing about our situation? Let's fix that first! Oh, the pain!
Front of the house and back of the house.
Front of the house:
Back of the house:
That's what embarrasses me. What embarrasses you?
@mattbk @kzisme et al. Here's a rough draft of a blog post about the refunds:
https://medium.com/gratipay-blog/1-0-money-available-indefinitely-39c07bd031b
Let's try and get that out the door tomorrow, eh?
@whit537 I like the post the only part that reads funky to me is "We were only able to refund $3,089.23"
That whole paragraph could be formatted differently rather than having some of the numbers run together. Other than that it seems great!
Also, I suppose the EDD as shown above could be fleshed out into their own issues, right?
P.S. - I didn't know that adding a '.' before a tweet allowed for followers to see the tweet as well as have it reply to your own. Thanks for pointing it out :point_left:
@kzisme I think there's tickets for everything already.
Also embarrassing:
Inbox 2, GitHub 0, L2 Support 2, Vendors, etc. 0.
Diving into contracting gig here. I'll try to hit the blog post after lunch.
Can't edit Teams! gratipay/gratipay.com#3545
I'm pretty embarrassed by that. It's also a simple thing from a user perspective that doesn't make any sense.
Also embarrassed that I have to keep explaining the arrears thing, and why receiving and payouts don't match.
This is one of the cases where, if you're pitting "what the user wants" against "what's better for us," the user should probably win.
I think the blog post is clear.
Is one of the reasons people didn't hear about the Gratipay payout because they don't even have an email address set up here? I've seen that on several profiles. I know some people hate email, but it's pretty standard to require an email address to sign up for anything online.
The last ticket/issue I saw was that the user didn't read the email we sent. On Oct 16, 2015 4:01 PM, "mattbk" notifications@github.com wrote:
Is one of the reasons people didn't hear about the Gratipay payout because they don't even have an email address set up here? I've seen that on several profiles.
— Reply to this email directly or view it on GitHub https://github.com/gratipay/inside.gratipay.com/issues/368#issuecomment-148820141 .
Yeah, but if they never get an email, they don't even get the chance to ignore it.
Here's another interesting one. Haven't checked to see if true. https://twitter.com/3v4l_org/status/655381901851664384
Not quite confident to self-review, but this is sort of important and only a small change, so I'll go ahead if no problems reported in an hour or so. https://github.com/gratipay/gratipay.com/pull/3836
ETA: Actually, never mind. Need someone else to deploy anyway.
What are you working on this week and why?
last week