Free-Libre-Open Hardware Definition
Hello, I'm starting a "friendly fork" of the OSHW Definition here because, currently engaged in writing a free/libre/open hardware project proposal to a set of potential clients who are not at all familiar with the whole genre of free/libre/open approaches, I feel the current OSHW Definition is not concise enough to just reproduce as an excerpt. I also feel the current OSHW Definition risks the same division between "open source" methods and "free" ethics that has complicated relations for years within the free/libre/open source software community.
Back in 2004 while preparing a presentation deck for my Director General in government, I needed to cram the OSI definition into a single screen: http://www.goslingcommunity.org/gtec2004.shtml In the end I felt the short version I had adapted was more useful as a definition than the original, in the same sense that dictionaries also hold to very concise phrases. Over the years too, I came to see the importance of including both the methods and ethics elements into projects.
So what appears here as a "fork" to facilitate discussion is the current draft text that appears in my own free/libre/open hardware document.
I hope nobody is offended by this thorough change. Putting it up as a fork here just seemed to best way to discuss it without interfering with your main definition text.
Updating and creating a stable version.
Hello, my name is Michelle Kosik, I'm new to this so please excuse my inexperience. I was hopping we can make the font bigger or bolder. How do I change the version to the stable vershion?
- You don’t just change the stable version. See Authoring process for more information. --Mormegil (talk) 05:18, 26 March 2013 (EDT)
Definition should contain a link to Definition/1.1 to make it easier for people to refer to that version specifically. (People who write books, for example, might not intend to link to Definition which is a moving target, but to Definition/1.1 which their book refers to.)
- I added the link into the grey introduction box. Do you think it is OK? --Mormegil (talk) 11:58, 17 February 2015 (EST)
Expire of licenses if break
Source requirement on stable vs. optional source offer on unstable
I have noticed, thanks to some people on a IRC channel on chat.freenode.net, that the stable version requires source files to be redistributed and be on a format/standard/codec that is friendly to free/libre software, while the unstable version puts redistribution of source files as an option.
I, personally, see that, under the stable definition, almost no work would qualify as free/libre cultural work, not even those under free/libre licenses.
I'm not a free/libre culture activist (I'm only a free/libre software activist that thinks that non-functional data (like images, sound, and such) should be at least shareable), but I just want to know why the changes related to this difference weren't made to the stable version? What's the reasoning for holding it? I know there's no consensus, but can you describe the points where the opinions
Everything in AtOmXpLuS