-
Notifications
You must be signed in to change notification settings - Fork 38
Radar 23 #332
Comments
Roadmap (what?)Next Four Weeks
Longer Term |
Queues (what?)
|
Highlights:
|
Inbox 4, GitHub 0, L2 0, Vendors 0. Diving back in on the Pivot ... |
Actually, I'm gonna land the 1.0 payout form first first, which is on Balanced Shutdown. |
... and that's leading me into charging in arrears, which will simplify our computation of 1.0 balances, and also has been in the works for a while and should be brought in for a landing. |
Landed arrears, back to payout form. |
Okay, payout form is out. I want to get Team review streamlined (gratipay/gratipay.com#3568) and then add Team images (gratipay/gratipay.com#3750) for bonus points if I can tonight. |
Alright, done for the night. I ended up getting side-tracked by gratipay/gratipay.com#3755, but I did manage to land streamlined Team review (gratipay/gratipay.com#3568), which joins streamlined 1.0 payout application and review from earlier today. Huzzah! 💃 |
Can I bump FD tickets to L2 if I am unsure about this? |
Actually, I can't seem to find/see the "Clear for payout" button anymore. Did it move? Did my name change affect this? |
@mattbk - Looking at https://github.com/gratipay/gratipay.com/pull/3744/files, looks like that was taken out. It's now placed on the user's profile page, over the profile picture - here are a few screenshots |
Thanks @rohitpaulk. I wasn't sure what that was. I think I understand the statuses now since there is a message that pops up when you change it. |
Looking a bit ahead: once we get through Pivot and Balanced Shutdown, what's next? We've got five other milestones:
That's existing milestones, but we'll also want to think about creating milestones that don't exist yet. I want something about encouraging corporate giving, e.g. |
Inbox 4, GitHub 0, L2 Support 0, Vendors, etc. 0. |
I just deleted about 15 branches that I had locally. Now I'm down to six (including master). :) |
I'm catching up on Support with a bunch of payouts to approve. Had a huge local event over the weekend, so last week and most of this week were spent in preparation/cleanup. |
Support 5. |
Alright, Team images are coming along: gratipay/gratipay.com#3750. I'm hoping to land that today. I also have to run payday: #335. |
!m @mattbk Did you have a race? How'd you do? :-) |
We put on a mud run. Nobody died. |
Nice. :-) |
Inbox 4, GitHub 0, L2 Support 0, Vendors, etc. 0, Payday 1, Lunch 1. |
Just made my first PR in Korean: https://github.com/teampopong/popong.com/pull/11. :-) |
Blog post about charging in arrears, ready for review: https://medium.com/gratipay-blog/charging-in-arrears-18cacf779bee. |
@whit537 I liked the post! I went ahead and shared it on the Gratipay Twitter as well! |
Alright, posted up at the bar, planning to land payday, and then Team images! |
Just gave the post a once-over and refined some of the language (no major changes). Since it's out on Twitter I went ahead and published it on Medium as well (it had been an "unlisted" draft): https://medium.com/gratipay-blog Okay! Now payday and Team images. :-) !m * |
Payday: check. Gonna take five and then dive back in on gratipay/gratipay.com#3750 ... |
Okay! I'm all scotch egged, ready to cap another 2**6 Team images! |
🏊 |
I have pinged The Changelog about new Teams and the big refund: thechangelog/ping#277. |
To: Adam and Jerod (Changelog)
|
Carol on Beyond Code: https://www.youtube.com/watch?v=-g9vlI43H-w. :-) |
We're live with http://gratipay-or-bountysource.guide/. :-) Cleaning up a couple things on IG ... |
"The other novel idea in open-source funding is Gratipay, where money is entirely divorced from deliverables." http://coffeeonthekeyboard.com/bounties-and-tips-1204/ He's working with old models for both Bountysource (as they move to recurring monthly) and Gratipay (as we move away from individuals to Teams), but the basic point I think still applies. |
Support 0. |
Inbox 5, GitHub 0, L2 Support 0, Vendors, etc. 0. I keep staring at these:
:-) |
Email (what?) |
What are you working on this week and why?
last week
The text was updated successfully, but these errors were encountered: