FreedomSponsors is a crowdfunding platform for programming tasks of Free and Open Source Software.
You can place money bounties for issues that you care about getting fixed, and you can collect bounties by working on open issues.
The main difference is that we are focused on helping the Open Source and Free Software community.
But we believe that what really makes us unique is that we have a strong philosophy based on openness and freedom.
That philosophy means we put the community first in everything we do. Here's a few examples:
We want to build a community based on trust and reputation. Sponsors only have to pay their bounty after the developer resolves the issue (but you can choose to pay before, if you wish.)
We want to be the change we wish to see in the world. We're "open everything", so everything we do is out in the open: Check out our website statistics, browse our blog, and see the way we handle all feedback. It has a lot in common with the "open company" concept pioneered by our friends at Gittip.
Yes. Honestly, we do.
We believe that there are enough decent, honest people in the world for this to work.
A wise guy once said, stay foolish. We intend to do just that.
Have you heard of the Agile Manifesto? FreedomSponsors is all about taking the third Agile principle to its ultimate consequence: "Customer collaboration over contract negotiation."
We want to give people the ability to push forwards the projects they love. No contracts, just trust that developers also love these projects too, and feel happy when they can be paid to put more work into them.
Gravatar is a nice and simple online service that will let you upload avatar pictures and associate them with an email address.
For example, the email firstname.lastname@example.org is linked to this image.
So create your Gravatar account and associate an avatar to the email you use here.
Like eBay, you should check out their profile and take a look at their history. If there are a lot of unpaid offers on resolved issues, that's a bad sign.
Yes, but later (that's the way clever people say no).
We just display the user history attached to a profile. But we intend to have something more sophisticated in the future.
Actually you just pay each developer directly.
Our purpose is to do business in public. We don't show your email address, but everything that you do here (making an offer, saying you'll work on an issue, all your comments) is public for the world to see.
Payments can be made either in USD via Paypal, or in Bitcoins
If you don't have a Paypal account, setting up one is very easy and you can do it when you're making your first payment.
Setting up a bitcoin wallet is also very easy, see "What is Bitcoin?".
Before you can receive payments, we recommend you have both a Paypal account and a Bitcoin address so you can accept all offers. We check that each Paypal account is valid before allowing anyone to make a payment to it.
FreedomSponsors charges a 3% fee on top of offers, regardless of the payment method. We clearly state this on each payment page. To keep things simple, we use Paypal’s Parallel payment type, so a single payment is sent to two or more receivers.
For example, when you want to pay a US$ 100 bounty, you may decide to give US$ 50 each to 2 developers. On Paypal’s website, you will see:
Bitcoin has no “parallel payment.” Instead, you send us, we verify the transaction, keep 3%, and transfer the rest to the developer(s) being paid.
To be able to receive payments, you’ll need to set up one of these options on your profile page.
If you're sponsoring issues, you don't need that until right before making your payment. If you made an offer in USD and you don't have a Paypal account, you'll be prompted to setup one when you're making your first payment (and it's very easy to do so).
If you don't know what Bitcoin is, you should! This short video (1m44s) does an excellent job explaining it.
If you still don’t have a Bitcoin Wallet, it’s really easy to set up one – and it’s free. You can either host your wallet on your computer using a Bitcoin client, or you can create a wallet online in a web wallet provider. Take a look at this link to learn more about those options: http://bitcoin.org/en/choose-your-wallet
First, verify that the issue is really solved. It's perfectly OK to pay only after your problem is really fixed.
Then you have to decide whether you'll pay developer A, developer B, or both. To make a fair choice, do a little digging and check out the original issue to see how it went down.
Maybe one person submitted a pull request for a bugfix, and another person had to rework it and then merged it. If so, they both deserve some thanks, and your money. You decide how much you pay to whom. The choice is yours.
Ideally, there should be no "independent developers". The best way for a developer to contribute to an open source project is to actually get involved with the corresponding community.
In most cases, it is also a bad thing for the end user (meaning, the sponsor) if the work is done on a branch, or a fork of the main codebase, because then the user would not benefit from new improvements that eventually get added in the future.
The "Sponsor issue" form has a "No Forking" checkbox as part of the acceptance criteria. By checking it, the sponsor is telling that only solutions that are implemented on the main project's codebase will be accepted.
We want to encourage sponsors to actually fund the original projects, so that checkbox comes checked by default.
Normally we have an atmosphere of gratitude and collaboration among sponsors and developers. However we do know that conflict situations may come up.
Try to resolve conflict with compassion. An excellent book that explains how to do this is Marshall Rosenberg's "Non-Violent Communication: A Language of Life".
Simply, tell them how you feel without judging them or evaluating the situation, then request a description of what their ideal situation is, and ask for suggestion about how to get there.
If you feel upset, and judge the sponsor as not trustworthy, remember that the issue - and its comment history - will be publicly linked to the sponsor's account. If you feel unhappy, we suggest you go to sleep before posting anything you might later regret.
Yes. When you start working on an issue, simply check the “start accepting payments” box, and kindly ask your patrons to pay you.
We recommend only doing this when you're confident that you will be able to complete the issue. If you think the total payment should be higher, track down some other users who suffer from this issue and ask them to check it out on FreedomSponsors.
Normally you have to wait until the developer has marked the issue as “DONE”.
However you can do this when the issue is “IN_PROGRESS” and the developer has indicated that they wish to start accepting payments. But remember that it's ok to wait until the issue is finished before you pay the developer.
We encourage you to only pay beforehand to developers you know you can trust!
Politely ask for a refund — from the developer. We cannot refund you because payments are made directly to developers.
(This is why we encourage to only pay beforehand to developers you know you can trust.)
Calleri Informática is the legal entity behind FreedomSponsors.
Address:Rua Araçuaí, 89, Bosque dos Eucaliptos.>São José dos Campos - São Paulo - Brazil.
Phone numbers:+55 12 39371638 / +55 12 81440013
We've also had a lot of help from awesome people who love libre, to whom we are all deeply grateful
Our favorite designer and front-end developer.
#1 in pull requests.
Always provides great advice.
Heavy user and great feedback.
Heavy contributor to the Django codebase.
You are keen! Here are 3 simple ways to get stuck in:
We need all kinds of help, not just coding. Check out our README file's section on Helping out.
If you don't know what a Github is, but you found an issue with our website or have any suggestion or comment at all, we want to hear from you! Drop your thoughts on our feedback section.
If you do know what Github is, log in and create a new issue on our repo. Write what you wish to be better and we'll hop to it.
(If you don't know what a Github is but want to find out, spend 15 fun minutes on try.github.io)