<div dir="ltr">I agree with your sentiments, Tom. If the code isn't your asset why not make it publicly available?<div><br></div><div>Just for the sake of information, as someone whose former job entailed ensuring my paranoid company was 100% legal w.r.t. open source compliance, sometimes making source code publicly available is not as straightforward as it may seem. DSI may not actually own the code; it may have been licensed to DSI in perpetuity by the programmer who actually owns the code. Or the code may contain other code or libraries that haven't been open sourced, and seeking those third parties' approvals to open source *their* code might not be easy, or even possible. Or the code may be so messy or full of obscene comments that it would be too much of an overhead for a tiny business to clean it all up just to make it public. And last, but not least, manufacturers often no longer have the code! That won't the case with DSI but wasn't uncommon in days gone by. <div><br></div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, 14 Mar 2017 at 21:47 Tom Wiltshire <<a href="mailto:tom@electricdruid.net">tom@electricdruid.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg">I'm not sure I agree. Why shouldn't they share the "proprietary code"? "Proprietary" is just a way of saying "owned" e.g. not public or shared, isn't it? So it's only "proprietary" because they choose to keep it so.<div class="gmail_msg">After all, sharing it doesn't stop them from using in the next product in any way shape or form. In fact, DSI might find that other people make improvements to it that they'd never thought of, or would never have had the resources to do (everyone says Tempest, although a greta box, could use some further bug fixes and improvements from what I understand). In which case, they could continue to produce Tempest hardware (let's not forget that this Open Source OS is only useful on one single proprietary product that you need to pay DSI money for - and that's all good) and people could put some amazing code on it, or better still, people could put whichever amazing code they fancied on it.</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Frankly, I don't really understand why manufacturers haven't seen what's happened with the chip/OS upgrades for some vintage/classic gear which has given them new lease of life and multiplied second-hand values to some incredible degree. That could be your product, and it could be now, and you could still be making them, while the user community does the (hard) software work for you! How is that not a good thing?! Imagine you were Roland producing Jupiter 6's and the Europa mod came out? Wouldn't you embrace it? How many more Jupiter 6's would you sell?</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">I think manufacturers need to step back and take a much bigger-picture view of this. If they did, I think they'd see that a more sharing relationship with their user base might pay dividends financially.</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><div class="gmail_msg">Tom</div><div class="gmail_msg"><br class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg">On 14 Mar 2017, at 18:35, Bruno Afonso <<a href="mailto:bafonso@gmail.com" class="gmail_msg" target="_blank">bafonso@gmail.com</a>> wrote:</div><br class="m_-8319528566846136359Apple-interchange-newline gmail_msg"><blockquote type="cite" class="gmail_msg"><div dir="ltr" class="gmail_msg">I definitely understand that and I'm not thinking he should share their proprietary code. Just the required info on how to interface with the hardware for any one interested in writing their own. May be unrealistic, not sure.<br class="gmail_msg"><br class="gmail_msg"><div class="gmail_quote gmail_msg"><div dir="ltr" class="gmail_msg">On Tue, Mar 14, 2017 at 2:26 PM Chromatest J. Pantsmaker <<a href="mailto:chromatest@azburners.org" class="gmail_msg" target="_blank">chromatest@azburners.org</a>> wrote:<br class="gmail_msg"></div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr" class="gmail_msg">He probably will reuse chunks of it for other projects, so it would still be useful for him.</p>
<div class="gmail_quote gmail_msg"></div><div class="gmail_quote gmail_msg">On Mar 14, 2017 2:04 PM, "Bruno Afonso" <<a href="mailto:bafonso@gmail.com" class="gmail_msg" target="_blank">bafonso@gmail.com</a>> wrote:<br type="attribution" class="gmail_msg"></div><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote gmail_msg"><div dir="ltr" class="gmail_msg"><span style="font-size:13px" class="gmail_msg">Just read that Dave announced no additional development will be made on the tempest firmware. I wonder in that case why not let anyone make new ones? Share all the needed information for the community to write their own. </span></div></div>
<br class="gmail_msg"></blockquote></div><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">_______________________________________________<br class="gmail_msg">
Synth-diy mailing list<br class="gmail_msg">
<a href="mailto:Synth-diy@synth-diy.org" class="gmail_msg" target="_blank">Synth-diy@synth-diy.org</a><br class="gmail_msg">
<a href="http://synth-diy.org/mailman/listinfo/synth-diy" rel="noreferrer" class="gmail_msg" target="_blank">http://synth-diy.org/mailman/listinfo/synth-diy</a><br class="gmail_msg">
<br class="gmail_msg"></blockquote></div>
</blockquote></div></div>
_______________________________________________<br class="gmail_msg">Synth-diy mailing list<br class="gmail_msg"><a href="mailto:Synth-diy@synth-diy.org" class="gmail_msg" target="_blank">Synth-diy@synth-diy.org</a><br class="gmail_msg"><a href="http://synth-diy.org/mailman/listinfo/synth-diy" class="gmail_msg" target="_blank">http://synth-diy.org/mailman/listinfo/synth-diy</a><br class="gmail_msg"></blockquote></div><br class="gmail_msg"></div></div></div>_______________________________________________<br class="gmail_msg">
Synth-diy mailing list<br class="gmail_msg">
<a href="mailto:Synth-diy@synth-diy.org" class="gmail_msg" target="_blank">Synth-diy@synth-diy.org</a><br class="gmail_msg">
<a href="http://synth-diy.org/mailman/listinfo/synth-diy" rel="noreferrer" class="gmail_msg" target="_blank">http://synth-diy.org/mailman/listinfo/synth-diy</a><br class="gmail_msg">
</blockquote></div><div dir="ltr">-- <br></div><div data-smartmail="gmail_signature">-- <br>Sean</div>