Radar 44

[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 (use id as primary key instead of username gratipay.com#835)
• widgets are broken (Radar 31 #389 (comment))
• escrow imprecision (Radar 31 #389 (comment))
• no payroll! bring back take-what-you-want gratipay.com#3433
• 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]

#479 (comment)

As long as you're available for review, that is fine with me :)

I'll try to keep up and contribute for as long as I'm able/needed. gratipay/gratipay.com#3909 :-)

[chadwhitacre]

This fellow thinks Twitter is dying because of abuse.

[mattbk]

That's interesting, since I find Twitter to be a generally positive force in my life. Oh wait, I mean the people I follow on Twitter.

[chadwhitacre]

:-P

[chadwhitacre]

@kaguillera and I are gettin' good and pissed over here (okay, mostly me :) at gratipay/finances#3.

[chadwhitacre]

Hey @mattbk et al., do you remember what week it was when we passed $1M?

[chadwhitacre]

Made a pass through team review.

[mattbk]

Hey @mattbk et al., do you remember what week it was when we passed $1M?

#389 (comment)

[mattbk]

@kaguillera and I are gettin' good and pissed over here

🍻

[chadwhitacre]

#389 (comment)

Thanks! :)

[chadwhitacre]

Any objections to me making gratipay.com/master a protected branch?

[rohitpaulk]

👍, that's a good idea

[chadwhitacre]

Sent to @justinxreese (founder of Code & Supply and host of the upcoming Abstractions conference) in private email:

I was just thinking today about how the offline FOSS community experience is so different from the online (Twitter) experience, and that maybe it's time to reconnect offline. :) We're aiming to publish a tiny post about the Gittip crisis in a week or two ("319"—as I recall, you saw some early wrestling with that, in the back room at Sprout). Maybe I'll re-emerge after that bit of closure? Build Night on Feb 29, ya?

[chadwhitacre]

👍, that's a good idea

It would prevent, e.g., gratipay/gratipay.com@0a546eb ~= gratipay/gratipay.com#3907. cc: @techtonik ;)

[chadwhitacre]

Though it would also prevent us from pushing markdown changes directly to master. That's probably a fair tradeoff.

[chadwhitacre]

Maybe we should have Gratipay meetups?

[chadwhitacre]

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

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

gittip—#319
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]

The milestones like Team Basics and Pivot collect lower-level tickets that ideally more recently onboarded contributors can get done. Someone newly onboarded is not going to build an accounting system or drive Aspen to 1.0.

I think I need to focus my time in thirds:

• tackling big projects
• enabling the team—going through tickets, writing good descriptions, labeling, pruning
• representing Gratipay to the outside world

[chadwhitacre]

@aandis @deivid-rodriguez et al. Wanna help us land the Team Basics milestone? :-)

[chadwhitacre]

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

[mattbk]

The milestones like Team Basics and Pivot collect lower-level tickets that ideally more recently onboarded contributors can get done. Someone newly onboarded is not going to build an accounting system or drive Aspen to 1.0.

Could this be added to http://inside.gratipay.com/howto/onboard-yourself?

[chadwhitacre]

@mattbk Good call. Constantly reviewing and updating the IG docs is definitely a part of TeamX. :-)

[mattbk]

Which in itself is something good for new onboardees to start with.

[chadwhitacre]

Which in itself is something good for new onboardees to start with.

Yeah, but I think that's usually considered a cop-out. On the one hand, new contributors shouldn't get the less glamorous tasks that no-one "more important" can be bothered to do. It's a sign of a healthy project when the most senior people do their share of toilet cleaning. On the other hand, it's the more senior folks that know what the documentation is supposed to say! :-)

[chadwhitacre]

@mattbk Do you have interest and bandwidth to take responsibility for the freshness of the IG docs? You're not a newbie any more, so I can ask. ;-)

[mattbk]

Good point. I try to change things when I see they are out of date, but I might start making issues just so I'm reminded.

[chadwhitacre]

!m @mattbk

[aandis]

Wanna help us land the Team Basics milestone?

Heh! Yes! :)

I was thinking to start with #3545 or #3736 once we land #3909. Things are a little busy at college. I'll try to do as much as I can. :)

[chadwhitacre]

@aandis Awesome! I think we're close on gratipay/gratipay.com#3909 (I'm willing to help with the README update if you don't get to it first). Either of those others you mention would be a great next ticket.

!m @aandis

[chadwhitacre]

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

[chadwhitacre]

@mattbk @kzisme Payday 152? That was a while ago. :-P

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

[mattbk]

I have fat fingers, apparently.

[chadwhitacre]

Any objections to me making gratipay.com/master a protected branch?
👍, that's a good idea

Hearing no objections ...

[mattbk]

Took a crack at the Widgets 2.0 milestone, but I don't understand exactly how the tests failed.

[techtonik]

👍 on protected master.

[chadwhitacre]

@techtonik :-)

[chadwhitacre]

Email (what?)