-
Notifications
You must be signed in to change notification settings - Fork 38
Radar 29 #377
Comments
Roadmap (what?)Short Term
Long Term |
Queues (what?)
|
Inbox 10, GitHub 26, L2 Support 3, Vendors, etc. 2. |
Inbox 5, GitHub 0, L2 Support 1, Vendors, etc. 1. Sitting down with @kaguillera. We're gonna start by knocking out gratipay/gratipay.com#3810, then ... |
@kaguillera and I are deciding what to work on next ... |
We went through the Balanced Shutdown milestone and trimmed it up (closed a few things, bumped a few others off the milestone). What's left are five pretty accessible copy changes, and then waiting for Balanced to send us our escrow (gratipay/gratipay.com#3826). |
We started going through the Pivot milestone as well, but got bogged down (when is the pivot done?), so we're pulling back from that and focusing on Balanced Shutdown. 🏊 |
Currently I'm studying for a software engineering midterm - but there's was/is a conversation going on (here)[https://twitter.com/GrahamDumpleton/status/655609676386598912]. Anyone have any ideas why some people seem to be completely unaware of where their funds are? (Also most of the people in that thread - if not all do |
We probably should've send out an email blast on September 1. We didn't because when we sent two email blasts back in May we got some blowback from people who considered us to be spamming them (see #235). Now we're getting ire from the other angle: people who want us to have sent them an email they didn't specifically ask for. At this point we've gotten enough negative feedback that the situation probably warrants some attention. Reticketed as #380. |
L2 Support 0. |
Okay! We've got the Balanced Shutdown down to one ticket! 💃 https://github.com/gratipay/gratipay.com/milestones/Balanced%20Shutdown The last ticket is about getting our escrow money out of Balanced: gratipay/gratipay.com#3826. |
@kaguillera and I had a conversation about project management. The proposal we were discussing is that we bring the Pivot in for a landing by closing whatever tickets we can, releasing the rest back into the backlog. I've found it helpful to have the Balanced Shutdown and Pivot milestones, but they've been too big, especially the Pivot. Milestones should last one week to one month. How many tickets is that for us? Here's the number of tickets closed per week, going back 12 weeks:
I interpret the wide variability (70% σ/μ) in on-milestone activity as saying that we can get distracted, and therefore it will help us to try to stay more focused week to week. I propose that we close the Pivot, and then try a two-week milestone, starting with 5-10 initial tickets and aiming for 16 ±10 tickets overall, counting on the number to grow as we reticket and make PRs. Furthermore, I propose that we do away with the star labels. I don't think they're helpful anymore. Or, if we keep them, we should only apply them to milestone tickets. |
Good for somewhere on inside.gratipay.com. |
seem like a good basis for a "complete teams" type of milestone. Or maybe they could be separate. |
The other thing is that I'm down to two days a week. @rohitpaulk has been back around, but we don't really have a ton of bandwidth, actually. 16 ±10 may be too ambitious. |
L2 Support 0, Vendors, etc. 0. |
I'm leaning in that direction. |
And I'm inclined to look at this next. |
Support 0 (for now). |
!m @mattbk Just sent one your way though (arrived via portal instead of email, hence landed in Vendors, etc.). ;-) L2 Support 0, Vendors, etc. 0. I just made a Basic Math milestone. Let's collect some tickets there. |
I moved three tickets from Pivot to Basic Math. That makes five: we have a milestone! 💃 |
💃 !m @mattbk |
Email (what?) |
What are you working on this week and why?
last week
The text was updated successfully, but these errors were encountered: