Rosetta Code talk:Copyrights: Difference between revisions
→Book: Picolisp by example derived from the site: I told them to sit back. I did get a heads-up. I look like an authority figure. I hoped RC would still get behind this. I think it's good for RC.
(→Book: Picolisp by example derived from the site: What is polite?) |
(→Book: Picolisp by example derived from the site: I told them to sit back. I did get a heads-up. I look like an authority figure. I hoped RC would still get behind this. I think it's good for RC.) |
||
Line 63:
::Hi Michael, thanks for your explanation. I guess the picolisp authors aren't required to join in this discussion either, which is what I would have preferred.
::If ''they'' had given the site a heads-up before publication then I wouldn't be surprised if RC contributors could have helped them in their endeavours. An announcement by them, with a meaningful sub-heading or a user sub-page off their User page, would have got some attention here, but then, they aren't required to do that either. --[[User:Paddy3118|Paddy3118]] 03:45, 3 September 2012 (UTC)
::: I explicitly told them to simply hunker down and code, and that I'd see what I could do on this end. Tempers being as high as they were, it was obvious to me I needed to step in as a moderator/mediator before mixing things up again.
::: They did give ''me'' a heads-up, but I didn't relay the announcement at that time, owing to the extraordinary time crunch I described above.
::: As for whether it was appropriate for them to contact me directly, rather than leaving a note on their user page, the etiquette on that kind of thing is really very unclear. I'm sometimes amazed at how unfamiliar people are with wiki etiquette when I talk with them face-to-face on such things. At the same time, most signs looking for labeled authority on RC lead back to me, so I give the appearance of a single (or, at least, first) point of contact. So perhaps there's a better way for this kind of thing to be handled in the future.
::: I presumed the RC community would still be willing to to lend a hand and get this thing rolling. The infrastructure and effort required to set up a book like this (and the experience gained therefrom) can be turned around and applied to ''every'' language on Rosetta Code, which I saw as a great opportunity to raise awareness of more programming languages, provide more consolidated documentation for some, show off the great work that the RC community as put into creating this corpus, and to highlight editorial need. (Seriously, read through the book; presented in this way, you can see the variance in quality and organization of RC tasks, and it strikes me as a great view to help come up with a better task layout and template.)
::: I really think the RC community should step up and lend a hand, even if only by looking at [[Task Description Authors]] and applying it to each task on RC. The PicoLisp by Example book looks (to me) like a great opportunity to drive improvement on RC, and to bring what we've done to more people (while setting up a framework for doing similar things going forward). --[[User:Short Circuit|Michael Mol]] 13:51, 3 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)
| |||