On Wed, May 30, 2012 at 9:17 PM, Michael Snoyman <
mic...@snoyman.com> wrote:
> This actually brought up two difficult questions for me: how should
> Yesod collect donations, and what should we do with the money? For
> now, I asked Jean-Christopher to send the donation to my personal
> Paypal account, though long term I'm sure there are better options. Is
> anyone familiar with how other open source projects deal with this?
There are (1) vendor-controlled projects, (2) projects that set up
their own organizational entity, (3) projects that join an entity set
up to be a legal and financial home for open source projects, and (4)
projects that don't bother as they don't take donations at all, or
where it is appropriate for donations to go to single developers.
I'd guess (3) is appropriate. Haskell.org recently did this, joining
Software in the Public Interest --
http://www.spi-inc.org/projects/haskell/ -- given that maybe (3') is
seeing if the
http://www.haskell.org/haskellwiki/Haskell.org_committee
which I know nothing about would want to take on "determining how
haskell.org funds are spent" for funds donated to Haskell projects.
Besides SPI, the obvious entities to look at are Software Freedom
Conservancy and Apache. SFC provides a few more services than SPI, see
http://www.spi-inc.org/projects/services/ and
http://sfconservancy.org/members/services/ while Apache of course
provides a lot and requires buying into various Apache processes. I'm
on the committee for SFC that evaluates project applications so
obviously I endorse that route, but SPI may be better if the only real
need is someplace to handle money.
> The other question is: how should we use this money? The only expense
> the project really has is a pittance to EC2 for hosting each month. A
> few months ago, I would have said we could hire a professional
> designer to clean up my horrible site design, but Luite already
> addressed that.
I think some common uses in addition to paying for hosting are
sponsoring developer travel to conferences, community event expenses,
paying developers to fix specific bugs or complete specific features,
and with lots more money, paying some of the core team to work full
time on the project.
Mike