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

Radar 53 #558

Closed
gratipay-bot opened this issue Apr 3, 2016 · 46 comments
Closed

Radar 53 #558

gratipay-bot opened this issue Apr 3, 2016 · 46 comments

Comments

@gratipay-bot
Copy link

← Radar 52


Docs

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

Scope

This radar covers everything in the Gratipay organization that is not covered by another radar.

Roadmap

Short Term

Embarrassments:

Long Term

Color code:

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

roadmap

@chadwhitacre
Copy link
Contributor

Now that gratipay/gratipay.com#3110 is landed, I've manually updated the owner of the aspen team to be ~Aspen.

https://gratipay.com/aspen/
https://gratipay.com/~Aspen/

@chadwhitacre
Copy link
Contributor

I'm really encouraged by the traction we're getting with the take-what-you-want story (#552)!

  • we're queued up for the Platform Coops book
  • OuiShare Fest is giving us a great spot on stage
  • OpenSource.com is excited about us
  • Code & Supply is excited, too
  • we even have a shot at Abstractions

We need to keep chipping away at grossnesses such as capping unfunded dues and db + accounting cleanup and widget cleanup, and of course we need to stay on top of our security queue. But with the opportunities that are lining up for us to tell the "take-what-you-want" story, I for one am ready to dive into identity and then payroll for the Gratipay Team ... and then for everyone else!

Yay for product and marketing! ☯

@rohitpaulk
Copy link
Contributor

My focus for this week is to get gratipay/gratipay.com#3873 (team receiving page) out and take a look at Amazon SES (#515)

edit: And run payday

@chadwhitacre
Copy link
Contributor

!m @rohitpaulk

Awesome! I will try to help as I'm able.

@aandis Do you have any cycles this week to help @rohitpaulk land gratipay/gratipay.com#3980 gratipay/gratipay.com#3981 and gratipay/gratipay.com#3873?

Today is full of calls for me: French tutor, Cobudget, @tlevine, and Bountysource. Tomorrow and Thursday are clearer.

@chadwhitacre
Copy link
Contributor

Some 🚿 thinking this morning: we are a "functional non-profit." We're not organized using a non-profit legal structure, but we act like one because we don't distribute profits to our owners (our owners participate in compensation sharing the same as the rest of our members—i.e., not at all just yet! :). Something to work into the "Governance" chapter of The Gratipay Guide, as well as the question of our operating agreement (#72).

@chadwhitacre
Copy link
Contributor

Inbox 4, H1GH 1, L2 Support 0, Vendors, etc. 0.

@aandis
Copy link

aandis commented Apr 5, 2016

Sure. I'll go over them and see what I can do. :)

@chadwhitacre
Copy link
Contributor

!m @aandis Thanks! :-)

@chadwhitacre
Copy link
Contributor

@chadwhitacre
Copy link
Contributor

Also, Recurrency:

Recurrency was dreamed up on a WriteyBoard in Noe Valley.

Actually, it was dreamed up in my head, and then Jason Calacanis found someone to clone Gittip when I wouldn't talk to him privately. 🍤

@chadwhitacre
Copy link
Contributor

Okay, enough grousing. To bed! 😴 💤 :-)

@rohitpaulk
Copy link
Contributor

we have a page full of nickels

Increase the minimum tip to 1 dollar 🎉 I remember suggesting this a while ago, can't seem to find the ticket though. I guess I'll create a new one if I can't find it today

@chadwhitacre
Copy link
Contributor

Increase the minimum tip to 1 dollar 🎉

Then I'd have to up my giving by $66.50 (256%) in order to keep 70 out of 171 approved teams (40%) from receiving 0. 😞

I don't think we want to cut off the bottom end, I think we want to add back in the top end. How do we bring back companies giving on Gratipay?

screen shot 2016-04-06 at 4 22 52 am

@chadwhitacre
Copy link
Contributor

How do we give our Teams the tools they need to succeed?

@aandis
Copy link

aandis commented Apr 6, 2016

I remember suggesting this a while ago.

@rohitpaulk we had a discussion about this a while ago but we didn't create the ticket.

@chadwhitacre
Copy link
Contributor

@aandis @rohitpaulk Upping the minimum from $0.01 to $1.00 might make a difference if we had lots of givers < $1.00, but 40% of our teams have no givers at all. 0 x $1.00 is the same as 0 x $0.01. How do we change the 0?

@mattbk
Copy link
Contributor

mattbk commented Apr 6, 2016

I’d bet that @Medium introduces some sort of micropayment features soon.

https://twitter.com/R27D/status/717548120691769348

@chadwhitacre
Copy link
Contributor

I've deployed 1946, which includes gratipay/gratipay.com#3986, gratipay/gratipay.com#3984, and gratipay/gratipay.com#3983.

I'm now deploying a fix for H1-115284 ...

@chadwhitacre
Copy link
Contributor

gratipay/gratipay.com@4edbaf7 deployed. As you were!

@chadwhitacre
Copy link
Contributor

We're due for another blog post. Maybe on our HackerOne program? It's become quite important to us—to me at least, in terms of time and attention spent on it.

@chadwhitacre
Copy link
Contributor

@rohitpaulk @clone1018 Let's get in the habit of announcing here when we're going to deploy. That way hopefully we can avoid stepping on each others toes (not that it's usually an issue right now, but it's easy enough to do and a good habit to form).

@chadwhitacre
Copy link
Contributor

I'm deploying gratipay/gratipay.com#3987 ...

@rohitpaulk
Copy link
Contributor

rohitpaulk commented Apr 6, 2016

"Radar ticket as a mutex"

@chadwhitacre
Copy link
Contributor

@mattbk Do you remember what tickets we +1'd recently for the AsciiDoc maintainer? They were coming to us from Bountysource, we should really try to make them happy.

@chadwhitacre
Copy link
Contributor

Deploying c9e9ac2 got hung up in Travis. I've restarted the build.

@chadwhitacre
Copy link
Contributor

Hmm ... failed again ...

@chadwhitacre
Copy link
Contributor

Fixed in 28dcc03. IG deployment is back on track.

@mattbk
Copy link
Contributor

mattbk commented Apr 7, 2016

@mattbk Do you remember what tickets we +1'd recently for the AsciiDoc maintainer? They were coming to us from Bountysource, we should really try to make them happy.

I don't remember without additional information, sorry.

@chadwhitacre
Copy link
Contributor

@mattbk It was something about companies needing invoices (I thought, though I don't see anything recent on gratipay/gratipay.com#1199), and ... bank payins?

@chadwhitacre
Copy link
Contributor

Found it! gratipay/gratipay.com#777 (comment)

@mattbk
Copy link
Contributor

mattbk commented Apr 7, 2016

@chadwhitacre
Copy link
Contributor

💃

!m @mattbk

@mattbk
Copy link
Contributor

mattbk commented Apr 7, 2016

Nice work everyone this week!

@chadwhitacre
Copy link
Contributor

They were coming to us from Bountysource, we should really try to make them happy.

Reticketed as #563.

@chadwhitacre
Copy link
Contributor

Inbox 5, H1GH 2, L2 Support 0, Vendors, etc. 0.

@chadwhitacre
Copy link
Contributor

@rohitpaulk Wanna deploy gratipay/gratipay.com#3981?

@rohitpaulk
Copy link
Contributor

On it..

@rohitpaulk
Copy link
Contributor

Deployed, script output verified.

@chadwhitacre
Copy link
Contributor

Woo-hoo! One less pretty embarrassing thing! 💃

@chadwhitacre
Copy link
Contributor

Dang. Ridin' pretty high after #563 (comment). Let's make that happen!

Looking at milestones ...

  • I just converted "Email" from a milestone to a label. I think that better fits the way those tickets were related.
  • Where's the verb!? I just renamed a few to make it clearer that these are basically big todos:
    • "Payroll" → "Bring Back Payroll"
    • "AML Program" → "Implement an AML Program"
    • "Team Basics" → "Finish Team Basics"
  • I still think we should prioritize Finish Team Basics and Pivot. We are so close! Let's finish those up.
  • Let's talk about what comes next:

I would actually propose a new milestone: Solve Corporate Sponsorship of Open-Source. We know from #563 and from past experience that this is a big opportunity for us. The market is there and it hasn't been cracked yet. I'm pretty sure we still want to go after it—how does everyone else see this in relation to our other milestones and potentially other opportunities?

@chadwhitacre
Copy link
Contributor

I'm deploying gratipay/gratipay.com#3873.

@chadwhitacre
Copy link
Contributor

We just deployed a "Receiving" page for Team owners.*

*Warning: it's a bit rough. Release early, release often! :-)

screen shot 2016-04-09 at 4 06 18 pm

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

@chadwhitacre
Copy link
Contributor

And with that, I think we've got the Finish Team Basics milestone down to four tickets! Can we keep pushing and get that milestone closed?

@chadwhitacre
Copy link
Contributor

I've added a number of tickets to "Solve Corporate Sponsorship of Open-Source," though I don't think we should dive head-first into that quite yet. Let's see how #563 goes.

@chadwhitacre
Copy link
Contributor

The "Widgets for Gratipay 2.0" milestone in the grtp.co repo should be considered another chunk of Pivot, and perhaps even part of Finish Team Basics.

@chadwhitacre
Copy link
Contributor

chadwhitacre commented Apr 14, 2016

Email (what?)

screen shot 2016-04-14 at 10 37 32 am

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

5 participants