-
Notifications
You must be signed in to change notification settings - Fork 308
Receiving payments in new version unclear #3556
Comments
@whit537 It just occured to me for the first time that during "gratipocalypse", it was not only that we weren't getting paid. It was that the money was not accumulating on our accounts. |
@dcht00 I'm sorry. :-( |
@thomasdavis Hi! Thanks! :-)
Sorry for the confusion. :-/
Yeah, sorry, we need to bring the giving/receiving numbers (reticketed as #3560) and the history page (+1 added to #3455) up to speed. P.S. You can see how we're prioritizing things on our weekly Radar tickets. Here's this week's. At our current velocity I estimate we'll get to these issues in three weeks or so (PRs always welcome, of course).
Yes! I am seeing that the JSON Resume team is owned by ~thomasdavis (not ~jsonresume), and I do see payouts on the history page there. No? We're starting to talk at #3399 (comment) about cleaning up the team/owner/member ontology in Gratipay 2.1. |
@thomasdavis, this doesn't directly address your question, but might help clarify some things. There are now team pages and individual pages, something I hadn't understood until I read the linked comment. Apparently, all the individual payments sent and received before Gratipocalypse are still there on the individual page. I don't see any way to check these on the team page (even my own, to which I theoretically should have access). Example: To give credit where it is due, this blog post attempts to explain things, but the UI on the website doesn't make it easy to follow. Possible related tickets (to create if none related exist):
|
Thanks @mattbk that helps! So my main questions are:
|
+1 from https://gratipay.freshdesk.com/helpdesk/tickets/2450, added to Notify at top of ticket. |
So, @mattbk let's try to condense what we want to work on I suppose. My thoughts are:
I also feel like this could be talked about more here:
Also! Created an updated FAQ - or even a "Getting Started with Gratipay 2.0" would be nice. It would probably eliminate a lot of these PR's otherwise. |
@thomasdavis @mattbk @kzisme What if we link PayPal payout routes directly to Teams? Would that help us get rid of the confusing user(owner)/Team distinction? |
@whit537 @thomasdavis @mattbk How are payouts currently linked to teams? My current thinking is that:
I just connected my individual Gratipay account with Github and joined the Gratipay community, so I guess a distinction should be made between Teams/communities as well. |
It seems as though within each team they can choose how they want to 'Share their revenue'. Also how close are we to working out #3433? |
All money goes to an Owner, which is a ~user account (i.e., a record in the Team and Individual keeps coming up as a distinction. It's not the right one. The distinction we want to make is between:
The opposite of Team is Individual, so that's confusing. What's a better pair of terms to use here? |
Not close. :-( I see us spending the next month or two a) cleaning up bugs to bring Gratipay back up to beta quality, and b) dealing with escrow (#1383, #3539). Not until we have that stuff cleaned up can we even start on the hard work it will take to bring back payroll. Honestly? It could be a year. |
@whit537 Suggest "Entity" and "Member". Rationale
However, there is another type of Entity not mentioned: the loose Association of developers who contribute work to a FOSS project. The Association lacks any legal status, as well as the resources to attain legal status (no Social Security Number, Employer Identification Number, Articles of Incorporation, Bylaws, bank account, business license, etc.). PayPal can and does freeze assets for such Associations. Maybe an Association is an Entity, or it doesn't fit the Gratipay model, or something else? For these reasons, for my specific Entity, KnopProject, and its Owner ~KnopProject, I do not wish to create a new PayPal account. |
@stevepiercy Good comments, especially concerning PayPal's specific rules. As I understand it right now (because no payroll), the function of Teams is to funnel money to Owners, who are then responsible for disbursing it. The reason I bring up the Team/~user distinction is because that's the way it is set up right now--there is a specific page for each, so they appear as different classes of entities to any random person online. What I would like to see is a slight revamp of the ~user page (or general treatment of ~users in copy) that clarifies what is happening. "This is a ~user profile. He or she is paid for work on these teams [x, y, z], so please support him/her there." I understand that I'm hamstrung by knowing how things used to work, but on a site that is "a way to give money every week to people and teams you believe in," it's confusing to not be able to give money to a person, especially when I can see a profile that may still (post 1.0) explain what this person is doing and where contributions will be used. |
I looked all over the UI for a way to add Members/Owners to the Team, but found none. How can I do this? I cannot add my own ~user StevePiercy to the Team KnopProject. This also means I also have no way to disburse any funds, even if I had any to disburse.
It is my understanding that we do not give money to individuals anymore nor in the future. Even in history, people gave money for my work (what I do), not me as an individual (who I am).
As an aside, "belief" ruffles my feathers. I think Gratipay is a way to show gratitude for the work that people and teams produce by giving money every week. "Belief" has religious connotations for me. |
I think this is a function of #3433. |
This may merit a different ticket (because it's about pay_outs_, not pay_ments_), but it also looks like no tips are moved if there it not a valid payout (=transfer out of Gratipay) method available. At this time the only option for payouts is PayPal. All of these misunderstandings are interconnected.
This seems like a situation where escrow would be good to have (see additional discussion at #1383), but there is no telling when (if ever) ~Bob will add a payout method. In any case, the above behavior is something that needs to be (one of below)
|
This is an important paragraph. I feel as if we're standing at the edge of a cliff, gazing across and wondering how we will ever traverse it. The gulf is between the FOSS community's soft understanding of what a project entails—a "loose Association" as @stevepiercy ably describes it—and the hard understanding of what a corporation or organization is under the law. Gratipay 2.0 is about bridging that gap. Our asymptote is a Stripe-like "company as a service" abstraction. That's a 💩-ton of work, however, and we're triply bootstrapping. We're going to be slow getting there. Good thing you're patient, @stevepiercy. :-) |
@thomasdavis Thanks for your patience as we clean this all up. We now have a fresh visual design, rewritten About pages, and correct giving/receiving numbers on Team and ~user pages: Does this help address your issue? What else do we need on this ticket before we can close it? |
Sorry, linked to the wrong Team page. :-) https://gratipay.com/json-resume/ |
Gonna go ahead and call this one good. If something is still unclear feel free to say so, @thomasdavis! :-) |
Hi there, thanks for all the great work guys.
I couldn't quite deduce how the new system works.
On my organizations profile (https://gratipay.com/~jsonresume/) it says it receives xx per week. But when I look at the history tab, it says it hasn't received anything since April.
Have payments commenced since the switch?
Do the people who were originally donating have to sign up under the new system?
Notify
The text was updated successfully, but these errors were encountered: