[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Wiki Usage
- From: Man Kein Hong <mkh@...>
- Date: Sun, 15 Oct 2006 18:33:06 +0800
Quoting John Belmonte <john@neggie.net>:
> Man Kein Hong wrote:
> > The best way of doing this will be to add a proper documentation
> license
> > to the Lua wiki. [snip]
> >
Sorry about pointing the discussion in this direction. My phone line is
currently down and in my haste, I did not trawl the archives for past
discussions. If you were offended, sorry, I was just throwing an idea
into the air to see what the list's reaction is.
Personally, I have no preference either way; there are always responsible
ways of using or utilizing the wiki's information [in indirect ways] that
does not infringe on people's rights. I wasn't going to embark on a
crusade or anything, so, relax, calm down... :-)
> [snip]
> I really don't regret having no license and no sign-in mechanism on the
> wiki from the start. I view the wiki as graffiti on a public wall. If
> someone wants to sell photographs of the wall they can at their own
> risk. I like the freedom of public walls and free paint, and should
> the
> community insist this change I may regretfully wash my hands of
> lua-users.org.
Perhaps an item in the wiki front page would be helpful. The wiki has a
vast amount of useful information, and such questions will surface again,
because people will want to utilize the information in some way. In a way,
the creation of more information or documentation about Lua is good, but
running into obstacles like this is bad. We should avoid having such
invisible obstacles.
So, to avoid issues like this going kaboom in the future, the wiki should
have a clear notice somewhere about the status of the material and does
the job of disclaiming everything, i.e. everything is at the risk of the
party who wants to use the material. I looked around the wiki for a bit,
I didn't see one. I apologise profusely in advance if there actually is
one that I did not find. ;-)
> As I've advised in the past [1], it's best to keep this can of worms
> shut.
Another alternative would be for the tutorial project to contact some of
the main writers of the tutorials, so at least some sections (where
authorship can be clearly, absolutely, absolutely established) can be
used with a minimum of changes, with authorship attribution if required,
so no one is deprived of anything and nothing goes kaboom.
Cheers,
--
khman
KL, MY
----------------------------------------------------------------
This e-mail has been sent via JARING webmail at http://www.jaring.my