andrewtindall wrote:In regards to that last part about public provision - could we suggest that if any bespoke software is to be developed for public sector use, it must be released Open Source / Under GPL? This would address issues like the recent case of Royal Mail sending C&Ds to the company that developed a Postcode Search API without paying for a licence, despite society having already paid once for it via tax, which had a knock-on affect on other services such as JobCentrePlus.
andrewtindall wrote:Ah. number 9 could be interpreted in such a way as to breach privacy, as tax information, terror suspect info, etc. would technically be "procured at public expense" and thus have to be made public. Although it would be nonsensical to conclude this was intended, ambiguity should be as far removed as reasonably possible.
What we want to reform are commercial copyrights and patents. The basic notion of copyrights was always to find a fair balance between conflicting commercial interests. Today this balance is lost and needs to be regained. We say that copyrights need to be restored to their origins.
Copyright was created to benefit society by encouraging creation. Copyright imposes a limited-term monopoly on works (which is against the public interest), in order to provide an incentive for people to create (which is in the public interest).
To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries.
The official aim of the copyright system has always been to find a balance in order to promote culture being created and spread.
duke wrote:andrewtindall wrote:Ah. number 9 could be interpreted in such a way as to breach privacy, as tax information, terror suspect info, etc. would technically be "procured at public expense" and thus have to be made public. Although it would be nonsensical to conclude this was intended, ambiguity should be as far removed as reasonably possible.
I guess it comes down to how easy it is to remove the ambiguity; obviously it could specify "apart from information covered by the Data Protection Act or sensitive for commercial, military or security reasons" - but then this would still be open to interpretation; these days it seems possible to restrict almost anything for "reasons of national security".
andy_r wrote:I think it may be very useful to try and boil the long text above down to just its proposals. As I understand it, the concrete proposals from the working group are (in essence):
2) Copyright duration to be reduced to 5 years for closed source software.
3) Copyright duration to be reduced to 10 years for open source software.
vj wrote:andy_r wrote:I think it may be very useful to try and boil the long text above down to just its proposals. As I understand it, the concrete proposals from the working group are (in essence):
2) Copyright duration to be reduced to 5 years for closed source software.
3) Copyright duration to be reduced to 10 years for open source software.
There was a lot of opposition to treating FOSS in a special way here on the forums. I agree with all the policy proposals except these two. Can someone explain why FOSS should get separate, special, treatment? After all if I write a book and release it under a cc-by-sa licence I don't get this special extension despite contributing to free culture.
Indeed why are we treating software differently to other copyright at all?
andrewtindall wrote:vj wrote:andy_r wrote:I think it may be very useful to try and boil the long text above down to just its proposals. As I understand it, the concrete proposals from the working group are (in essence):
2) Copyright duration to be reduced to 5 years for closed source software.
3) Copyright duration to be reduced to 10 years for open source software.
There was a lot of opposition to treating FOSS in a special way here on the forums. I agree with all the policy proposals except these two. Can someone explain why FOSS should get separate, special, treatment? After all if I write a book and release it under a cc-by-sa licence I don't get this special extension despite contributing to free culture.
Indeed why are we treating software differently to other copyright at all?
I believe it to be related to the fact that many open source licences rely on copyright of at least 10 years to be workable, which is higher than we, and most pirate parties, are proposing as a baseline.
vj wrote:There was a lot of opposition to treating FOSS in a special way here on the forums. I agree with all the policy proposals except these two. Can someone explain why FOSS should get separate, special, treatment? After all if I write a book and release it under a cc-by-sa licence I don't get this special extension despite contributing to free culture.
vj wrote:Indeed why are we treating software differently to other copyright at all?andrewtindall wrote:I believe it to be related to the fact that many open source licences rely on copyright of at least 10 years to be workable, which is higher than we, and most pirate parties, are proposing as a baseline.
That explains the 10yr term for FOSS (effectively giving them their 5 yr extension for free) but why only 5 years for closed source software when every other medium gets 5+5?
johnb wrote:let me perhaps add a couple of points to this, as clarification...
(some snips made for brevity, hope I didn't screw up the quoting too badly!)vj wrote:There was a lot of opposition to treating FOSS in a special way here on the forums. I agree with all the policy proposals except these two. Can someone explain why FOSS should get separate, special, treatment? After all if I write a book and release it under a cc-by-sa licence I don't get this special extension despite contributing to free culture.
(1) To be very clear here:
FOSS is not getting separate, special treatment,...The special treatment is for software released with source code,
johnb wrote:(2) Why is software different?
Because when binary software is released, it is being released, but in a way it's also not being released, or only partially so, if source code is not provided. It is not the same as a book, music, or any other kind of work, and that presents a serious problem once the copyright expires, because the freedoms that would be available with any other kind of work (to reuse, redevelop, rework, etc) are not fully available without source code.
johnb wrote:vj wrote:Indeed why are we treating software differently to other copyright at all?andrewtindall wrote:I believe it to be related to the fact that many open source licences rely on copyright of at least 10 years to be workable, which is higher than we, and most pirate parties, are proposing as a baseline.
That explains the 10yr term for FOSS (effectively giving them their 5 yr extension for free) but why only 5 years for closed source software when every other medium gets 5+5?
There are two reasons I would point out as justification for that:
[snip]
(2) The other reason I can see is that if 10 years was possible for closed programs... Then FOSS (or any software released with source code, but especially FOSS) would be at a disadvantage
5+5 (like everything else) isn't more than 10.johnb wrote:... so do we really want to give any more than 10 years to any kind of software?
vj wrote:Thanks for the clarification john, I'm not 100% convinced (though more so than I was), so I'm going to play devil's advocate and pose some more questions. Not all reflect my opinion, but it's important to have answers for when we get asked these.
vj wrote:There was a lot of opposition to treating FOSS in a special way here on the forums. I agree with all the policy proposals except these two. Can someone explain why FOSS should get separate, special, treatment? After all if I write a book and release it under a cc-by-sa licence I don't get this special extension despite contributing to free culture.
vj wrote:So we're treating OSS in a special way then. Even if we understand the differences between FOSS and OSS, to the general public this is a distinction without a difference. Especially if non-commercial copyright infringement is being legalized. This policy is effectively saying to commercial operators give your source to your FOSS competitors! i.e. What would stop the non-commercial Open office from using MS Office code once non-commercial infringement is legalized?
vj wrote:johnb wrote:(2) Why is software different?
Because when binary software is released, it is being released, but in a way it's also not being released, or only partially so, if source code is not provided. It is not the same as a book, music, or any other kind of work, and that presents a serious problem once the copyright expires, because the freedoms that would be available with any other kind of work (to reuse, redevelop, rework, etc) are not fully available without source code.
We have de-compilers for this very reason. It might be harder, but the people who actually want the source will be able to read it.
johnb wrote:vj wrote:Indeed why are we treating software differently to other copyright at all?
(2) The other reason I can see is that if 10 years was possible for closed programs... Then FOSS (or any software released with source code, but especially FOSS) would be at a disadvantage
So are we are giving FOSS special treatment then?5+5 (like everything else) isn't more than 10.johnb wrote:... so do we really want to give any more than 10 years to any kind of software?
johnb wrote:it's all quite fiddly to think through, and as you also rightly point out, not that relevant to the "mass market" arguments about e.g. music, books, films, etc.
vj wrote:I'm not going to carry out debating point by point because it's starting to become unproductive, however there is one point I'd like to pick up because I just happened to think of it today.johnb wrote:it's all quite fiddly to think through, and as you also rightly point out, not that relevant to the "mass market" arguments about e.g. music, books, films, etc.
The problem here is computer games; very mass market so Software copyright will have to be easily explainable weather we like it or not. If the purpose of software is to "promote the useful arts" IMO shorter software copyrights (in relation to others) will have a detrimental effect on games. Companies won't release the source, they'll go back to releasing games on cartridges. Worse, the games they'll release will be crippled and IMO everyone will move to an EA sports model of releasing the same game every year, with only a couple of changes.
Example:
I bought Mario cart for my DS(phat) near it's release (2005), Nintendo are still selling the same game over 5 years on for the DSi(yes, I bought it). Had the above regime been in place the IMO (this is what I'd do if I was Nintendo and only had a 5yr term) the original game would have had fewer tracks and I'd have released Mario cart 2, Mario cart 3 etc. all exactly the same but different tracks. This would hurt the consumer as prices would remain the same so I'd have had to buy multiple games for the same content, no one would really benefit as all maro characters are trademarked, so my cheap knock-off would look like a cheap knock-off. Also I have no way of getting a cartridge other than by asking Nintendo. A 5+5 term gives Nintendo time to release a new platform, and make people buy the fully featured game + bonus retro tracks for the DS++ that finally stopped supporting original DS carts.
martinbudden wrote:3) Currently under UK law an individual's work is automatically copyright as soon as it is manifest in some physical form (including electronic form). The author does not have to specify it is copyright - it is copyright by default. If the author wishes to place the work in the public domain, then they must explicitly do so (for example by using a creative commons license).
The situation should be reversed. Namely a work should by default be in the public domain and should only be copyright if the author explicitly makes it copyright.
Users browsing this forum: No registered users and 0 guests