<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>
</head><body style="">
<div>
Consider starting with "why" too:
</div>
<div>
</div>
<div>
<a href="https://www.youtube.com/watch?v=qp0HIF3SfI4">https://www.youtube.com/watch?v=qp0HIF3SfI4</a>
</div>
<div>
<p>We could learn a lot from how something thrives in the marketplace. </p>
<p> </p>
<p>On March 26, 2013 at 10:20 AM Matt Maier <blueback09@gmail.com> wrote:<br/><br/>The problem is that we don't know what we need.<br/><br/>That's where the committee comes in. We need to get some stakeholders into a room and hash out a mutually agreeable prioritization of requirements. There is little point in discussing specific "hows" until we have some consensus on "what." <br/><br/>For example, the STEP file format is indeed a standard for exchanging product information, but it's copyrighted and has a massive amount of overhead. I doubt even OSE is doing any project big enough to justify that much complexity. A giant, complicated format like STEP could obviously describe simple projects, but it would also create a huge barrier to entry due to all of the complexity that is only there for complex projects. Since most open hardware projects are simple, or at least striving for simplicity, STEP might be kind of like hiring a marching band to follow you around and play a song when you get a new text message.</p>
</div>
<p> </p>
<div>
</div>
</body></html>