Re: [Paddlewise] Boat Design

From: Elias Ross <genman_at_noderunner.net>
Date: Sat, 14 Aug 2004 01:01:27 -0700
Doug Lloyd wrote:
> Here's a link to an excellent article that gives a hint regarding the work
> that goes into designing a kayak:
> 
> http://www.pygmyboats.com/WoodenBoat%20Article.htm

It was interesting reading about software and kayaks:  I spend a bit of 
my free time and some work time developing "free software", which is 
"free as in freedom".  I'm many of you out there have heard of Linux, or 
maybe the web browser Mozilla or HTTP server Apache.  All of these 
software packages are free to copy, with some restrictions.  They are 
copy-lefted, not public-domain, meaning that the original creator 
reserves certain rights and control over their own copyrighted work.

http://www.gnu.org/philosophy/free-sw.html

     * The freedom to run the program, for any purpose (freedom 0).
     * The freedom to study how the program works, and adapt it to your 
needs (freedom 1). Access to the source code is a precondition for this.
     * The freedom to redistribute copies so you can help your neighbor 
(freedom 2).
     * The freedom to improve the program, and release your improvements 
to the public, so that the whole community benefits (freedom 3). Access 
to the source code is a precondition for this.

I spend a bit of my time helping out these projects because:  1.  I use 
free software and feel obliged to contribute because if I don't, who 
will?  2. I enjoy the pride of seeing my contributions out there, the 
name recognition is nice as well.  3.  It's fun.  4.  Helps my resume, 
it looks good to employers.

Software design isn't exactly boat design, in that boats are probably 
best designed by one hand.  Does this analogy make any sense? 
And--currently--designs can't be protected like software can.

But consider if boat designs were protected and there was a similar 
"free" boat design movement, as say Linux:  If you had somebody who came 
out with 3 solid hull designs, publish under "copy-left" (which were 
copyrighted), consider the possibilities.  Although many expect anarchy 
when it comes to free software, changes are usually tightly controlled 
and a free software package often turns into a mature product.  Eric 
Raymond calls the free software development model the Bazaar:

http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar

If kayak designs were like free software, expert paddles and even 
average paddlers might contribute changes or suggestions.  (People can 
make suggestions now, but let's say the designer ignored your pleas: 
Your own changes could be incorporated in a related design.)  What if 
there was a "bug" database for kayaks, where design defects or 
suggestions could be tracked?

With appropriate design collaboration software (e-mail?) maybe somebody 
would develop the Linux of kayaks.  (Penguin shaped!?)

Anyway, free designs could be downloaded and customized for different 
people:  Maybe some of these designs would be appropriate for home 
builders (plywood or strip construction), others would be published for 
commercial development (fiberglass or plastic).  Any of your changes 
would have to be released.  If you change a loft line or two, you would 
be obligated to publish the new dimensions and acknowledge that whoever 
still "owned" the original design, though he may or may not have 
approved it.  (Typically, under free software you have the freedom to 
keep the changes to your self if you don't redistribute them.)

How would designers make money?  Well, the same way that Linus makes 
money:  Business and software consulting.  Customization.  Branding. 
What impulse would there be to design something new?  Fun.

Industry analysts speculate that Linux is going to take over the 
operating system market--well, maybe not for home systems, but at least 
for servers--in the not-so-near future.  Eventually, maybe in the next 
fifty years, without design protection in law or not, enough people are 
going to "donate" enough kayak designs.  We'll eventually have 
intelligent enough software and fabrication machinery to instantly pump 
out these designs and any variations.  There likely isn't going to be 
any need for the Microsoft of the kayak world.

[P.S.  Personally, I would like to see protection for boat designers, 
but at the same time I don't want designers to be "anti-social" (for 
want of a better word.)]
***************************************************************************
PaddleWise Paddling Mailing List - Any opinions or suggestions expressed
here are solely those of the writer(s). You must assume the entire
responsibility for reliance upon them. All postings copyright the author.
Submissions:     PaddleWise_at_PaddleWise.net
Subscriptions:   PaddleWise-request_at_PaddleWise.net
Website:         http://www.paddlewise.net/
***************************************************************************
Received on Mon Aug 16 2004 - 06:09:16 PDT

This archive was generated by hypermail 2.4.0 : Thu Aug 21 2025 - 16:31:16 PDT