Radar 48

[chadwhitacre]

last week

---

Docs

http://inside.gratipay.com/howto/sweep-the-radar

Roadmap

Short Term

Embarrassments:

• not using immutable ids (use id as primary key instead of username gratipay.com#835)
• widgets are broken (Widgets for Gratipay 2.0)
• escrow imprecision (Radar 31 #389 (comment))
• no payroll! bring back take-what-you-want gratipay.com#3433 (Payroll)
• Team and ~user pages are the same Differentiate participants and projects gratipay.com#3852

Long Term

Color code:

• red—external forces that we're under
• yellow—administration
• green—product development
• orange—marketing
• blue—capitalization

[chadwhitacre]

This radar brought to you by a script! :-)

I ran it locally for this week. Deploying to be run automatically each week ticketed as gratipay/bot#3.

[chadwhitacre]

I wrote the script in such a way that it will automatically adjust as we add more team radars in the future. Docs forthcoming ...

[mattbk]

Would love to merge gratipay/gratipay.com#3923 this week and knock off 1/6 of the embarrassments.

[chadwhitacre]

Inbox 15, GitHub 48, L2 Support 0, Vendors, etc. 16. 😩

[chadwhitacre]

Vendors, etc. 1.

[chadwhitacre]

As @clone1018 indicates at #467 (comment), payday is back in my court this month.

[chadwhitacre]

GitHub 1.

[mattbk]

I just merged gratipay/gratipay.com#3923 since it seemed justified. I won't be offended if it's unmerged (PR is the work of @aandis, nice job!). Mostly I'm assuming that @rohitpaulk didn't have any other issues with it; if that's wrong I'm sorry.

I remember the rule about "no self merging" by which I took the initiative to merge that PR, but when looking at http://inside.gratipay.com, I couldn't find a reference to that rule, or other things I should check before merging. Where should I look?

[chadwhitacre]

!m @mattbk

As far as I'm concerned, you did the right thing. It's really great to have the three of you moving development forward while I and others are preoccupied with other things. That's the way Gratipay is going to grow. Zuck don't write no code. 😳

Under the influence of @JeffSpies and @hurlothrumbo, I'm thinking that my role this year should be more in the sales and marketing departments (also security, governance, accounting). As embarrassing as our product is, we still have a few new Teams signing up each week—and significant ones such as Karma and Fallen Fruit (which @JessWhit heard about "in the wild" on Facebook—a first!). It seems to me like a powerful combo to have @mattbk running outside-in product management ("embarrassments") in combination with @rohitpaulk and @aandis doing the heavy lifting ("real work" ;). With those bases covered, I see other areas as needing more attention from moi. Ain't no-one else ready to sell that I can see, and I think it's time to start pouring more traffic in the top. Insofar as people fall out the sides, we simply have an opportunity to grow our contributor base ("Help us improve!").

You ready for 2016, @gratipay?

[chadwhitacre]

God I don't wanna be Zuck. 😳

[chadwhitacre]

Which of course means that I also kind of do, amirite? 😞

In 🍷 the truth.

[chadwhitacre]

@mattbk @kzisme With the sales/marketing focus, I'm interested in getting more involved with the Gratipay Twitter again. What's the current state of play and what do we need to work out amongst ourselves so we (I) don't step on toes?

[chadwhitacre]

I just went through and unfollowed the few individuals we were following. Seems cleaner for Gratipay to follow other companies/orgs/brands.

[chadwhitacre]

Made a few tweets cross-promoting our customers:

https://twitter.com/Gratipay/status/704869890641952774
https://twitter.com/Gratipay/status/704869477746286592
https://twitter.com/Gratipay/status/704869031161888768

Don't want to blow our wad. We've got 156 more approved teams to work back through—follow and retweet. If we do one or two a day that should last six months and maybe get a ball rolling. Thoughts?

[chadwhitacre]

From Heroku:

Your database (MAROON on gratipay) must undergo maintenance.

Several vendors recently disclosed a vulnerability (CVE-2015-7547) in the getaddrinfo functions in libc which allows an attacker to potentially execute remote code via DNS lookups returning a specially-crafted payload. You can find more details about this vulnerability in this excellent writeup by Google Security. As a result, we need to perform maintenance to your database as soon as possible to apply the patch for this vulnerability. We plan on performing this maintenance at 2016-03-01 19:00:00 +0000 during your set maintenance window of Tuesdays 19:00 to 23:00 UTC.

At that time, we will restart your database or database server as needed.

You may choose a new or more appropriate maintenance window, as needed. For example, you may run: heroku pg:maintenance window="Tuesday 14:30" to set a maintenance window for Tuesdays at 2:30pm UTC.

You can also run this maintenance directly, using heroku pg:maintenance run.

---

Maintenance on your database (MAROON on gratipay) has been completed and your database is now back online.

We expect operations to continue normally, but feel free to notify us if there are any outstanding issues with your database (MAROON on gratipay).

[chadwhitacre]

cross-promoting our customers

With 150+ customers, seems like a pretty solid strategy to simply amplify their good news. Gonna be something from somewhere most weeks, and it's a natural piggy-back, win-win.

[chadwhitacre]

Inbox 6 7, GitHub 1.

[kzisme]

@mattbk @kzisme With the sales/marketing focus, I'm interested in getting more involved with the >Gratipay Twitter again. What's the current state of play and what do we need to work out amongst >ourselves so we (I) don't step on toes?

I've just been checking for users who have been interacting with us on a daily or every other day basis. Other than that I think it would be a good idea to promote teams that are signing up and just continuing to link 'Gratipay' to other entities (teams) for increased exposure.

[aandis]

I created a bug label for gratipay issues to highlight high priority issues, mostly on production. I hope that's okay.

[chadwhitacre]

@kzisme Okay. I guess we'll just have to watch for any time we have multiple people engaging with the same person at the same time.

I worked through more of the accepted teams list, down to OS.js. It's easy to tell where I stopped by looking at the "Following" on Twitter.

[chadwhitacre]

@aandis Yay! I was meaning to ask if you had permission to modify labels. I guess that's a yes. :-)

[chadwhitacre]

Inbox 6, GitHub 2, L2 Support 0, Vendors, etc. 1.

[chadwhitacre]

I'm on payday today. I'm trying to get @gratipay-bot to kick off a payday ticket automatically.

[chadwhitacre]

Yesssssssss! #526.

[chadwhitacre]

Lunch 1. Then more gratipay/gratipay.com#3934 and payday (#526).

[chadwhitacre]

@aandis Do you use Twitter? I looked and didn't find an account for you, re: https://twitter.com/Gratipay/status/705470198980022272.

[aandis]

https://twitter.com/aandis_

[chadwhitacre]

Thanks! :-) https://twitter.com/Gratipay/status/705488919681437698

[aandis]

😊

[chadwhitacre]

How the heck are we ending up with so many people who enter their credit card information but don't set up a tip? I'd expect the funnel to leak in the other direction—people set up a tip, but don't put in credit card info (not that the two are mutually exclusive).

[chadwhitacre]

Screencap is from the review dashboard, btw.

https://gratipay.com/dashboard/

[mattbk]

Is that what the review dashboard means? I figured those were just accounts, didn't realize they had set up a credit card already

Not all of those accounts have a credit card set up.

[chadwhitacre]

Yeah, it's pretty broken. 😞

[rohitpaulk]

Reticketed as gratipay/gratipay.com#3937

[chadwhitacre]

!m @rohitpaulk

[chadwhitacre]

More positive vibes on Twitter from gratipay/gratipay.com#3923:

https://twitter.com/caspervonb/status/705768187850203136
https://twitter.com/thientranduy/status/705566282532261889
https://twitter.com/anthonny_q/status/705493245455896576

Great work, @aandis et al.! 💃

Shall we keep working down the Team Basics milestone?

[aandis]

Could land #3873. It looks near completion.

[chadwhitacre]

... which gets down into gratipay/gratipay.com#3876. I've added that to Team Basics as well.

[chadwhitacre]

First tweet in French-ish:

https://twitter.com/Gratipay/status/705858243961212928

🇫🇷 😄

s_b_sh has been engaging with us a lot lately and advertises Lille as their location.

[chadwhitacre]

Who's excited for @gratipay-bot to rotate the Radar this weekend! ✋

[chadwhitacre]

Picking up from #487 (comment) ...

Here's the big things I'm thinking about and working on:

accounting—gratipay/finances#3
aspen—AspenWeb/pando.py#357

governance—#72

vault—gratipay/gratipay.com#3504
payroll—gratipay/gratipay.com#3433

TeamX—I want to make Gratipay really fun and easy to hack on.
marketing—I want to find the people that want to know about Gratipay, and tell them about it.

[chadwhitacre]

D'oh! I tried changing the star labels to 😳, but GitHub wouldn't let me. Pretty sure I hit this before, actually. :-/

[chadwhitacre]

I'm thinking about embarrassment driven development, you see. :-)

[chadwhitacre]

Email (what?)