Skip to main content

Don't bank on open source backing

There's a bunch of websites that let you become a backer of open source software or back an issue. In my opinion trying to get "funding" from these is a complete a waste of time and effort. Generally speaking, the providers of these services and only a small portion of the users benefit and make any the money. Lets look at a few numbers to see why.

OpenCollective 

Url - https://opencollective.com/opensource
Fee - 5%



On their home page you see the estimated annual budget, currently at $525k / year and 309 projects.  Wow $525k! But wait, scroll down to the collectives and you see webpack is getting about HALF of that ($241k). So do the math if we exclude the outlier (webpack) the average project makes a whopping  $920 per year or about $80/month.  The average US engineer will make that monthly amount in about 1-2 hours. Most of these open source projects I'm sure have several hundred ours of work behind them. It just doesn't make sense. Oh and I forgot to mention that nearly 50% of the "collectives" make $0/year.

Meanwhile, OpenCollective is making ~$10k/year in fees (assuming the payment processor takes 3%).

BountySource

Url - https://www.bountysource.com/
Fee - 10%



Bountysource lets you "back" a particular issue of a git project. Cool idea, however I see a few projects that misuse this where the owners simply post a bountysource link for every issue on the project and don't even reply (ie a few of the kivy projects) to issues unless they post a bounty. I kind of get it, time is money, but seriously? Way to slap potential users face and turn them away from a project. Anyways, let's see how bountysource adds up.

If you sum up the totals of that "All" time bounty hunters you currently get $303k. It's been around since 2012 so that's  about, hold your breath, $60k/year for the TOP 30 developers so average $2k/year (again a few outliers here skewing this) so it doesn't seem too bad.

However, if you go into their stats (which is good they post!) then we see there's been roughly ~3500 active developers (less than half of which never return to the site year to year) over the past 4 years and the sum of all the paid out bounties since Q1 2013 is about $478k or about $120k/year meaning the average developer is earning, wait for it about $34/year lol.

Meanwhile, BountySource is making ~$9k/year in fees (again assuming the payment processor takes 3%).

So what did we learn here?

In short, don't quit your day job. While these services may work depending on your project, a large majority of the time they're worth nothing to the developer(s) of a project. Don't get your hopes up with sites like these (that's not to say don't use them), just plan to get funding or sales through other means. 

They might be a way to get some money on the side if the project is something you have to build anyways!

Feel free to comment with any better alternatives that may be out there!






Comments

Popular posts from this blog

A look at Chaquopy the Python SDK for Android

I recently heard about chaquopy - A "Python SDK for Android" and was really excited. There's already a demo app on the Play store for python 2 and python 3. As the author of enaml-native , I had to take a look to see how others are trying to tackle the python on android challenge.  So here's a short review and discussion of my initial thoughts on chaquopy. Demo I encourage you to try out the demo yourself to get a feel for it, but here's a short demo of what it does. Initial thoughts. It starts reasonably fast (about 3-4 seconds on my phone).  There's a noticeable delay when starting the python activity on my phone (much smoother on the emulator), but other than that the widgets look great and interaction is smooth! The apk is 11.54 MB and the app is only 18 MB installed (21MB if you include the cache), which is very good for bundling python! Also, the build process was a piece of cake!  I cloned the repo, opened in android studio, pressed play,

Kivy vs React-Native for building cross platform mobile apps

I've built three apps now using Kivy and one with React-Native, just wanted to share my thoughts on both. Just a warning, I am strongly biased towards python and this is all based on opinion and experience and is thus worth what you pay for it. I don't claim to be an expert in either of these, just have worked with each for several months.  If something is incorrect I'd love to hear advice. Kivy Demo of one of the apps Pros: Nice to be able to run natively on the desktop WITHOUT a simulator Python is easy to work with Use (almost) any python library Very easy to create custom widgets Kivy properties and data binding just work. Way nicer than React's "state" / flux / redux whatever you want to call it (stupid?).  Native interfaces (pyjnius) and (pyobjc) Runs and feels pretty smooth Cons: Default widget toolkit looks like Android 4.4. Requiring you use your own widgets or a theming kit like KivyMD  if styling bothers you Creating dy

Control Systems in Python - Part 1 - Bode and Step Response

I hate matlab with passion, yet sadly, nearly everyone uses it.  I'm a fan of Python and open source stuff so here's a simple article on how to do some common control systems stuff in Python. First we need to make sure the environment is setup. Install IPython (or you can use any other python shell, but a unicode supported shell is preferred) Install python-control (numpy, scipy) Install sympy These should do if your on Ubuntu/debian: sudo apt - get install python - sympy python-numpy python-scipy python-matplotlib ipython Then you need to install python control, see How to download and install python-control Intro to using Sympy Open ipython and run the following: import sympy from sympy import * sympy.init_printing() s = Symbol('s') Now we can do things like define transfer functions using the symbolic variable s. We can expand the bottom using the .simplify() method and we can do something more complex like... which is really nice because it