Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Open Manufacturing
Home
+ new post
About this group
Join this group
Fwd: Google Doc for describing best practices.
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Bryan Bishop  
View profile  
 More options Mar 7, 3:07 pm
From: Bryan Bishop <kanz...@gmail.com>
Date: Thu, 7 Mar 2013 14:07:01 -0600
Local: Thurs, Mar 7 2013 3:07 pm
Subject: Fwd: Google Doc for describing best practices.
Print | Individual message | Show original | Report this message | Find messages by this author

From: Nathan Seidle <nat...@sparkfun.com>
Date: Tue, Mar 5, 2013 at 12:16 PM
Subject: Re: [Discuss] Google Doc for describing best practices.
To: The Open Source Hardware Association Discussion List <
disc...@lists.oshwa.org>

Hi David - thanks for hammering on this. Ayah - I hope you don't mind but I
use littlebits as an example. I'd love to hear your feedback.

I can't quite get wording of an important section of 'Overall' and would
like to discuss it. Littlebits is an example of mixed open/close. The PCB
layouts are released (https://github.com/littlebitselectronics), the
connectors are awesome and novel and unique, but are not released. This mix
can be found in other projects, Makerbot being a large one. There are lots
of parts we all use that won't have design docs (ex: microUSB connector),
but when we the designer have access to the design docs and they are not
released, then the design is not open source hardware in my eyes. I want to
be clear that I don't think little bits is doing anything wrong; we've just
never addressed this aspect. However, going forward I think we need to
clear up the ambiguity. So here's my stab at the wording:

Any part of a design that can be opened but is intentionally withheld will
cause a design to be considered partially open. The rule of thumb: Have I
released all the source files that I have access to? If the answer is no,
then the project is not OSHW.

I don't want to discourage people from releasing! So I'm willing to
consider 'partially open' wording as a way to allow folks to get the
benefits of open community while closing parts of a design if they feel the
need.

Cheers,
-Nathan

--
Nathan Seidle
CEO, SparkFun Electronics Inc
Boulder, CO
Phone : 1-303-284-0979
Fax : 1-303-443-0048

On Sun, Mar 3, 2013 at 6:35 PM, David A. Mellis <d...@mellis.org> wrote:

_______________________________________________
discuss mailing list
disc...@lists.oshwa.org
http://lists.oshwa.org/listinfo/discuss

--
- Bryan
http://heybryan.org/
1 512 203 0507


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Bryan Bishop  
View profile  
 More options Mar 7, 3:07 pm
From: Bryan Bishop <kanz...@gmail.com>
Date: Thu, 7 Mar 2013 14:07:26 -0600
Local: Thurs, Mar 7 2013 3:07 pm
Subject: Fwd: Google Doc for describing best practices.
Print | Individual message | Show original | Report this message | Find messages by this author

From: Catarina Mota <catar...@openmaterials.org>
Date: Thu, Mar 7, 2013 at 11:04 AM
Subject: Re: [Discuss] Google Doc for describing best practices.
To: The Open Source Hardware Association Discussion List <
disc...@lists.oshwa.org>

Hi all,

We're organizing a hackathon to arrive at some OSHW documentation best
practices and tools: http://www.opensourcewarehouse.org

It all started a few months ago with a few causal conversations with open
source hardware developers that were concerned with the fact that weren't
getting enough public contributions to their projects and also that they
sometimes found it difficult to build on top of other's projects. Both were
related to insufficient, deficient or hard to interpret documentation. So
this got us thinking about how can we improve documentation to make open
source hardware more accessible to all and to drive more contributions to
projects. This is the initial list of challenges we identified (to build
upon by the community):
http://www.opensourcewarehouse.org/problem-statement/

And here's an initial taxonomy (to be refined or abandoned at the
hackathon):
https://docs.google.com/spreadsheet/ccc?key=0AkNG-lv1ELQvdHViNEdtVHp4...

Since this a huge challenge and one that concerns the entire community, we
figured the best way to approach it would be to start with a hackathon to
identify the problems and find ways to tackle them.

We hope that some of the outcomes will be:

- A set of best practices for open source hardware documentation, including
a taxonomy and a check list.
- A set of recommended software tools for generating and sharing
documentation - this may either be the adoption of something that is
already out there or, more likely, a mashup of existing platforms
- A way to identify which parts of a project are open source and have
documentation
- The seed for an OSHW repository or a search engine

I hope many of you can join us and bring your ideas and insights to the
table. More details coming up on a separate email.

Cheers,
Catarina

On Tue, Mar 5, 2013 at 4:17 PM, Windell H. Oskay <wind...@oskay.net> wrote:

_______________________________________________
discuss mailing list
disc...@lists.oshwa.org
http://lists.oshwa.org/listinfo/discuss

--
- Bryan
http://heybryan.org/
1 512 203 0507


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google