#2 Hosting/cloudiness?
#3 Administration?
#4 Custom adaptation?
#5 Privileged early access to updates/content files?
All those different strategies has been used to "sell" GPL software. Even the last one has been used, even if their customers could repackage the update and redistribute it to non-paying customers.
Then there's the recent example of Openshot, a GPL licenced video editor where the author went to kickstarter to gain funding for improving it greatly, the goal was $20.000 and it reached $45,028.
I see a combination of these models as a future popular way of making money out of your open source efforts.
Dual-licensing effectively says, "We'll let you take away user freedoms, but only if you pay the original copyright holders." Which is akin to openly bribing communist party officials.
Kickstarter projects is USA specific, and it seldom works if you need a steady income of money.
As for steady income of money, true that this type of funding isn't of the steady pay-check variety but if you can continue to add value to your project then it could become a long term income.
Either way I'd say the vast majority of open source desktop software today is done without any compensation and during developers spare-time, things like kickstarter opens up possibilities for them to actually make money while doing what they would likely have done either way, and it can also give them the financial opportunity to work exclusively on the project for a period of time.
Quoting from the VideoLAN web site, > x264 is a free software library and application
That is a developer tool on my language.
The possibility of a dual licence gives the creator a compensation because he waives the rights the GPL gives him for you.
Also: Support contracts. A lot of poeple live in the support ecosystem and adapt GPL/BSD software for costumers.
Fixed:
If you use ANY GPL code in your product you have to provide the source.(There are of course exeptions eg LGPL)
Also it isn't simply derivative work that that can be forced to re-license under the GPLv3. If FreeBSD had elected to adopt a GPLv3 compiler and distribute the source(as they do with the compiler) then the FreeBSD kernel itself would become subject to it. In fact, it isn't just gcc which has this restriction. Any GPL v3 code isn't allowed in base.
Further reading:
http://www.freebsdfoundation.org/press/2007Aug-newsletter.sh...
The GCC 'runtime library exception' firewalls all 'target code' from the GPLv3, and even allows proprietary preprocessors, linkers and assemblers (but nothing that would involve modifying GCC to split what it does in to more granular stages)
You have to license any code that links with GPL code under the GPL. This does not prevent you from dual-licensing your own portion of the code base, or shipping non-GPL, non-linked code as part of the same product (Although in the case of things like DLL plugins it gets a bit hazy)
Actually, that's a common, but wrong interpretation. The whole work becomes GPL, but the code that links to GPL code doesn't have to be GPL.