<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body >For things like that there's the legacy approval, isn't it? Could you send us a link to one of your software?
<div id="message"></div>
<br id="br3">
<div id="signature"></div>
<div id="content"><blockquote><br> ---- On Do, 23 Jun 2016 15:08:25 +0200 <b> feiteng854@gmail.com </b> wrote ----<br><br><div>Thanks for sharing your point of view.<div><br></div><div>ZPL has been applied in three of our products and approved by hundreds of thousands users of ours. It has made our team to be able to keep updating our software and other developers to benefit from our open source software.</div><div><br></div><div>With the spirit of sharing and respect to OSI, we submitted our request for approval. But <span></span>apparently, there is a huge divergence between you who has dozens of years experience dealing with open source and us. It might seems to you that what we are doing is not open source, which is OK to us, because we are more practical and value our users' approval.</div><div><br></div><div>Thank you all for your time and advice.</div><div><br><br>On Thursday, June 23, 2016, Carlo Piana <<a target="_blank">osi-review@piana.eu</a>> wrote:<br><blockquote style="margin: 0 0 0 0.8ex;border-left: 1.0px rgb(204,204,204) solid;padding-left: 1.0ex;"> <div> <div>Open source spirit and open source law are the same.<br> <br> The spirit lies in licenses that abide by the principles. If we relaxed the principles, the spirit would go. Nothing is absolute, and a rule of reason can be applied. But there are limits, like field-of-endeavour limitations, which is a no-no. A piece of software whose source code cannot be used in certain fields or in certain combinations, is not open enough. It's not a bad thing, but it's not open source and cannot receive approval.<br> <br> Therefore, to obtain the badge of being open source, the license shall adapt to the rules, not the rules to the license, for practical reasons. Had we (collectively) acted for practical reasons some 20 or 25 (alas, actually more than 30!) years ago, open source would not exist now. Most of people who knew what was workable taught us that open source was a garage developers' toy, if not a cancer. <br> <br> My opinion. Others might feel different.<br> <br> All the best <br> <br> Carlo<br> <br> <br> On 23/06/2016 08:45, Fei Teng wrote:<br> </div> <blockquote>As time goes by, everything is changing and changed. Different situation requires different license. Changes might happen to badgeware license in the future. <div><br> </div> <div>In China, a lot of developers who love open source eventually stopped updating their software because of other developers' violation of the common rules and disrespect the open source spirit. If this keeps happening, it is harmful to the whip open source community. <span></span> </div> <div><br> </div> <div>Is it to follow all the old rules which is detrimental to open source spirit more important? Or to take actions to protect open source spirit more important?</div> <div><br> </div> <div><br> </div> <div><br> <br> On Wednesday, June 22, 2016, Josh berkus <<a target="_blank"></a><a target="_blank">josh@postgresql.org</a>> wrote:<br> <blockquote style="margin: 0 0 0 0.8ex;border-left: 1.0px rgb(204,204,204) solid;padding-left: 1.0ex;">On 06/20/2016 08:29 PM, Fei Teng wrote:<br> > 3. A lot of end users removed the badge of our product<br> > 4. A lot of developers who develop based on our product removed the<br> > badge of our product and they do NOT share their code with us<br> <br> I thought we weren't approving any badgeware licenses? If that's the<br> case, why are we still talking to Fei Teng?<br> <br> --Josh Berkus<br> _______________________________________________<br> License-review mailing list<br> <a target="_blank">License-review@opensource.org</a><br> <a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review</a><br> </blockquote> </div> <br> <fieldset></fieldset> <br> <pre>_______________________________________________
License-review mailing list
<a target="_blank">License-review@opensource.org</a>
<a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review</a>
</pre> </blockquote> <br> </div> </blockquote> </div> _______________________________________________<br>License-review mailing list<br><a href="mailto:License-review@opensource.org" target="_blank">License-review@opensource.org</a><br><a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review</a><br></div></blockquote></div></body></html>