Radar 14

[chadwhitacre]

What are you working on this week and why?

last week

[chadwhitacre]

[chadwhitacre]

Last week I fixed the worst of our security bugs. Our security queue itself is half-broken since we're still between GitHub, Freshdesk and HackerOne (#255). I'm not prioritizing that this week, though. I want to focus on the worst remaining regressions from 2.0: closing accounts and history and subscriptions. A lot of the user pressure in our support queue is due to those bugs.

[chadwhitacre]

Something for our radar: our next big event is August 19, when we refund remaining 1.0 balances. That's 44 days away. At 30 days out, we should send an email to everyone affected. We should start getting ready for this now.

[chadwhitacre]

Alright, pressure is on on gratipay/gratipay.com#3539. Let's get account closing and history/subscriptions cleaned up ASAP, so we can get team review and one-time applications done before July 21.

[chadwhitacre]

@techtonik I just reviewed #263.

@kzisme @rorepo @rohitpaulk @mattbk et al. What's your availability and interest this week? Anyone looking for something to do? :-)

@pjz Should we try again this Thursday for the July Aspen call?

[pjz]

@whit537 only if you're going to show up.

[chadwhitacre]

@pjz Well, we don't have any half-released security fixes this week, which improves our chances. ;-)

Reticketed as AspenWeb/pando.py#472.

[chadwhitacre]

Who's pumped? I'm pumped. :-) 🍥 🍇 🛅

[chadwhitacre]

Okay, I tried to top up all of you fine folks on the PRs/issues you're working on. If I missed something let me know. I'm going to see about gratipay/gratipay.com#3461 after lunch ...

[chadwhitacre]

Inbox 3, GitHub 29, Support 58, PRs 28, Review 5, Security 6, Issues 749

[kzisme]

@whit537 I have some free time to do some small stuff - I know you mentioned working on the chrome extension and such. Anything bigger/smaller need to be looked at or thought about? I'm open to anything just trying to learn!

[chadwhitacre]

@kzisme Huzzah! 💃 Maybe look at gratipay/gratipay-everywhere#34?

[mattbk]

I've been trying to triage support tickets as I have time. Also have been trying to understand how 2.0 works in the process.

People's main concerns are

• What happened to my donations?
• How can I donate?

[techtonik]

Tried to rewrite algorithm.py docs to make it more clear that state is an actual dictionary and not some abstraction. PR is open AspenWeb/state_chain.py#12

Then I'd like to hack on "export to PNG" working in blockdiag - https://bitbucket.org/blockdiag/blockdiag_interactive_shell/issues/4/save-as-png as I find it rather annoying to use save/choose-name/open/choose-file/upload chain for just copy/pasting the image into another window.

Then I'd like to work on default blockdiag block style. Our radar plan is hardly readable, even though blocks have much free space.

And of course I need to address review comments in #263 after testing that it works as expected.

[rorepo]

Sorry @whit537, been a bit busy last couple of days. Relatively free for the rest of the week, so could take up something. Suggestions are welcome. Familiar area for me would be python/database, but I'm open to anything.

[chadwhitacre]

@mattbk @techtonik @rorepo Cool. I am working on Gratipay today and then off consulting again tomorrow. Next week I'll have four days on Gratipay. We've got our monthly Aspen call in half an hour, then I'm planning to check in on account closing before moving on to history and subscription pages cleanup.

@rorepo Want to help me land gratipay/gratipay.com#3601? :-) I need someone else to review it and then we can merge and deploy it together.

@mattbk I haven't reviewed your support replies yet ... have you been answering people? Do you know the answers to those questions? What do we need in order to communicate more effectively? Do our recent blog posts answer the questions?

[chadwhitacre]

@rorepo You could also start looking at gratipay/gratipay.com#3378 or gratipay/gratipay.com#3475. We should really have those before August 20. They're good and database-y. :)

[kzisme]

@whit537 What is your opinion about a few new issues being opened based off of #3556?

I was going to think about some new issues and possibly opening a few based on what @mattbk said.

Also - Is there a specific labeling scheme you like to use? I was going to start labeling new issues and things that came in.

I'll try to knock out the second chrome extension issue you mentioned earlier in the week.

[mattbk]

@kzisme I'd like it if you could help break out some of the issues at gratipay/gratipay.com#3556. It would be great to bounce some ideas back and forth about the UX.

[chadwhitacre]

!m @kzisme @mattbk

Feel free to create new labels. Please update http://inside.gratipay.com/howto/label-github-issues if/when you do (click the edit pencil at the bottom).

[chadwhitacre]

(P.S. I'm running payday: gratipay/gratipay.com#3606.)

[chadwhitacre]

Okay! Payday done.

Inbox 4, GitHub 47, Freshdesk 72

[chadwhitacre]

GitHub 46! :-)

🍴 🐘

[chadwhitacre]

GitHub 45

[chadwhitacre]

GitHub 38!

[chadwhitacre]

@mattbk May I give you admin bit on Gratipay? That will enable you to, among other things, clear users such as FD2523 for 1.0 payouts.

[chadwhitacre]

💃

[kzisme]

!m Everyone :D
On Jul 9, 2015 6:52 PM, "Chad Whitacre" [email protected] wrote:

[image: 💃]

[image: screen shot 2015-07-09 at 6 51 33 pm]
https://cloud.githubusercontent.com/assets/134455/8608716/99b7db14-266b-11e5-82a5-d6c06b05829f.png

—
Reply to this email directly or view it on GitHub
#283 (comment)
.

[chadwhitacre]

!m @kzisme 💃

[chadwhitacre]

@mattbk Re: #180 (comment) (let's avoid cluttering that already-overloaded ticket), are you aware of See Also? That's where we track competitors and such. Feel free to open a new ticket here in IG if you'd like to do an analysis of our competition.

[techtonik]

#263 is ready for review.

[chadwhitacre]

!m @techtonik

[chadwhitacre]

GitHub 0! 💃

[chadwhitacre]

That's mostly it from me for the week. I'm off consulting tomorrow. I'll be around four days next week, looking to land account closing and clean up history and subscription pages. Tootaloo! :-)

[techtonik]

• Upgrading Aspen to 0.37+ #263
• Broken 'Source Code' link. #178 (needs someone with Safari browser)

[mattbk]

@mattbk I haven't reviewed your support replies yet ... have you been answering people? Do you know the answers to those questions? What do we need in order to communicate more effectively? Do our recent blog posts answer the questions?

I can figure out the answers to come questions, but most of the "where's my money/did I get paid this week" don't seem to be something I can check. The reason I've been harping on the History page is that this is where people are looking for information, and they aren't finding it.

For example, https://gratipay.com/~nplainsathletes used to get $0.10 a week, but who knows what is happening now? All that shows on History after Payday 152 is that my escrow was transferred to PayPal. (This is not a support request, just an example). Considering that I've been lurking here and actively trying to figure things out and I still don't know, I can understand why people are confused.

[chadwhitacre]

@mattbk If you're willing to accept the admin bit (#283 (comment)) then you will be able to review people's history pages, which ... won't help a ton until we fix gratipay/gratipay.com#3455. :-/ I'm hoping to make a PR for that on Monday.

[chadwhitacre]

I love having an excellent reputation. :-)