Jump to content

Rosetta Code talk:Copyrights: Difference between revisions

Line 55:
::: Hmm? No, I mean the copyright concern. Assuming Abu is the author of said book, how many picolisp examples on RC are not written by Abu? Even though code he released on RC is under CC (or is it GFDL?), he ''himself'' can still use his own code however he pleases, such as publishing somewhere else without mentioning RC. Unless you do find in his book substantial code written by other RC users, there's no reason be be concerned about. --[[User:Ledrug|Ledrug]] 07:50, 2 September 2012 (UTC)
:::: I was contacted beforehand for advice. It's my understanding that all of the code examples were written by Abu, so I believe it's fine. I've also been asked to write a forward for "PicoLisp by Example", which I intend to get around to today. --[[User:Short Circuit|Michael Mol]] 10:08, 2 September 2012 (UTC)
 
The book has around 600 task descriptions copied just about verbatim from RC. Each section of the book begins with the task description and yet only Alexander Burger and Thorsten Jolitz are cited as authors. No attempt seems to have been made to even inform RC contributors of the existence of the book prior to publication.
 
Personally, If they had acknowledged that the task descriptions take time and expertise to create and are NOT authored by them, added an explanation of how to look at authorship through RC page histories and added links to each task page from every task they had used (in the style of some of their RC external links that they have left in), then that may help; but they seem to have concentrated merely on the examples they may have written in PicoLisp and, maybe by ommision, they claim authorship of the task descriptions too. --[[User:Paddy3118|Paddy3118]] 10:53, 2 September 2012 (UTC)
 
P.S. doesn't the license state that some attempt at stating authorship needs to be given? --[[User:Paddy3118|Paddy3118]] 10:53, 2 September 2012 (UTC)
Anonymous user
Cookies help us deliver our services. By using our services, you agree to our use of cookies.