The Open Trawler Project!

We have recently kicked off an open source web based trawler design project. The output of the project will be a trawler design that can be used by anyone to build or have built their own boat. It is our goal to start from scratch and end with a design that can be NC cut by anyone who desires to build from the project plans.

Please have a look at our website www.opentrawler.com

We are currently looking for the following core team members:

-CAD – CAM Technology Coordinator (responsible for coordination of all software -used in development)
-Hull Engineering Team Members
-Systems Engineering Team Members
-Propulsion Team Members
-Lead Hull Navel Architect
-Lead Systems Engineer
-Lead Propulsion System Designer
-Lead Marketing Manager
-Interior Designers

The project is called Open Trawler because the design is being produced under the copy left copyright which is the practice of using copyright law to offer the right to distribute copies and modified versions of the work while requiring that the same rights be preserved in modified versions of the work.

 

Forgive me if I'm wrong, but this looks rather like you are trying to get someone to design you a boat for nothing.

 

It's an interesting idea. I love the open source concept -- I use a lot of open source software, and I put quite a bit of time into working on it. But ... for a boat? I don't know. On their specs they've already picked a tank size and engine room color, but haven't yet picked a hull length or an outline of accommodations. They're already arguing about "green" propulsion systems. Seems a bit like choosing the perfect woman by committee ... might end up looking like Frankenwoman.

On the other hand ... if one designer put together the hull form and set some requirements and limitations for other systems and design features an open source community might be able to refine those systems. It seems to me a project like that would naturally branch into dozens of versions, but there would be some systems common to all that could be optimized. It's interesting.

 

The term open source used in the Open Trawler Project describes practices we use in production and development that promote open access to the end product's source materials. Some consider open source a philosophy, others consider it a pragmatic methodology. Those who are involved with the particular open source projects generally have a personal connection to what they are working on either through use of the outcome product or as a hobby in part of its production. It seems that an open source boat project will work well as many of us are hobbiest and or professionals on various parts of boat design or construction.

The guidelines you read on the open trawler site are maintained by the specific team leaders, some were populated before the project kicked off and will be revised as team leaders come on board. Items such as paint and other asthetics can obviously be taken as recommendations not rules. It is our goal to produce a base specification, design, and product that can be reproduced and re used by anyone. This said of course the project can and will branch into many different designs, my guess is that some of these will continue on our site, while others may take place apart from the original Open Trawler project.

I would guess the majority of people lurking on this site could contribute to the Open Trawler Project in some way. Come on over and join today, we are still looking for team leaders and general team members.

 

This is true -- which is why every open source project I've seen or been involved in began with a functioning design that new members could improve and expand. From what I can see, you're starting from scratch. How can a person decide if they want to participate in a design when they have no idea what they're designing? If you started with a designer who donated a proven design, and there were some set some limits on how it was expected to evolve -- you might have something.

Open source software projects have been successful because they are not designed by committees or teams, except on rare occasions. Specific features are generally completely designed by people who want a specific feature, and take control of it. This is only possible where there is an existing core product, and it's clear that all changes and modifications have to integrate with the existing core design and other design elements.

 

Don't get me wrong... I have no problem with the concept of an open source design. Take a look at the Option One threads and you will see that I was one of the originators of the project. Read on though and you will also see that in the end the project ultimately fell short of producing anything tangible. Not because of a lack of desire on the part of the participants, but because ultimately, people who are looking to custom build a boat are looking for such a vast array of often conflicting attributes that no single base can easily satisfy all their needs.

 

"A fuel efficient trawler yacht. "

If efficiency is important in your SOR you have the wrong style.

I looked for a decent SOR on that site for area of operation, and desired economy but the SOR is conspicuously absent. You need to hammer that out so people can actually see what you think you want to achieve in the design. Then we could tell you whether it's even actually feasible.

 

This is 100% correct. Open source projects are usually started & written initially by 1 driven person who wants something and is prepared to put in the hard work to get there. If it's more broadly useful, other people come aboard and the system gathers momentum.

I predict that this project will never get anywhere because the proposer(s) haven't got the expertise or vision to define what they need and then to produce a solid 'proof of concept' system for critique and refinement.

FWIW I'm a software designer with a niche open source system in everyday use and use other open source tools daily.

PDW

 

Understood. In software, you can hang features on a core product like ornaments on a Christmas tree -- there are few limits. In designing a boat, almost every feature is going to fork the project (create a new branch) because system options are highly integrated. In a boat it's not "this and that," it's "this or that" ...