<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hmm, I think a mail in response to Nate's question this morning got lost. A few things I'd like to see:<div><br></div><div>What are the next steps for OSHWA, based on what do its constituents need?</div><div><br></div><div>Marco's mails have been really informative on what use IDSA has been to its members. Question for the members, what use has OSHWA been for you, and what further use could it be?</div><div><br></div><div>How can the OSHW definition be used in practice? </div><div><br></div><div>I'm still confused on this. Nate's document on how to open-source something seems good to me, and it seems like a beginning of the layering approach I was advocating at the beginning of this thread. I'd love to see that list turned into a checklist or an online tool that can help people determine what to do next. I'll pick that up in another thread though.</div><div><br></div><div>t.</div><div><br></div><div><br></div><div><br><div><div>On Mar 1, 2013, at 3:50 PM, David A. Mellis wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Great question, Nate! I think we could use a few things:<div><br><div><i>A definition of open-source hardware. </i>This we've got, although we may need to do a better job of explaining that and how it applies to things besides circuit boards. In most situations where things are described in words, I think it's straightforward to be clear about which parts of a project are open-source and which aren't. The confusion seems mostly to arise when we're applying the logo in a situation where it's not clear what it refers to. Which brings us to the next thing we need...</div>
<div><br></div><div><i>Guidelines for the use of the logo.</i> This seems to be most of what we're debating. It's complicated by the variety of ways you can use the logo and of combinations of open- and closed-source parts that might be nearby. Does somewhat want to take a shot at distilling the discussion down into some guidelines?</div>
<div><br></div><div><i>Best practices for open-sourcing something.</i> This would be great for the community to work on. Nate's document (<a href="http://www.oshwa.org/sharing-best-practices/">http://www.oshwa.org/sharing-best-practices/</a>) seems like a good starting point, although I'd suggest rephrasing it to clarify which activities are core to the practice of open-source hardware (i.e. sharing original source / design files) and which are simply useful additions. Should we make a Google Doc (or use a wiki) to edit it collaboratively? Anyone have any specific suggestions for changes?</div>
<div><br></div><div>David<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 1, 2013 at 12:21 AM, Nathan Seidle <span dir="ltr"><<a href="mailto:nathan@sparkfun.com" target="_blank">nathan@sparkfun.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div>I am enthralled by this discussion but what should come of it? Topics to add to the FAQ? We need to consolidate the communities' feelings into one place so that we do not repeat the same debates.</div>
</div></div></blockquote></div></div></div></div></div>
_______________________________________________<br>discuss mailing list<br><a href="mailto:discuss@lists.oshwa.org">discuss@lists.oshwa.org</a><br>http://lists.oshwa.org/listinfo/discuss<br></blockquote></div><br></div></body></html>