I completely agree with David, Tom and Marco and what they suggest has so far been standard and the advise OSHWA provides when that question arises: can I call my product open source but only release the files in 3/6/12 months?<div>
<br></div><div>As someone pointed out in this discussion: the only differences between a proprietary and open source project are the availability of the files and a license (or statement) that allows anyone to study, copy, modify and redistribute the product. Without the first one, the second one is not very useful.</div>
<div><br></div><div>So while it's perfectly acceptable for a company or individual to release the files at a later point (be it for business reasons or simply because the documentation is not done yet) the product is not actually open source until this happens and therefore should not be described as such. Intent is impossible to gauge and, in my opinion, can't be factored in.<br>
<br><div class="gmail_quote">On Sat, Mar 2, 2013 at 5:27 PM, Marco Perry <span dir="ltr"><<a href="mailto:mperry@pensanyc.com" target="_blank">mperry@pensanyc.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF"><div>Call its open when it's open. One can always plan and lay graphics out on your equipment and packaging, but if it ships/posts/ is deployed in a significant way with a logo and it's not open yet, thats should not be allowed. It's like a UL logo. You plan for it, but they wouldn't let a product ship that didn't pass their standards and still use their logo. <br>
<br>Sent from my iPad</div><div><div class="h5"><div><br>On Mar 2, 2013, at 3:22 PM, Tom Igoe <<a href="mailto:tom.igoe@gmail.com" target="_blank">tom.igoe@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite">
<div>That argues in favor of only calling it open when it ships, doesn't it?<br>
<br><div class="gmail_quote">Marco Perry <<a href="mailto:mperry@pensanyc.com" target="_blank">mperry@pensanyc.com</a>> wrote:<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>What if the person doesn't follow thru with best practices? It's hard to revoke if the boards and package is printed.<br><br>Sent from my newly outdated iPhone 4S</div><div><br>On Mar 2, 2013, at 10:52 AM, Tom Igoe <<a href="mailto:tom.igoe@gmail.com" target="_blank">tom.igoe@gmail.com</a>> wrote:<br>
<br></div><blockquote type="cite"><div>I'd agree with that, though it's an interesting question for things like Kickstarter campaigns. Do you release the files when you start your kickstarter campaign, or when you ship? <div>
<br></div><div>r.</div><div><br><div><div>On Mar 2, 2013, at 10:49 AM, David A. Mellis wrote:</div><br><blockquote type="cite"><span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><div dir="ltr">
Personally, I think it's okay to use "open-source hardware" and the logo as long as the design files are released with the product. Before release, the distinction between "is" and "will be" seems like a subtle one -- for everything about the product, not just whether or not it's open-source. </div>
<div class="gmail_extra"><br></div></span></blockquote></div><br></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>discuss mailing list</span><br>
<span><a href="mailto:discuss@lists.oshwa.org" target="_blank">discuss@lists.oshwa.org</a></span><br>
<span><a href="http://lists.oshwa.org/listinfo/discuss" target="_blank">http://lists.oshwa.org/listinfo/discuss</a></span><br></div></blockquote><p style="margin-top:2.5em;margin-bottom:1em;border-bottom:1px solid #000">
</p><pre style="white-space:pre-wrap;word-wrap:break-word;font-family:sans-serif;margin-top:0px"><hr><br>discuss mailing list<br><a href="mailto:discuss@lists.oshwa.org" target="_blank">discuss@lists.oshwa.org</a><br><a href="http://lists.oshwa.org/listinfo/discuss" target="_blank">http://lists.oshwa.org/listinfo/discuss</a><br>
</pre></blockquote></div>
<br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.</div></blockquote></div></div></div>
<br>_______________________________________________<br>
discuss mailing list<br>
<a href="mailto:discuss@lists.oshwa.org">discuss@lists.oshwa.org</a><br>
<a href="http://lists.oshwa.org/listinfo/discuss" target="_blank">http://lists.oshwa.org/listinfo/discuss</a><br>
<br></blockquote></div><br></div>