<html dir="ltr"><head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta content="MSHTML 6.00.6000.16809" name="GENERATOR">
<style title="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body ocsi="x">
<div dir="ltr"><font face="Tahoma" color="#000000" size="2">As someone mentioned it depends on the license of that project. If it is a permissive license you can certainly fork and build your own product....open or proprietary.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">If it is GPL or any other strong copyleft you cannot unless you can secure the commercial rights for that software in Japan. Many abandoned projects were written by one or two individuals. It may be possible to
purchase it from them but otherwise option a) doesn't really exist. You must release source to your customer, and they can use anyone for support and even redistribute both source and binary to your competitors.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">I would do the following without knowing the license:</font></div>
<ul dir="ltr" style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">
<li>
<div><font face="tahoma" size="2">Figure out the costs for modifications and translation. Double it because you're likely wrong. There may be no savings vs just buying the proprietary product.</font></div>
</li><li>
<div><font face="tahoma" size="2">Figure out the costs for just writing from scratch because modifying poorly documented and haphazardly written source will take as long, if not longer, to make usable and leave you with a bad foundation anyway.</font></div>
</li></ul>
<div dir="ltr"><font face="tahoma" size="2">Compare potential revenue stream of your new product (you may have to assume only cost savings vs buying the proprietary product times the total number of installs you make...outside sales may be zero...) against
simply providing support for a proprietary system you install. Do not neglect the usual analysis of opportunity costs of what else you could be doing with your coding resources instead of hacking someone else's buggy code into something useful for your customers.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">Make sure this is purely a business decision and not something else. It is, after all, YOUR job on the line and not some abstraction. Small companies don't often have a lot of margin for big errors.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">Is there middle ground/alternatives? Maybe...it all depends on that initial license or whether you write it yourself.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div id="divRpF862606" style="DIRECTION: ltr">
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> Alberto Lepe [dev@alepe.com]<br>
<b>Sent:</b> Thursday, March 05, 2009 4:14 AM<br>
<b>To:</b> license-discuss@opensource.org<br>
<b>Subject:</b> What do you recommend?<br>
</font><br>
</div>
<div></div>
<div>Hello everyone, (sorry for my English)<br>
<br>
I work for a small company in Japan.<br>
<br>
My boss asked me to buy a proprietary system and set up it for one of our customers.<br>
I develop in Linux and I use open source software, so I recommend my boss to go for an open source alternative and save some money.<br>
<br>
However I didn't find any OSS that fit our requirements. The closest I found requires many modifications and even translation to Japanese, other thing is that its lacking of community support and there is almost no activity in their forums.
<br>
<br>
I was thinking that we (our company) could take that project and perform all required modifications.<br>
<br>
So, my questions are:<br>
<br>
1. Can we sell that system as ours without having licensing problems? I personally would like to notify it to the OSS project owner and specify that our system was based in that OSS.<br>
<br>
2. Because we are planning to perform many modifications (which may loose any compatibility with the original code), what it would be better:<br>
a) Create our own branch of the system and sell a license that will include support?<br>
b) Contribute to the OSS project and only sell support in Japan?<br>
<br>
If we go with b), I'm aware that the product itself will improve and many more people will be more interested in it, which can help us to improve our popularity.<br>
However, any other Japanese company (with more resources) could get in, at any time, and sell the support taking us out of that bussiness...<br>
<br>
If we go with a) any other Japanese company would have to start from our starting point.
<br>
<br>
What do you recommend? Are there any other alternatives? <br>
<br>
Thank you in advance for your advice...<br>
<br>
Alberto.<br>
<br>
<br>
<br>
<br>
</div>
</body>
</html>