Rosetta Code talk:Copyrights: Difference between revisions

Line 75:
: GFDL, CC and various other licenses were designed to promote share and reuse of ideas; getting all worked up as if Abu & Co. were trying to steal your life's work (I'm pretty sure they weren't) is quite contrary to that spirit. Technically it's within your right to demand attribution, but, to me, that doesn't make your desire of being credited wherever possible any less petty.
: (The above are my personal, original opinions; they would normally have been available under the terms of GFDL 1.2 per RC copyright policy, but I hereby release these four paragraphs, including this one, into public domain.) --[[User:Ledrug|Ledrug]] 02:08, 3 September 2012 (UTC)
 
::I have seen it written that book authorship and where your work has been cited is currency in academia, reviewed in job applications and on promotion boards. In computing, job applicants are told that contributions to open source projects help their case. It would have been polite, when you can look at a page of the book and see a task description longer than the picolisp code and which could have taken more effort to put together than the code, it would have been polite if one had known it was coming.
::I have learned and derived pleasure from writing and modifying task descriptions as well as code. I think its good to see their improvement over time, and think they ''are'' of intrinsic value. I cannot say what individual task authors would think, but with so much of the book being RC stuff not written by the picolisp authors then I would think it was blindingly obvious to someone that has an account on the site enough to write all that picolisp, that discussing the use of such text on the site would be a good idea. But they don't have to, and have (still) chosen not to do that. --[[User:Paddy3118|Paddy3118]] 04:27, 3 September 2012 (UTC)
Anonymous user