New UI for Github Organizations

[jeresig]

Make it so that you can give one amount to an organization and have it be split amongst multiple people.

This would be a cosmetic change for the organization page (removing all the buttons for the individual contributors and replacing it with one large input that's hooked to each user).

[logo] jQuery
       Has 3 public members

Give to [Name]: [  3.00]/week [GIVE]

Note: You're giving money to a number of individuals, all of which are
listed below. You're not giving money directly to the organization
associated with this Github account. Feel free to add more tips to any
individuals, or remove any tips, to match your desired contribution.

On Gittip:
- jeresig [ 1.00]/week
- wycats  [ 1.00]/week

Not on Gittip:
- somedude [ 1.00]/week

Whenever the value changes in the top input all the user text inputs should update automatically (splitting evenly amongst all the users).

If a user's text input is updated by hand then the amount in the top input should update as well.

Note that there should be a single "GIVE" button at the top to make it obvious that when you click submit you're giving that much money to all those different people.

(I'm not a member of the gittip project yet but you can feel free to assign this to me, I can implement it.)

[chadwhitacre]

(I'm not a member of the gittip project yet but you can feel free to assign this to me, I can implement it.)

@jeresig May I add you to the Gittip org as a collaborator with perms on the www.gittip.com repo?

[jeresig]

@whit537 Sure thing, thanks!

[chadwhitacre]

Done. Welcome aboard! :)

[chadwhitacre]

Okay, let's sort this out. I want to use the funds for this (#449).

If you want to do a Hangout or IRC let me know. Otherwise I'm going to do a brain dump here.

[jeresig]

Feel free to do a brain dump - although I probably won't be able to do a hangout/IRC until Thursday evening. I'll watch this thread and chime in wherever I can!

[chadwhitacre]

"Funds" belong to "participants" and are simple key/value mappings where the keys are other participants and the values are the percentages to split money given to the fund. Funds can be nested and we are able to compute the steady state of the graph during payday so money poured in the top of one fund ends up split properly taking nesting into account.

[chadwhitacre]

From a UX perspective I'm worried about people ending up with tons and tons of small gifts to many people and they don't remember who they are or why they tipped them. Funds gives some hope of keeping that straight for users.

[chadwhitacre]

(I already have the problem of wondering why I have someone in my list of receivers. See also #222 and #759.)

[chadwhitacre]

This blog post captures my thinking pretty concisely, btw:

http://whit537.org/2013/01/disappointed-with-gittip.html

[chadwhitacre]

Right, so then a "bulk giving" page (#880) would result in a "fund".

[chadwhitacre]

The idea is to make these funds publishable so I can give to @jeresig's "jQuery" fund and I don't have to know all the people involved. I can trust his judgement. The top few people in each project/community would have public funds, so I can pick between @jeresig's jQuery fund and @wycats' jQuery fund, which in all probability are both included in the other (again, we have the algorithm for resolving these circular references).

[chadwhitacre]

So what am I saying?

[chadwhitacre]

I'm saying that "funds" are the abstraction underlying several user experiences:

• giving to the contributors to a repo
• giving to the collaborators on an org
• giving to the maintainers of an npm module

Basically any place where we need to aggregate individuals into groups and give to them collectively, we should use a fund.

[chadwhitacre]

One design requirement here is to be able to set up funds for projects without waiting for the projects themselves to join Gittip. So that's fine. Worst-case scenario we can keep funds private to a user, and make them publishable down the line.

[chadwhitacre]

I believe the use case for this is solved with Teams, especially now that you can link a GitHub org to a Gittip account (#871).