我想前幾位前輩解釋的滿清楚的,有些licence,你如果用了,既使你改了source code,也是得公開的。例如osCommerce的GPL:
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
yihungkuo wrote:
前提是我要確認我的網...(恕刪)
code 加密後雖然無法確認是否與原來的 osc 架構相同
但 database 的部分可以與原始的 osc 比對,且從 GET 和 POST 的傳值也能輕易判定
osc 這套我也幫客戶做過客製化,裡面的 code 其實不是很好改(幾乎都連動的)
尤其 database 的部分,要改的話通常是直接寫新的程式配合新的 table 去做
所以要完全改掉 osc 原本的架構是 100% 不可能的,不然一開始何必套 osc 的架構來做?
另外這家公司的做法是綁維護的,在業界是有人這樣做的,要原始檔通常是報價 double
這部分只能說雙方事前溝通不夠,且沒有正式合約可以相互約束
至於報價是否太貴,得看你客製化到哪個地步,如果包含金流等資安技術,應該是有那個價錢
若不是的話,只能看對方有沒有良心了...
內文搜尋

X