My fiscal responcibility to my company ver. Open Source - advice please

Wil McGilvery wmcgilvery-6d3DWWOeJtE at public.gmane.org
Thu May 13 17:15:00 UTC 2004


I think the answer is as varied as the programs being offered that are built on Open Source.

Just take a look around, there are hundreds of free GPL programs. Some are very good, some are horrible. There are also numerous proprietary solutions available that use Open Source tools and they still charge a fee. 

There also companies that offer both solutions. One is a "lite" version for free and another is a full blown version at a cost.

I think your company should do what is best for your company. You can always give back to the community after you have eaten :)

Other things to consider:

1) Maintenance and Support
2) Personal vs Commercial
3) Is this your main focus for your company or is it an offshoot.
4) If you go open source how will you pay your bills?




Regards,

Wil McGilvery
Manager
Lynch Digital Media Inc

         

416-744-7949
416-716-3964 (cell)
1-866-314-4678
416-744-0406  FAX
www.LynchDigital.com


-----Original Message-----
From: owner-tlug-lxSQFCZeNF4 at public.gmane.org [mailto:owner-tlug-lxSQFCZeNF4 at public.gmane.org] On Behalf Of Madison Kelly
Sent: Thursday, May 13, 2004 12:49 PM
To: tlug-lxSQFCZeNF4 at public.gmane.org
Subject: [TLUG]: My fiscal responcibility to my company ver. Open Source - advice please

Hi all,

   I am in the middle of my biggest dilema since starting to work in the 
Linux community professionally. I need your guys' advice on how I should 
go about this.

   I have been asked to write a program which I think, when done, will 
have an honest benefit to the community. Now, I was able to write it 
because my boss paid my hourly wage to write it so the program belongs 
to the company. The question is how to release it.

   Obviously my boss has made a decent investment in developing the 
program and wants to see a return (hell, the company needs money to 
survive, economics 101) and so they want to release the program closed 
source. The other issue is that this will be one thing we can offer our 
clients that no one else can offer. They worry (fairly) that if the 
program is made freely available under the GPL that we would lose our 
advantage.

   I understand their economic concerns and they are valid (this is 
certainly -not- a case of greed, we're a new startup and it's about 
keeping the company afloat). My worry though is that we are 
Linux-centric and if we don't contribute back to the community that we 
are based on we will be seen as trying to ride the wave of the new open 
source model while holding onto the old proprietary business model and 
lose respect amoung our clients. From what I can tell anyone who uses 
Linux has a political view on it.

   So, I have been arguing strongly to release to program open source. 
The boss and marketting guy wants to release it closed so that we can 
recoupe the investment they made and feed the company. Am I 
misunderstanding the Linux community? I don't want to go into the debate 
and push full out for an open source release if it hurts the company I 
work for but I also want to give back to the community that has helped 
me so often.

   On the legal side: our program calls GPL'ed programs but the actual 
program is cleanly our code.

   What have you guys done? Have you release open-sourced programs and 
still made a profit? How do most business customers react when they know 
that they -could- get the program for free? Do they still buy it from 
you anyway to ensure proper support? Do you lose work to others who took 
your app and sold it? All your advice is greatly appreciated!

Madison

--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml


--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml





More information about the Legacy mailing list