Charging for Free/Open Source Software

Memo to OSS developers: I can pay money for software licenses, even if the license is just “MIT, but we invoice you”, but I cannot just put business funds in your tip jar.

from an article about TarSnap, the secure backup service, and how it could be better run as a business.

This is an important insight: software can be licensed under the GNU GPL or MIT with a software fee included. This is allowed by the licenses and it makes it possible for businesses to buy your free/open source software. To developers, it’s seen as a donation to their project, but to businesses it will be seen as a justifiable business expense.Modern business concept

Personally, I’ve tried to convince previous employers that they should donate to free/open source projects that we routinely used. My justification to them was that we rely on the projects so much that the donations are essentially a business expense. Unfortunately, if it’s labeled as a donation and not as a sponsorship or as a required license fee, businesses will not see it as an expense, they’ll see it as free code that will lower costs.

My suggestion to other free/open source developers is to have either dual-licensing, where companies can pay to use a proprietary license instead of the GPL; or to have a separate page that’s meant for businesses and business leaders to check out where they are explicitly charged for the download of the software or signed up for a subscription which includes regular upgrades. Other developers, such as myself, would appreciate this too. It would be nice to say “hey we need $100 for a copy of Essential Code v1.2” instead of simply downloading the code for free and keeping the business blissfully unaware of all the software required to run the business.

Article Translations

Read the above article in other languages!

(French translation)

Ceci est une idée importante: sous la licence GNU GPL ou MIT logiciel peut être autorisé avec des frais de logiciel inclus. Cela est permis par les licences et il permet aux entreprises d’acheter votre logiciel libre / open. Pour les développeurs, il est considéré comme un don à leur projet, mais pour les entreprises, il sera considéré comme une dépense d’entreprise justifiable.

Personnellement, je l’ai essayé pour convaincre les employeurs précédents qu’ils devraient donner à des projets libres / Open Source que nous utilisons régulièrement. Ma justification pour eux était que nous nous appuyons sur les projets tant que les dons sont essentiellement une dépense d’entreprise. Malheureusement, si elle est étiqueté comme un don et non comme un parrainage ou une redevance requise, les entreprises ne verront pas comme une dépense, ils verront ce code comme libre qui permettront de réduire les coûts.

Ma suggestion à d’autres développeurs libre / open source est d’avoir soit de double licence, où les entreprises peuvent payer pour utiliser une licence propriétaire à la place de la GPL; ou d’avoir une page séparée qui est destiné aux entreprises et aux chefs d’entreprise de vérifier où ils sont explicitement facturés pour le téléchargement du logiciel ou signé pour un abonnement qui inclut les mises à jour régulières. D’autres développeurs, comme moi, aimeraient aussi. Ce serait bien de dire “hey, nous devons 100 $ pour une copie de Essential v1.2 Code” au lieu de simplement télécharger le code gratuitement et garder l’entreprise parfaitement inconscients de tous les logiciels nécessaires pour diriger l’entreprise.

(Russian translation)

Eto vazhnyy vyvod : programma mozhet byt’ pod litsenziyey GNU GPL ili MIT s platoy PO v komplekte . Eto dopuskayetsya po litsenziyam , i eto dayet vozmozhnost’ dlya biznesa, chtoby kupit’ vash besplatnyy / programmnoye obespecheniye s otkrytym iskhodnym kodom . Dlya razrabotchikov , on videl v kachestve pozhertvovaniya v ikh proyekte , no dlya biznesa eto budet rassmatrivat’sya kak opravdannoye biznes-schet.

Lichno ya pytalsya ubedit’ predydushchikh rabotodateley , chto oni dolzhny pozhertvovat’ svobodnykh / otkrytykh proyektov , kotoryye my ispol’zovali regulyarno . Moy opravdaniye dlya nikh bylo to, chto my polagayemsya na proyektakh tak mnogo, chto pozhertvovaniya , po sushchestvu, biznes-schet . K sozhaleniyu , yesli ona imeyet imya v kachestve pozhertvovaniya , a ne kak sponsorstvo ili kak neobkhodimogo litsenzionnogo sbora , predpriyatiya ne uvidite yego v kachestve raskhodov , oni budut videt’ yego kak svobodnyy kod, kotoryy pozvolit snizit’ zatraty.

Moye predlozheniye , chtoby drugiye razrabotchiki svobodnogo / otkrytogo istochnika imet’ libo dvoynoye litsenzirovaniye , gde kompanii mogut zaplatit’, chtoby ispol’zovat’ sobstvennyy litsenziyu vmesto GPL ; ili imet’ otdel’nuyu stranitsu , prednaznachen dlya predpriyatiy i biznes-liderov , chtoby proverit’ , gde oni yavno vzimayetsya dlya zagruzki programmnogo obespecheniya ili podpisalsya na podpisku , kotoraya vklyuchayet regulyarnyye obnovleniya . Drugiye razrabotchiki , takikh, kak ya , budet tsenit’ eto slishkom . Bylo by khorosho , chtoby skazat’: “Ey , my dolzhny $ 100 za kopiyu Essential Kod v1.2 ” vmesto prosto zagruziv kod besplatno i podderzhaniyu biznesa v blazhennom nevedenii vsego programmnogo obespecheniya , neobkhodimogo dlya zapuska biznesa.

(Korean translation)

이것은 중요한 통찰력이다 : 소프트웨어가 포함 된 소프트웨어 수수료the GNU GPL 또는 MIT에 따라 사용이 허가 될 수있다. 이 라이센스에 의해 허용과 기업 무료 / 오픈 소스 소프트웨어를 구입하는 것이 가능하게된다. 개발자에게, 그것은 자신의 프로젝트에 기부로 간주,하지만 기업에 그것은 정당한 사업비로 볼 수 있습니다.

개인적으로, 나는 그들이 우리가 일상적으로 사용하는 무료 / 오픈 소스 프로젝트에 기부해야한다는 이전의 고용주를 설득하기 위해 노력했습니다. 그들에게 나의 정당화는 우리가 기부금은 본질적으로a 사업비 것을 너무 많은 프로젝트에 의존하는 것이 었습니다. 이 기부금으로하지a 후원 또는a 필요한 라이센스 비용으로 분류 있다면 불행하게도, 기업은 비용으로 그것을 볼 수 없습니다, 그들은 비용을 낮출 것이다 그것을 무료 코드를 볼 수 있습니다.

다른 자유 / 오픈 소스 개발자를위한 나의 제안은 기업이 대신 GPL의 독점적 인 라이센스를 사용하기 위해 지불 할 수있는 듀얼 라이센스, 하나를 가지고있다; 또는 명시 적으로the 소프트웨어의 다운로드 요금이 부과 또는 정기적으로 업그레이드를 포함하는 서브 스크립 션에 가입 한 위치를 확인하기 위해 기업과 비즈니스 리더에 대한 의미있어 별도의 페이지를 가지고있다. 다른 개발자는 자신과 같은, 너무이 감사하겠습니다. 대신 간단하게 무료로 코드를 다운로드하고 사업을 실행하는 데 필요한 모든 소프트웨어의 행복하게 모르고 사업을 유지하는 “야 우리가 필수 코드 1.2의 사본을 $ 100 필요”말할 필요도 좋을 것이다.

(Serbian translation)

Ovo je važan uvid : softver može biti licenciran pod GNU GPL ili MIT sa softverskim naknadu uključen . To je dozvoljeno dozvola i omogućava preduzećima da kupite free / open source softvera . Programerima , to vidi kao donaciju njihov projekat , ali da preduzeća će se posmatrati kao opravdanog trošak poslovanja.

Lično , ja sam pokušao da ubedi prethodnih poslodavaca da bi trebalo da doniraju free / open source projekata koje smo rutinski koristili . Moj opravdanje im je da se oslanjamo na projektima toliko da su donacije u suštini poslovni trošak . Na žalost , ako je označen kao donaciju , a ne kao sponzorstvo ili naknade za licencu potrebna , kompanije neće videti kao trošak , videće ga kao slobodni kod koji će smanjiti troškove.

Moj predlog za druge slobodan / open source programere je da ima ili dual – licenciranje , gde kompanije mogu da plati da koriste vlasnički licencu umesto GPL ; ili da ima posebnu stranu koja je značilo za preduzeća i poslovne lidere da proverite gde se izričito terete za preuzimanje softvera ili prijavili za upis koji uključuje redovne nadogradnje . Drugi programeri , kao što su mene , da cenim ovo previše . Bilo bi lepo da kaže ” hej trebamo $ 100 za kopiju esencijalnih zakonik v1.2 ” umesto jednostavno preuzimanjem kod besplatno i čuvanje poslovanje u blaženom neznanju svih softvera potrebnog za pokretanje poslovanja.

Advertisements

One thought on “Charging for Free/Open Source Software

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s