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

Radar 34 #419

Closed
chadwhitacre opened this issue Nov 24, 2015 · 26 comments
Closed

Radar 34 #419

chadwhitacre opened this issue Nov 24, 2015 · 26 comments

Comments

@chadwhitacre
Copy link
Contributor

What are you working on this week and why?

last week

@chadwhitacre
Copy link
Contributor Author

Roadmap (what?)

Short Term

Embarrassments:

Long Term

Color code:

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

screen shot 2015-11-19 at 1 59 15 pm

@chadwhitacre
Copy link
Contributor Author

Inbox 13, GitHub 32, L2 Support 0, Vendors, etc. 1.

@kzisme
Copy link

kzisme commented Nov 24, 2015

Currently reading and working on some school stuff before Thanksgiving. Although...I work every day on my "break".

Sent out a tweet or so today. Been following along with development as much as possible!

@chadwhitacre
Copy link
Contributor Author

It would likely be helpful if the gratipay and inside.gratipay.com repos were to have 2.1 milestones.

That's @webmaven at gratipay/gratipay.com#3584 (comment) and #254 (comment). I had forgotten about Gratipay 2.1! 😊 Here's the comment where I introduced the idea:

The principle of business vision that is driving Gratipay 2.1 is that we want economic engines, because our mission is to cultivate an economy. We want companies. We don't just want "teams" that don't make any money. We want companies that make money and offer open work. We want open companies.

gratipay/gratipay.com#3399 (comment)

This also relates to "We are building viable open businesses. We are building viable open businesses. We are building viable open businesses":

screen shot 2015-08-13 at 1 46 29 pm

As well as @mattbk's question, "should we be selling before there is a completed product?" and the ongoing confusion about personally branded teams (it's a company named after you, not you). The conversation going on under "bring back payroll" also relates: gratipay/gratipay.com#3433 (comment).

I feel like we've got an important thing coalescing here. What is it and what does it mean?

@chadwhitacre
Copy link
Contributor Author

Also relevant: @webmaven's suggestion at gratipay/gratipay.com#3399 (comment) and gratipay/gratipay.com#3820 (comment) that we use "open organizations" instead of "teams" or "open companies."

@chadwhitacre
Copy link
Contributor Author

I feel like we've got an important thing coalescing here. What is it and what does it mean?

I think "it" is Gratipay 2.1. :-)

@chadwhitacre
Copy link
Contributor Author

gratipay/gratipay.com#3399 (comment) as modified by gratipay/gratipay.com#3399 (comment):

  • Gratipay 2.0: Payments and payroll for open work.
  • Gratipay 2.1: Payments and payroll for open organizations.

@chadwhitacre
Copy link
Contributor Author

Okay! Inbox 6, GitHub 0, L2 Support 0, Vendors, etc. 0.

Heading home for lunch and then #403.

@webmaven
Copy link

@whit537:

What is it and what does it mean?

"Where are we going, and what am I doing in this handbasket?" 😜

This week I will likely continue to participate in more team reviews, take a stab at the glossary page (#243).

Perhaps I will also do a UI fix (for which I added a new 'Design / UI' label), and see about creating a 'hard stuff' diagram (per #402 (comment), although there seems to be some confusion about whether it is about GP's required competencies, or about the hard stuff GP solves)).

@chadwhitacre
Copy link
Contributor Author

Call with Neal in T-10 minutes. View link will land on #403.

@chadwhitacre
Copy link
Contributor Author

Big new question: should we consider trying to join forces with Enspiral? #421

@kzisme
Copy link

kzisme commented Nov 27, 2015

A little off topic - but does anyone have suggestions on some Python books? (actual books not e-books)

@chadwhitacre
Copy link
Contributor Author

@kzisme I haven't learned Python from books, so there's none I can recommend directly. However, I have an irrationally high opinion of http://www.greenteapress.com/thinkpython/. YMMV. :-)

If you decide to work through it, I'd be happy to work through it with you. Maybe in a different repo?

@chadwhitacre
Copy link
Contributor Author

Embarrassments:

Our greatest embarrassment is that we don't have payroll. Our product is payments and payroll for open work/organizations, and WE DON'T HAVE PAYROLL. We are vaporware. 😞

@chadwhitacre
Copy link
Contributor Author

Everything not on the critical path to payroll needs to take a back seat. 💺

@chadwhitacre
Copy link
Contributor Author

What is the critical path to payroll? PCI DSS → Identity Verification → Payroll

@chadwhitacre
Copy link
Contributor Author

Roadmap, popping payroll:

roadmap

@chadwhitacre
Copy link
Contributor Author

Gosh. We have to start storing SSNs. Time to grow up.

@chadwhitacre
Copy link
Contributor Author

I feel as if my SSN should be the first SSN we store.

@chadwhitacre
Copy link
Contributor Author

Perhaps that's not leaderly enough, though (#404, #420, #72).

@chadwhitacre
Copy link
Contributor Author

It struck me in the past day or two that @mattbk and @webmaven have never experienced our payroll system. Nor has @kzisme. A new generation, unfamiliar with how it actually works™. That's scary! We need to bring back payroll! 😱

@chadwhitacre
Copy link
Contributor Author

Conclusion: building a vault (gratipay/gratipay.com#3504) is our highest-priority task, because it is the next step on the critical path to payroll. Objections?

@kzisme
Copy link

kzisme commented Nov 29, 2015

I agree on that step 👍

Also I created that repo!

@kzisme
Copy link

kzisme commented Nov 30, 2015

Also - I was poking around and found this he's one of the creators of Bootstrap and he still has a Gittip link in his Github profile. It makes me happy to see that BUT wouldn't someone in charge of something as large as Bootstrap be interested in Gratipay 2.0?

Just a thought :)

@mattbk
Copy link
Contributor

mattbk commented Nov 30, 2015

@kzisme I'm not sure that guy on Twitter knew what we meant by "1.0 payouts." His previous tweets made it sound like he thought we had reverted from 2.0.

@chadwhitacre
Copy link
Contributor Author

Email (what?)

screen shot 2015-12-01 at 2 02 21 pm

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

4 participants