Version 1.1 of the definition has been released. Please help updating it, contribute translations, and help us with the design of logos and buttons to identify free cultural works and licenses!
Talk:Definition/Unstable: Difference between revisions
m (.) |
mNo edit summary |
||
Line 30: | Line 30: | ||
Joseph Potvin | Joseph Potvin | ||
. | . |
Revision as of 06:23, 9 August 2020
)
fnash
fnash
.fnash
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.
DRAFT: http://freedomdefined.org/User:Jpotvin/Free-Libre-Open_Hardware_Definition
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.
Regards,
Joseph Potvin
.
Expire of licenses if break
Some licenses, that are declared as free, expire, if you break them. I can't see that this restriction is allowed. -- David23x (talk) 10:55, 1 October 2015 (EDT)
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
[AtOmXpLuS](https://atomxplus.com)