Closed chadwhitacre closed 8 years ago
Color code:
Inbox 13, GitHub 32, L2 Support 0, Vendors, etc. 1.
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!
It would likely be helpful if the gratipay and inside.gratipay.com repos were to have 2.1 milestones.
That's @webmaven at https://github.com/gratipay/gratipay.com/issues/3584#issuecomment-159010620 and https://github.com/gratipay/inside.gratipay.com/issues/254#issuecomment-159011112. I had forgotten about Gratipay 2.1! :blush: 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.
https://github.com/gratipay/gratipay.com/issues/3399#issuecomment-112110512
This also relates to "We are building viable open businesses. We are building viable open businesses. We are building viable open businesses":
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: https://github.com/gratipay/gratipay.com/issues/3433#issuecomment-158986489.
I feel like we've got an important thing coalescing here. What is it and what does it mean?
Also relevant: @webmaven's suggestion at https://github.com/gratipay/gratipay.com/issues/3399#issuecomment-159010969 and https://github.com/gratipay/gratipay.com/issues/3820#issuecomment-159033281 that we use "open organizations" instead of "teams" or "open companies."
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. :-)
https://github.com/gratipay/gratipay.com/issues/3399#issuecomment-112110512 as modified by https://github.com/gratipay/gratipay.com/issues/3399#issuecomment-159010969:
Okay! Inbox 6, GitHub 0, L2 Support 0, Vendors, etc. 0.
Heading home for lunch and then https://github.com/gratipay/inside.gratipay.com/issues/403.
@whit537:
What is it and what does it mean?
"Where are we going, and what am I doing in this handbasket?" :stuck_out_tongue_winking_eye:
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 https://github.com/gratipay/inside.gratipay.com/issues/402#issuecomment-158972240, although there seems to be some confusion about whether it is about GP's required competencies, or about the hard stuff GP solves)).
Call with Neal in T-10 minutes. View link will land on #403.
Big new question: should we consider trying to join forces with Enspiral? https://github.com/gratipay/inside.gratipay.com/issues/421
A little off topic - but does anyone have suggestions on some Python books? (actual books not e-books)
@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?
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. :disappointed:
Everything not on the critical path to payroll needs to take a back seat. :seat:
What is the critical path to payroll? PCI DSS → Identity Verification → Payroll
Gosh. We have to start storing SSNs. Time to grow up.
I feel as if my SSN should be the first SSN we store.
Perhaps that's not leaderly enough, though (#404, #420, #72).
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! :scream:
Conclusion: building a vault (https://github.com/gratipay/gratipay.com/issues/3504) is our highest-priority task, because it is the next step on the critical path to payroll. Objections?
I agree on that step :+1:
Also I created that repo!
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 :)
@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.
What are you working on this week and why?
last week