Can Open Source Hardware Feed the World?
jfruhlinger writes "When it comes to food scarcity in the developing world, one of the major problems is production capacity: land that could be arable using modern techniques goes underutilized because locals don't have the ability to build or buy equipment. A group calling itself Open Source Ecology is trying to solve that problem. They've developed a set of open source hardware specs for 50 different industrial machines, which they're calling the Global Village Construction Set."
Worry about stabilizing the regional governments first and then worry about upgrading them to first world farming techniques.
Keeping those who know how to farm alive and on the land they know how to farm will be necessary to make new equipment have any lasting effect.
No.
I'd say, ask Norman Bourlag how it could be done, but he's dead unfortunately. But he had a good plan, and several other good plans. I'm sure crazy greenies and environmentalists will come out whining now, but 'green farming' will never produce enough food. And unless you're going to shovel off 2/3's of the population to die. His ideas will be the future of farming.
Om, nomnomnom...
Its spelled Cid Meier.
If I can just reach out with my words and touch a butthole, just one, it will all be worth it.
http://openfarmtech.org/wiki/Main_Page
"Lame" - Galaxar
"In a visit to Ethiopia in 2009, I talked to more than one citizen there who said that the arability of the land wasn't so much the problem as not having the machines to farm the land productively. "
This is completely ignorant. Read here:
"In the late 1970s Ethiopia's communist regime nationalised all land, and private ownership remains outlawed. The millions of small-scale farmers work under licence from the state, and most plots are one hectare or less, which has hampered efforts to improve food security."
Now the Ethiopian government is leasing out large scale plots of land to foreign farm companies, which will certainly produce some work for Ethiopians, but your typical Ethiopian still has no ownership of the land and thus no ability to use that capital to get loans for farm equipment, fertilizer, and seed.
As Hernando DeSoto pointed out in "The Mystery of Capital", every developed nation in the world at one time went through the transformation from predominantly informal, extralegal land ownership to a formal, unified legal property system that allowed people to leverage property into wealth. This has not been done in countries such as Ethiopia (Egypt is another country with little rural private land ownership).
Lack of private property rights and over-regulation and government ownership of business causes poverty. Enhancing private property rights and freedom to participate in commerce cause wealth. Even the Chinese have realized this (belatedly, after starving tens of millions of people to death with collective farming during the Great Leap Forward).
Poor people around the world are not too stupid, too lazy, or too ignorant to be entrepreneurs and productive farmers. They are simply kept from becoming rich by government. They can solve their own problems if they are allowed to.
Open specification is giving the requirements, but not necessarily a detailed plan, for a pole. (And then probably charging licensing fees when someone makes a pole using the spec; "open" is not "free".)
"Open Source" is giving someone the plans for a pole in detail, and allowing them to do whatever they want with the plans, including modification or redistribution (perhaps we could better label this "Free Hardware").
Remember, just because you get can get binaries and happen to have a compiler doesn't mean that "open source" software is anything but "detailed plans" that have to be built in order to actually do anything.
Don't think of it as a flame---it's more like an argument that does 3d6 fire damage
No,
Garden of Eden Creation Kit - Open Source
G.E.C.K.O.S.
See if you can get the Geico critter as a spokes-lizard.
Learning HOW to think is more important than learning WHAT to think.
Apache Web Server is open source, yet the Apache group doesn't give you a working server, nor do they give you the power to turn the server on. They give you source code and instructions to achieve a working server. You must provide the hardware, power and the time.
Your comparison to the fishing proverb isn't appropriate.
Closed source is giving a man a fish (I agree)
Open source is teaching a man to fish (which I believe would encompass teaching the necessary pole technology)
Source is knowledge, not product.
"Lame" - Galaxar
Right now most countries refuse American Corn and wheat unless it has been ground up int a meal or flour. Why? because Monsanto has polluted our food stream with it's copyrighted and trademarked products so completely that other countries do not want to allow the lawsuit ridden crops to ever be planted in their countries. Monsanto has sued most USA farmers out of existence that dared to plant a non Monsanto crop by claiming IP infringement when a neighbor crop cross pollinates theirs. and IF you dare to own a seed cleaner and keep part of your crop as seed, they will go after you and bankrupt you. Most other countries, including the ones that have a lot of starving people do not want this problem there. Monsanto owns the USA, they do not want them to own them as well so they refuse crops and seed from the USA.
Want to feed the world? fight for the invalidation of all patents on food crops.
Do not look at laser with remaining good eye.
I founded the Open Graphics Project. Our objective was to develop an open source graphics card. At the time, no GPU maker was releasing specs that would allow FOSS developers to write good drivers. This started in 2004, with a lot of attention and excitement. Being the sort to DO, rather than just complain, and also being a graphics chip designer, I decided that the open approach might be the solution. There were multiple slashdot articles, interviews, and a good deal of hardware design and software was developed.
It's now 2011, and you most likely have never heard of the Open Graphics Project. Also, it's 2011, and most other open hardware projects have come and gone or are just limping along.
Why is this? Because nobody wants to provide the one thing that makes or breaks an open hardware project: Money.
Building hardware costs money. Designing it is hard enough, but we got that accomplished. It took until 2009 before the OGP managed to actually build our prototype hardware in quantities that we could lend and sell, and this was because we got donations from the Linux Fund.
Why does no one put up money? Because it's (rightfully so) too much of a risk. If you could predict that one project or another would succeed, you might invest, especially if you knew that you'd get some kind of return on your investment (besides "sponsor"). But you can't make that prediction, and it's foolish for you to throw money at every fly-by-night project that comes along. And thus, open hardware projects die, except those that are backed by someone who already has money. The problem is that most of THOSE people aren't willing to "give away" their designs. Conundrum.
Some friends and I have some solutions we're working on. Watch this space for late Summer 2011. :)
There is an entertaining video on this from a presentation at TED (Technology Entertainment and Design) that is only 4 minutes long. And no I've never been.
http://www.ted.com/talks/marcin_jakubowski.html
Kalashnikovs and RPGs are already made in simple machine shops.
If we actually gave a fuck about the folks in Darfur etc, we'd arm them decisively and the Janjaweed would be dead on the spot.
That's too controversial so we protract their agony instead.
"This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
. . . and the other 70%?
"Stop worrying about what to do first and just do something. Anything."
Which is exactly how you get into knee-jerk reaction based crises. I hope you've never complained about Iraq II or the TSA.
Closed source is giving a man a fish (I agree)
Open source is teaching a man to fish (which I believe would encompass teaching the necessary pole technology)
I like your analogy. It clearly shows the difference between open and closed source.
Thinking about it now for a while, I may use it in discussions, with this tweak:
Closed source is giving a man a fish
Open source is letting a man watch you fish
Code + documentation is showing a man how to fish
The extent to which code is self-documenting is the extent to which the fisherman gives you hard-won pointers between sips of beer. For technical discussions, this drills home the point of writing readable code and documenting what you've done :)
My suspicion is that you're going to wind up reimplementing a good fraction of a CNC machine's functionality, but here's an idea that might save you some time:
Implement the 1.5" increments via a ratchet-like mechanism. Allow the tube to slide down the V of some angle iron placed at a steep (say, 60 degree) angle. The drills are placed halfway down this. In the lower half of the V, there are registration pins (probably bolt heads of the appropriate size, machined to the proper diameter and with some taper for self-centering) every 1.5" for a couple repetitions. The tube is placed into the V, hits the first registration pins, is clamped to the V using electromagnets, and drilled from both directions (you have several options for moving the two drills here, but I kinda like the idea of pushing the drill away from the work with a spring and pushing it towards the work with pneumatic bellows). Once the drilling is done, some electromagnets above the tube pulse for a bit so that the tube pops up and slides down onto the next set of registration pins, and you repeat. The tube falls out of the V when it clears the last set of registration pins. Be generous with the hardware interlocking - at the very least you want to make sure one drill is out before the other drill goes in.