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

Radar 42 #472

Closed
chadwhitacre opened this issue Jan 18, 2016 · 20 comments
Closed

Radar 42 #472

chadwhitacre opened this issue Jan 18, 2016 · 20 comments

Comments

@chadwhitacre
Copy link
Contributor

What are you working on this week and why?

last week

@chadwhitacre
Copy link
Contributor Author

Roadmap (what?)

Embarrassments:
Milestones
Long Term

Color code:

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

roadmap

@chadwhitacre chadwhitacre mentioned this issue Jan 18, 2016
@chadwhitacre
Copy link
Contributor Author

Inbox 5, GitHub 0, L2 Support 0, Vendors, etc. 0.

@chadwhitacre
Copy link
Contributor Author

Pretty skimpy info re: #462 (comment). Sending the book back.

the big bro

picture credits

@chadwhitacre
Copy link
Contributor Author

Here's another project using Aspen!

https://github.com/falstaff84/acdr

:-)

@chadwhitacre
Copy link
Contributor Author

In turn, banks are starting to properly deal with payment aggregators, which were previously ignored if you were too small, protected if you were generating enough revenue, or shut down if you were in the awkward middle ground. Back then aggregators weren’t required to collect KYC and AML info because they were largely unregulated. They should have been collecting it, but no one was making them do it.

http://jkwade.me/post/128191359172/underwriting-marketplace-merchants

Sounds about right. 😥

@chadwhitacre
Copy link
Contributor Author

Teams reviewed.

@mattbk
Copy link
Contributor

mattbk commented Jan 21, 2016

We're increasing the number of teams, but ~users who give is remaining pretty flat. What can we do to improve that?

  • Gain new ~users
  • Encourage old ~users who were receiving to convert to teams
  • ?

@mattbk
Copy link
Contributor

mattbk commented Jan 21, 2016

On a related note, https://gratipay.com/~visionmedia is a prime example of a "team of one" who was getting lots of support under Gratipay 1.0.

@chadwhitacre
Copy link
Contributor Author

Alright! Looks like @rohitpaulk just brough his first complete payday in for a landing (#477). Woo-hoo! !m @rohitpaulk. ✈️ Meanwhile, I've been processing some awesome work from @jaraco on Aspen (and Mongs). !m @jaraco

My goals for the afternoon are to draft something on #457 (deadline is this weekend), and to get escrow to show up on the income statement over on gratipay/finances#1. @kaguillera has started on 2012-07. We are on track to have one or both months landed ahead of meeting with the CPA in a week (#285).

@chadwhitacre
Copy link
Contributor Author

It's gonna be huge to have an accounting system in place. We'll be able to approach our next growth curve with much more confidence, knowing exactly where we stand. We'll have a clear way to add new payin and payout routes such as Dwolla and Transpay without feeling like we're getting in over our heads ... same for potential modifications such as monthly and one-off payments. It ain't flashy, but proper accounting is vital to Gratipay's success. 📈

@rohitpaulk
Copy link
Contributor

It ain't flashy, but proper accounting is vital to Gratipay's success.

👍

@chadwhitacre
Copy link
Contributor Author

We're increasing the number of teams, but ~users who give is remaining pretty flat. What can we do to improve that?

The basic answer is the same as always: a) improve the product and b) tell people about it. I think you're right that the fuzzy ~user/Team distinction probably slows a lot of people down, for example.

@mattbk
Copy link
Contributor

mattbk commented Jan 21, 2016

Would adding a call to action special note on ~users without teams pages help (perhaps once we make the pages distinct)?

"This user is not on any teams, but if they're doing something cool and you want to give to them, why not tag them on social media and ask them to start a team?"

Sort of like the old way where you could give to people before they had an account (caught the mention of that in the call on Tuesday; didn't realize it had been dropped). CTA could be something like we have here: https://gratipay.com/on/twitter/realdonaldtrump/.

@chadwhitacre
Copy link
Contributor Author

Would adding a call to action special note on ~users without teams pages help

Sounds good to me.

@chadwhitacre
Copy link
Contributor Author

I'm cutting a release and I'm not sure I got the 1937 tag from the remote as I would've expected when updating. Not sure what's going on and I'm back on track now, chalking it up to "something to keep an eye out for in the future."

@chadwhitacre
Copy link
Contributor Author

@kzisme
Copy link

kzisme commented Jan 22, 2016

Awesome work everyone 🎯

@chadwhitacre
Copy link
Contributor Author

Thanks @kzisme! :-)

@techtonik
Copy link
Contributor

We're increasing the number of teams, but ~users who give is remaining pretty flat. What can we do to improve that?

The biggest incentive for me to use Gratipay was to redistribute the $$$ I earned to other open source projects. Now that I don't have anything incoming, it is kind of useless to me.

Also, for the past week I did a Roundup release and earned 500 EUR. To receive the money I had to create invoice, or make an agreement for the scope of work, send bank details and receive payment. But I can't do this twice a year, because I don't have legal entity. I can receive money only as a gift, which is what original Gratipay is proposed. So I am still interested - can I still receive gifts from people sent by Gratipay LLC.? On my side it is somewhat clear that I can, but what about the sender?

@chadwhitacre
Copy link
Contributor Author

Email (what?)

screen shot 2016-01-26 at 12 04 37 pm

@chadwhitacre chadwhitacre mentioned this issue Feb 15, 2016
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