-
Notifications
You must be signed in to change notification settings - Fork 38
Radar 22 #326
Comments
Roadmap (what?)Next Five Weeks
Longer Term |
Queues (what?)
|
I hived off a new Refund Announcement milestone from the Pivot. Refund blog post needs to go up tomorrow night (September 1), with email blast on Wednesday. |
I've trimmed up Refund Announcement. Gonna dive in on cleaning up the stats page ... 🏊 |
Okay! Stats PR is ready for review. Screenshot at gratipay/gratipay.com#3730 (comment). I'm gonna grab some lunch and coffee and then look at sprucing up the Team explorer: gratipay/gratipay.com#3704. That'll take care of all of the Cached Values work we need before the 1.0 announcement. After that I'll look at the Team Workflow issues. Once the workflow is nicer we'll open the floodgates and get that 1.0 refund announcement out the door! |
Alright, Team explorer! gratipay/gratipay.com#3704 |
Inbox 0, GitHub 0, L2 Support 0, Vendors, etc. 0. Alright, Team explorer! gratipay/gratipay.com#3704 :-) |
@rohitpaulk What's your schedule like? You heading back to school here? Think you'll be able to start contributing again? :-) |
Alright. I'm done for the night. I made it through the Cached Value tickets for Refund Announcement, and started in on Team Workflow with #3484. |
... that's gratipay/gratipay.com#3484. There are five tickets left on Refund Announcement. One is trivial (adding the "Apply" button to the homepage Team explorer), but we do also have to finish revising the blog post over on gratipay/gratipay.com#3539. The biggest chunk of work I'd really like to get done before the announcement is gratipay/gratipay.com#3568 ... and also gratipay/gratipay.com#3743. So that's six tickets left. Good night. :-) 🌔 |
Alright, tonight's the night to get this blog post up about the 1.0 refund. Gonna dive in here probably in an hour or two ... |
Okay! Trying something new: posted up at the bar tonight. Open late! :) 🍻 |
Inbox 5, GitHub 0, L2 Support 0, Vendors, etc. 0. Alright! What's next? Team review! gratipay/gratipay.com#3568 🏊 |
Actually, I'm gonna work on the blog post, under gratipay/gratipay.com#3539. That's the thing that absolutely has to get up tonight. We can make more changes to the site in the coming days once the post is up. |
Closed the Refund Announcement milestone. Gonna go sleep and take stock tomorrow. !m @mattbk |
I think it's a big, big !m @whit537this week! |
:-) Thanks, @mattbk. :-) You ready for a communications and support push? We want to pay out as many people as possible before October! |
Trying to catch up with all that have transpired since I have been missing |
I may have noticed this before, but it's fun to (re)discover: Matz is on Gratipay! :-) |
@mattbk Let's use the |
I've gone back through and tagged all closed tickets that were assigned to me as To: [email protected]
|
Got it. For now I'll check the tag of any issue I open before responding, although most of the ones I send to you are familiar. |
@mattbk Cool, thank you. It's fine if you want to respond to any reopened L2 (formerly assigned to me). I just missed FD2750 and FD1733, which I think you maybe thought were on my radar? Here's the view I check every day: https://gratipay.freshdesk.com/helpdesk/tickets/view/1000241179 |
The point being that if a ticket is not on here, then I'm not seeing it: https://gratipay.freshdesk.com/helpdesk/tickets/view/1000241179 |
I've added a note about escalating via |
Okay! Inbox 4, GitHub 0, L2 0, Vendors 0. |
|
|
I really want to get the 1.0-payout form out tonight if I can: gratipay/gratipay.com#3744. I'm knocked out tomorrow w/ consulting, and then we're into Labor Day weekend. |
Email (what?) |
What are you working on this week and why?
last week
The text was updated successfully, but these errors were encountered: