Radar 35

[chadwhitacre]

What are you working on this week and why?

last week

[chadwhitacre]

Roadmap (what?)

Short Term

Embarrassments:

• can't edit teams (Team Basics)
• not using immutable ids (https://github.com/gratipay/gratipay.com/issues/835)
• widgets are broken (https://github.com/gratipay/inside.gratipay.com/issues/389#issuecomment-153884921)
• escrow imprecision (https://github.com/gratipay/inside.gratipay.com/issues/389#issuecomment-153929881)
• Security 9 (https://github.com/gratipay/inside.gratipay.com/issues/389#issuecomment-153930768)
• no payroll! https://github.com/gratipay/gratipay.com/issues/3433

Long Term

Color code:

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

[rohitpaulk]

https://twitter.com/asm/status/664160319950880768

[chadwhitacre]

RIP Assembly

[chadwhitacre]

Heard from @progrium in private email. We're planning on a Hangout tomorrow at 2pm CST to catch up. I'll post the view link here. Our last call got some press coverage. :haircut:

[chadwhitacre]

Yikes! I guess HTTP/2 is here! Received in email this morning (re: whit537.org).

[chadwhitacre]

Okay! #319 topped up. Time for payday ...

[mattbk]

Just read https://github.com/gratipay/gratipay.com/issues/3862#issuecomment-161337126 and had an idea (not sure if it merits its own ticket yet). In the same way that we have talked about showing "excess" funds for teams, maybe we could encourage people to donate "excess" funds toward covering transaction fees for the smallest (below a certain value) donations.

This would essentially be a group pool; so rather than donating to a specific team (or to the Gratipay team), you'd be donating to everyone (both givers and receivers), by allowing them to keep more of their money.

It might be worthwhile to highlight how much users are paying in transaction fees on /about/charts as well, in order to encourage this.

Implementation could be an addition to a user's account in some way, or it could just be set up as a "special" Team--and then the receipts from that team each week could be used to replenish transaction fees.

Obviously not a priority, but just thinking about different ways for people to give.

ETA: ...although you could only distribute donated fees to people who had not donated their fees, otherwise the system wouldn't work. I suppose the idea of limiting this to the smallest receivers/largest givers could balance it out, though.

[chadwhitacre]

Inbox 10, GitHub 2, L2 Support 0, Vendors, etc. 0.

[chadwhitacre]

Call with @progrium: https://www.youtube.com/watch?v=RkDSXUQO9ys.

[kzisme]

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

[chadwhitacre]

!m @kzisme

[kzisme]

I watched the call as well - very interesting points made!

[chadwhitacre]

Nice! Thank you! :-)

[chadwhitacre]

Here's part of a private email I just sent to @oakes, pursuant to #392:

Gratipay has been a wild ride this year. We built a house of cards and it came crashing down six months ago (way sooner than it would've otherwise, because we're open: a vindication), in what we called "the Gratipocalypse"—wait—that was your word, wasn't it!? Thank you, tentatively! :-) Now we are "Gratipay 2.0" and we are slowly baling water out of the ship and repairing the mast, etc.

1. payments law—this is what we fixed six months ago
2. community management—also fixed with 2.0, but still looking for clojure (get it!? get it!?) on the "Gittip crisis"—hot right now
3. governance—still not a cooperative
4. generally accepted accounting principles—aka double-entry accounting. We didn't do them/it, and now we have three years and $1,000,000 of catching up to do (the data's all there, but ...).
5. tech debt—db ids should be immutable; Aspen is a failure; etc.
6. infosec—we need to implement PCI-DSS so we can store SSNs
7. employment law—we turned off our payroll feature, and none of us are getting paid. Eep!
8. product development—it's better than it was but still a mess: oh! for cycles!
9. marketing—ripe fruit! ripe fruit!
10. support—running pretty good, got good peeps on email and Twitter

Maybe shows where my heads at. :-)

[kzisme]

Random question - (I'm not sure if it's worth sending @whit537 an email)

How do you all list OSS contributions on your resume? Normally when I say I'm interested in OSS people say "Oh yeah! I use this "insert large OSS project here" but I don't contribute to it"

What constitutes a contribution? I'm a software developer - but I haven't contributed much code to Gratipay...yet so I would feel bad mentioning it under "contributions"

[chadwhitacre]

Email (what?)