-
Notifications
You must be signed in to change notification settings - Fork 38
Radar 28 #368
Comments
Roadmap (what?)Short Term???—We just got through the Balanced Shutdown. Need to take stock and regroup. Long Term |
Queues (what?)
|
Deployment is hosed. Immediate concerns for me today are:
|
Deploy issue: gratipay/gratipay.com#3821. |
Deployment back on track. I've looked at gratipay/gratipay.com#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 |
Thanks, @kaguillera. Happy birthday! :-) |
🎂 |
Alright! Caught up on local queues—Inbox 2, GitHub 0, Vendors 0, L2 Support 0! Also getting pumped for Speak Freely: #334. @kzisme Here's the event to promote: https://twitter.com/SpkPgh/status/652403773843841024. |
Let's see about refunding advances on Braintree ... gratipay/gratipay.com#3810. |
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... |
@mattbk We had two main sources of escrow:
On gratipay/gratipay.com#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.
Once I land gratipay/gratipay.com#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: gratipay/project-review#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). |
🍸 |
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 👈 |
@kzisme I think there's tickets for everything already. Also embarrassing:
|
What are you working on this week and why?
last week
The text was updated successfully, but these errors were encountered: