Radar 15

[chadwhitacre]

What are you working on this week and why?

last week

[chadwhitacre]

Map is the same afaict:

[chadwhitacre]

We've got a PR for closing accounts that we need to land: gratipay/gratipay.com#3601.

I'm hoping to get a PR for history pages today: gratipay/gratipay.com#3455.

I've got four days this week so hopefully we can get some stuff done. Anyone going to be around to help me land some PRs? 🐑 😁

[kzisme]

I'll be around a lot - keeping up with everything.

I'll probably look at the other extension issue at a minimum. Anything else small worth noting?:hammer:

[chadwhitacre]

Inbox 5, GitHub 3, Support 80, PRs 25, Review 5, Security 6-ish?, Issues 746

[chadwhitacre]

@kzisme Cool. Maybe gratipay/gratipay.com#3565?

[chadwhitacre]

@kzisme I tried pinging you in Google Hangouts Chat. You around?

[kzisme]

@whit537 Yup just replied

[mattbk]

I'm keeping an eye on Freshdesk support tickets, but there are some on there that are beyond my ken (checking bank transfer records, scheduling PayPal payouts, etc.). We can discuss at #280 if you'd prefer. Other than that, probably not much time this week.

[chadwhitacre]

I'm going to keep working on gratipay/gratipay.com#3618 for a bit this morning before heading over to meet @kaguillera at Blue Canary. I'll probably start self-merging PRs soon because I want to make sure we get some things out the door this week. I want to get account closing, history page updates (includes implementing double-entry accounting), and subscription page updates out the door before I get caught up on our support queue, since a lot of support queries depend on those.

When I'm able to digest support I'll review your work there, @mattbk, and see if there are ways we can make you more productive. Any time you're able to spend responding to people with a simple, "Sorry we're taking so long, we're trying to clean up some things, we'll get back to you again next week" message will help us out.

[mattbk]

That's pretty much what I've been doing.

On July 15, 2015 8:17:11 AM CDT, Chad Whitacre [email protected] wrote:

I'm going to keep working on
gratipay/gratipay.com#3618 for a bit this
morning before heading over to meet @kaguillera at Blue Canary. I'll
probably start self-merging PRs soon because I want to make sure we get
some things out the door this week. I want to get account closing,
history page updates (includes implementing double-entry accounting),
and subscription page updates out the door before I get caught up on
our support queue, since a lot of support queries depend on those.

When I'm able to digest support I'll review your work there, @mattbk,
and see if there are ways we can make you more productive. Any time
you're able to spend responding to people with a simple, "Sorry we're
taking so long, we're trying to clean up some things, we'll get back to
you again next week" message will help us out.

---

Reply to this email directly or view it on GitHub:
#284 (comment)

Sent from a phone that, although intelligent, is not street smart.

[chadwhitacre]

Awesome, thank you. :-)

!m @mattbk

[techtonik]

My queue:

• Attempt to simplify the docs with less abstract wording AspenWeb/state_chain.py#12 ready for review
• export to PNG for blockdiag - found a way to render SVG to canvas and then save as PNG - just need to code now. Learned some Clipboard API, and met with some SVG bugs on the way. Tried to use HTML imports from web components, but Firefox doesn't support them.

I am trying to get closer to client side javascript, and I'd like to visualize depersonalized data on GP 1.0 some day. I think that GP 2.0 is a necessary for us to survive, but it is not what people want. I still think we will resurrect GP one day.

http://www.forbes.com/sites/jurgenappelo/2015/07/08/the-peer-to-peer-bonus-system/

[chadwhitacre]

I'm back from the double-entry accounting 🐇 hole on gratipay/gratipay.com#3618 to land a quick fix for history pages on gratipay/gratipay.com#3616.

[kzisme]

I was considering opening a new issue, but I was curious if GSOC would be something we would want to do next year. Last year when I looked applicants (the orginizations) they were getting prepared pretty early. Would that be something you would be interested in @whit537

[rohitpaulk]

Just a word of caution - A GSoC program takes a lot of effort to manage, I doubt that we'll be able to pull it off in our current situation.

[chadwhitacre]

@kzisme Not a bad idea, but not something I'm ready to take on right now. I think @rohitpaulk is right and we should stabilize the project more first.

Okay! I've got gratipay/gratipay.com#3616 ready to go. I'm gonna see about gratipay/gratipay.com#3511 and then start merging PRs ...

[chadwhitacre]

I've self-merged account closing and a tiny bugfix. I'm going to spend some time on cached values, and then self-merge that (if I get far enough) along with history cleanup. Then I'm going to break for lunch and relocate to a coffee shop, whence I'll run payday and then start thinking about next steps on August 20, maybe getting into our support queue this evening. I guess I'd also like to rewrite the copy on the about pages and dust off stats as well. I think that could really help us not suck quite so bad and shouldn't be a ton of brain-work to get done before we start ramping up the communication engine ahead of August 20.

[chadwhitacre]

Breaking for lunch. Maybe I should keep going on cleanup today, tomorrow, and Monday. Next Tuesday is our target for communicating re: August 20.

[chadwhitacre]

Landed at this coffee shop. I'm releasing the PRs I merged earlier, then running payday.

[mattbk]

Account closing works! I plan on notifying everyone listed at gratipay/gratipay.com#3461 and fully closing at least a few Freshdesk tickets today or tomorrow.

[chadwhitacre]

That sounds awesome, @mattbk. Thank you! 💃

P.S. You might find one or two that want to close their account but own a team. Maybe reticket that from gratipay/gratipay.com#3461?

[chadwhitacre]

Erm, we already have gratipay/gratipay.com#3602. In that case maybe just copy over the notification list from gratipay/gratipay.com#3461 as relevant.

[chadwhitacre]

Payday done.

[chadwhitacre]

Alright, where am I?

Inbox 5, GitHub 5, Support 19, Vendors 51, etc.

[chadwhitacre]

Alright, where am I?

Inbox 5, GitHub 5, Support 20, Vendors 53, etc.

[chadwhitacre]

I'm gonna zip through the Vendors queue. That should go pretty quick.

[mattbk]

Notifications done for gratipay/gratipay.com#3461 related to account closing being back.

[chadwhitacre]

Yesssssssssssss.

!m @mattbk

[chadwhitacre]

https://www.stickermule.com/marketplace/1580-move-slow-and-make-things

[mattbk]

Notifications done for gratipay/gratipay.com#3455 related to History pages being fixed.

[chadwhitacre]

@mattbk Killin' it! 😎

I got #249 over the hump and dealt with #240 (comment).

[chadwhitacre]

The Freshdesk blog has good tips on running support. Their latest:

http://www.slideshare.net/Freshdesk/customer-servicetraining
http://blog.freshdesk.com/customer-service-training/

I've changed our subscription to their emails from vendors@ to support@ so the rest of yinz can benefit. :-)

[chadwhitacre]

Alright! We have five emails funneling into corresponding groups in Freshdesk:

• support@
• vendors@
• sales@
• safety@
• security@

With @mattbk stepping up, I'm going to try paying attention to Freshdesk in two queues:

• Support
• Vendors, etc.

We're currently at Support 20, Vendors, etc. 15.

[chadwhitacre]

Weeded Vendors, etc. Down to 9.

[chadwhitacre]

Moved three tickets out of "Pending." I suppose we could start using that state, but we should document it on http://inside.gratipay.com/howto/support-users if we decide to do that. Support 23.

[mattbk]

Yeah, I'll start doing what step five says:
"Regardless of what action you take, “Close” the ticket when you're done with it. If/when the user responds, it will be reopened automatically."

[chadwhitacre]

@mattbk Also note step 5 under "tips"

Do not include the Freshdesk URL in tickets. It's not immediately useful to users, and is only likely to confuse them.

Freshdesk includes that automatically when you start a reply, so you have to remember to remove it. Skimming through your recent replies it looks like you haven't been doing that. Otherwise your replies are looking good so far, which is a big help, thanks. :-)

[chadwhitacre]

Worked on #255. Vendors, etc. 1.

[chadwhitacre]

It was mis-classified. Vendors, etc. 0! Support 28.

[chadwhitacre]

I've given @mattbk admin bit per #280 (comment), and I've cycled out @seanlinsley @clone1018 and @Changaco:

=> select username from participants where is_admin;
┌─────────────────┐
│    username     │
├─────────────────┤
│ rohitpaulk      │
│ whit537         │
│ nplainsathletes │
└─────────────────┘
(3 rows)

[chadwhitacre]