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

Gratipay Experiments #991

Closed
2 tasks
mattbk opened this issue Jan 20, 2017 · 11 comments
Closed
2 tasks

Gratipay Experiments #991

mattbk opened this issue Jan 20, 2017 · 11 comments

Comments

@mattbk
Copy link
Contributor

mattbk commented Jan 20, 2017

This is one of those meta-issues that may not have a way to easily close. I'm going to use it as a place to take notes.

I've mentioned this in a few issues. What works for one project may not work for another, so we should build Gratipay as a place where you can experiment with things within your project, but also see the aggregate data for what other projects are doing as well.

  • Weekly/monthly/oneoff giving
  • TWYW vs even vs random
  • Anon/not
  • donating to basic income
  • kids eat first vs. adults or smallest value first
  • if funding a bundle of projects, distribution of funds: specifically allocated vs random vs even
  • others?

Encourage projects to see what works for them, and track the data. Use to help projects fund themselves the best. This turns Gratipay into more than just a platform for receiving funding, it's a playground/lab for crowdfunders to analyze behavior.

  • what are some metrics by which success of receiving could be measured?
  • what are some metrics by which success of giving could be measured?
@chadwhitacre
Copy link
Contributor

random

😄

@chadwhitacre
Copy link
Contributor

This is one of those meta-issues that may not have a way to easily close.

Paging @techtonik! 😁

@mattbk
Copy link
Contributor Author

mattbk commented Jan 20, 2017

random

Psychology!

@chadwhitacre
Copy link
Contributor

@chadwhitacre
Copy link
Contributor

We've looked at cohort analysis in the past.

@techtonik
Copy link
Contributor

Oh, I like that. I you would allow me to bloat it a little.. =) For some reason I see it (Gratipay Experiments) as a polymer components that could be switched on and off without affecting too much of the rest of site structure.

Place each Experiment-in-the-Box with defined input data that is required from Gratipay, desired location or interface, and some docs how to turn it on and off.

I'd like to have a interface like a circle where you turn experiments on and off (checklists are boring) which will also be a voting interface. It will also answer questions like if your giving/receiving stats are public.

@techtonik
Copy link
Contributor

techtonik commented Apr 16, 2017

My experiments (legalize):

  • calculate tax for your country
  • show your status and help you validate it
  • donate to specific expenses that person registered
    • domain name
    • hosting
    • guns and drugs (a sanity test)
    • etc.?
    • isolate payment receivers to open companies? or companies with public API?

@techtonik
Copy link
Contributor

Also, experiment with money-laundering - what is money laundering and what is not, how to comply with legal requirements. Ouch.. I opened the floodgate again.. )

@mattbk
Copy link
Contributor Author

mattbk commented Apr 17, 2017

Your examples seem almost like things a project owner would run through as part of a "complete your account setup" process, to teach them dos and don'ts.

Your Experiment-in-a-Box is what I was thinking of, though. A tool that could be used to maximize income, based on the donation history available.

@mattbk
Copy link
Contributor Author

mattbk commented May 25, 2017

+1 at #969 (comment) (for giving)

This is one of those choices we could build; divide money equally among X projects, or divide it up manually.

@mattbk
Copy link
Contributor Author

mattbk commented May 25, 2017

Gratipay should be the "big data*" of OSS funding.

*Not really big data, but a large enough dataset to have fun with.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants