Skip to content
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.

Radar 18 #302

Closed
chadwhitacre opened this issue Aug 3, 2015 · 16 comments
Closed

Radar 18 #302

chadwhitacre opened this issue Aug 3, 2015 · 16 comments

Comments

@chadwhitacre
Copy link
Contributor

What are you working on this week and why?

last week

@chadwhitacre
Copy link
Contributor Author

Roadmap (what?)

roadmap

@chadwhitacre
Copy link
Contributor Author

Queues (what?)

N Queue Description
0 Violations private communication amongst the safety team
8 Security private communication with security researchers
4 Legal private communication with our counsel
22 Support private communication with users
6 Applications public review of applications for new teams
105 Errors production errors
0 Vendors, etc. private communication with our vendors
(also includes low-volume mailboxes: safety and security)
13 Balanced Shutdown a milestone
20 Pivot a milestone
9 Milestones all milestones
3 Review work in the final stage of development
25 PRs work in progress
749 Issues public communication with contributors

@chadwhitacre
Copy link
Contributor Author

Okay! With that, I am heading afk for a bit of vacation. I will check in again briefly on Thursday for payday.

Have a great week, @gratipay! 💃

@chadwhitacre
Copy link
Contributor Author

!m *

@mattbk
Copy link
Contributor

mattbk commented Aug 3, 2015

A little bit of support this week for me.

Is there anyone available who knows how to close a team account? This has been requested at https://gratipay.freshdesk.com/helpdesk/tickets/2750 (login required).

@chadwhitacre
Copy link
Contributor Author

Here to run payday: gratipay/gratipay.com#3669.

@mattbk Team closing is gratipay/gratipay.com#3602.

@chadwhitacre
Copy link
Contributor Author

I'm reading Small is Beautiful this week.

@chadwhitacre
Copy link
Contributor Author

Okay! Back to vacation. :-)

See yinz Monday! 💃

!m *

@mattbk
Copy link
Contributor

mattbk commented Aug 6, 2015

Support 8, mostly waiting on solutions that I can't provide.

@mattbk
Copy link
Contributor

mattbk commented Aug 8, 2015

Documentation is darn good for getting Gratipay up and running--even I was able to do it on my local machine in less than an hour! Nice job, folks!

Now I can mess with things locally and maybe teach myself some Python in the process. This is exciting.

@chadwhitacre
Copy link
Contributor Author

!m @mattbk Nice! 💃

@chadwhitacre
Copy link
Contributor Author

We haven't communicated properly the extent to which Gratipay 2.0 is a from-scratch reboot. We have not been pooling up money since the Gratipocalypse, as many seem to think.

I've modified the "Update" on "Gratipocalypse" from:

We have returned to processing.

to:

We have relaunched as Gratipay 2.0.

And I've modified the opening paragraph of "Gratipay 2.0" thusly:

Last month, we warned that “it will be hard” for us to survive the demise of our vendor and close partner, Balanced Payments. Then we discovered that it “couldn’t be harder”: we had to stop processing paymentswent out of business, due to legal concerns with our old terms of service that came to light while migrating away from Balanced. Today, we’re pleased to announce that we have resumed processing paymentsrelaunched under new terms of service.

@chadwhitacre
Copy link
Contributor Author

I also changed "reopen" to "relaunch" in the second paragraph of "Off Balanced".

@chadwhitacre
Copy link
Contributor Author

Email (what?)

screen shot 2015-08-10 at 8 57 33 am

@chadwhitacre
Copy link
Contributor Author

The bounce rate spike is due to security research. Not sure about the complaint rate ...

@chadwhitacre
Copy link
Contributor Author

Looks like it was a single spam report, related (again) to security research.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants