<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 11, 2013, at 11:34 AM, malcolm stanley wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><i><span style="font-family:arial,sans-serif;font-size:13px">The day's not too far away when you melt down the case of your old gameBoy to feed your 3D printer, for example. But that's not an OSHWA problem. Yet.</span><br>
</i><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div style=""><span style="font-family:arial,sans-serif;font-size:13px">If not now, when? </span></div></div></blockquote><div><br></div>OK, start building it!<br><blockquote type="cite"><div dir="ltr"><div style=""><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div style=""><span style="font-family:arial,sans-serif;font-size:13px">its interesting to me that (re)-cyclical manufacturing of the type that you note implies access to the designs we are discussing, parts of which will be re-usable on a component basis and parts of which will be re-usable on a materials basis.</span></div></div></blockquote><div><br></div>Me too, I've been shouting about that to whoever would listen for the last six years or so. It's why I'm interested in open source hardware in the first place.</div><div><br><blockquote type="cite"><div dir="ltr">
<div style=""><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div style=""><font face="arial, sans-serif">begs the interesting question of when and whether we come to grips with deconstruction and tear down instructions for re-use. In Europe I think now for some products this is a requirement...</font></div></div></blockquote><div><br></div>You're talking about WEEE, I think, which requires take-back, but other than that and RoHS, I'm not sure a full ingredient list is required yet. I'd love to see it happen.</div><div><br></div><div>Also, there's money in recycling, and I think it could be more profitable if it's easier to do it safe because you have a de-construction guide for each product.</div><div><br></div><div>t.</div><div><br><blockquote type="cite"><div dir="ltr">
<div style=""><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div></div><div class="gmail_extra"><br clear="all"><div>_________________________________________<br>malcolm stanley<br><br>google.voice: 215.821.6252 <div>
Cell: 267.251.9479 <------------- new<br>email: <a href="mailto:a.malcolm.stanley@gmail.com" target="_blank">a.malcolm.stanley@gmail.com</a><br>twitter / linkedin: amstanley<br>Read my blog at <a href="http://soaringhorse.blogspot.com/" target="_blank">http://soaringhorse.blogspot.com</a><br>
_________________________________________</div></div>
<br><br><div class="gmail_quote">On Mon, Mar 11, 2013 at 11:25 AM, Tom Igoe <span dir="ltr"><<a href="mailto:tom.igoe@gmail.com" target="_blank">tom.igoe@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
On Mar 11, 2013, at 11:15 AM, Chris Church wrote:<br>
<br>
><br>
> On Mar 10, 2013, at 8:59 PM, Tom Igoe wrote:<br>
><br>
>> Great idea, but I wasn't actually imagining icons on the board itself, but on the website or packaging, more like a nutrition label. I think the two could work well together.<br>
><br>
> Tom,<br>
><br>
> That is pretty awesome. If you don't mind, we may follow this cue on our next products coming out here in a month or so. I like that way better than symbols that have to be looked up. (And it would look great on a certain style of company's packaging, like ours.)<br>
<br>
</div>Sure thing, I can put the SVG up somewhere in a CC-BY-SA if you want.<br>
<div class="im"><br>
><br>
> For recycling, don't we already have guidelines? I already have to print certain symbols on our batteries and electronics, I don't imagine it would require much more than that?<br>
<br>
</div>We have icons, but that's for consumers. I'd like to see us take it further, to where we're really talking about all the components. The day's not too far away when you melt down the case of your old gameBoy to feed your 3D printer, for example. But that's not an OSHWA problem. Yet.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
t.<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
> Chris<br>
><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>
_______________________________________________<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>
</div></div></blockquote></div><br></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></body></html>