Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] But too much logs kills the logs: How to Grok Logs
- Date: Mon, 11 Jun 2012 11:35:46 +0200
- From: Bruno Raoult <braoult@example.com>
- Subject: Re: [tlug] But too much logs kills the logs: How to Grok Logs
- References: <CAJA1Y2YMkk_5zub8HbUEXD-wenEmmGSOaB0nauhkT2+C97CVmA@mail.gmail.com> <87ehpvbvkj.fsf@uwakimon.sk.tsukuba.ac.jp> <CAJA1Y2ZCPbkPBU62mekMD1KvyuDgVoOxgS6517MKYu=h1w6Tew@mail.gmail.com> <20120605145534.6f24728f.jep200404@columbus.rr.com> <CAJA1Y2Yq9_3LSZAS1eLnu4JSy_75ZfSNpWkBefnaTp+ajbNAGA@mail.gmail.com> <20120605154738.586f7b77.jep200404@columbus.rr.com> <20120606145549.87d4443b7ef3027aecd9ad51@kinali.ch> <C6696B71-F057-425B-A83B-7761D963BAFE@gmail.com> <CAAhy3dvHgto-QZdOU6OBqhm2g567xDJvvUtHaSiGOET=ZyADuQ@mail.gmail.com> <CAJA1Y2bXfffdMB1SvGT5_x0cAXU52qexUG5yT8XkSwQg3smTZQ@mail.gmail.com> <4FD2FEBB.60404@gmail.com> <CAJA1Y2bmc_WuYxfbEtRkNg_sR846pBBv8BvdKhaRtkFVvM21-Q@mail.gmail.com> <4FD38142.4020701@gmail.com> <CAJA1Y2Y=CcOjcefXrxQVtUsK3ofnQhX0P=xexBX9k-UwUqO1LQ@mail.gmail.com> <4FD3EA4A.9010201@gmail.com> <CAJA1Y2ZyK2E4ETZQBFWncJNgPkGQJ2qx4fZ9ub23jXXeqOw9wg@mail.gmail.com> <4FD4E4A1.6040904@gmail.com> <CAJA1Y2YczjSAZGoD9uH1Z1WhLmg-2HgvBufPdgighV6gXGukYg@mail.gmail.com> <87d3568hzq.fsf@uwakimon.sk.tsukuba.ac.jp>
Hi Stephen,On Mon, Jun 11, 2012 at 8:44 AM, Stephen J. Turnbull <stephen@example.com> wrote:> > So, if you're thinking you can just go to TLUG and download> > things and translate them without asking the person who made
> > them, then you might be making a mistake...Ray
If one thinks that having it on TLUG means permission is given, it's
definitely a mistake. If one thinks that TLUG speakers are unlikely
to complain if one assumes that permission would be given, but doesn't
bother to get it, that's probably not a mistake.
In fact, I said I would give back a copy of the translated version.
Would this scenario work (I mean being acceptable):
- I get a version of the document
- I translate it
- I send the translated version of the document to the owner (and probably ask some questions
about unclear points)
- *After* reviewing it, the owner gives me (or not) the permission to use this version
in my local LUG meeting
- If the answer is "no", this is finished
- It it is "yes", well, somebody will do his/her best to make a correct presentation with the support
(surely after getting more information on the subject: nobody can discuss a subject without getting some
knowledge on it :-)
> I was hoping that people making a speech would make it "free"
Not a chance with my stuff; it's at best CC-BY-NC (Creative Commons
license with the "by attribution" and "no commercial use" clauses
invoked -- the latter makes it non-free). Supporting documents, I'd
probably do if asked, in most cases.
Thanks for that.No, it's not "public". It's owned by the author(s).
> Public, or not public??
Sorry, the term "public" was nor right.
It's probably
technically copyright infringement to put it up on YouTube, but since
that's been the practice for a while TLUG can probably argue that they
have grounds to assume permission. Of course, if they don't have it
in writing and the speaker complains, the video will be taken down.
Sure.
How would you suggest doing that? The speakers generally show up with
either a notebook or a USB stick, and leave with it. TLUG doesn't
have access to the documents in the first place.
I would suggest: Publish all support documents on TLUG, with appropriates warnings
and rights in them (such as what you can find in GPL). The ideal place could be attached on every
TLUG meeting announcement page, or a separate one (not sure what is the best).
The ideal situation would be to have the support document *and* the video (to understand
how the owner made it).
From then, and after all approvals from owner, the translated version would be also published
on TLUG with all information about owner (maybe translators' name added, so people could tell
if something is wrong in a few terms).
And all LUGS could use this same page as reference (links, and not copies), with all modified
versions (translated in my case).
This seems fair for me. Is there something wrong in this process?
Bruno.
PS. I think video and support documents are very different: For the first one, I understand the owner issue.
For the second, I am less sure. If the speaker allows a video to be taken, who is the real owner? You start
to make me afraid about all my holidays pics and videos, hehehe :-) In France, everybody could have *any*
video in which they appear taken off from any public space. We saw that with Google Street, and I understand this.
But this is about privacy (as opposed to ownership).
PPS. My initial question was about keeping knowledge flowing. I did not think at all it would be so difficult :-)
If I know something, I surely want people to know about it too (this is the way we -human- came to where we are today).
And my knowledge is surely not *mine*. I did not discover that earth was not flat :) Sharing is the magic word, isn't it?
--
2 + 2 = 5, for very large values of 2.
- Follow-Ups:
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: Josh Glover
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: Raymond Wan
- [tlug] Copyright and preserving TLUG presentations [was: ...How to Grok Logs]
- From: Stephen J. Turnbull
- [tlug] pictures and publishing (was: But too much logs kills the logs: How to Grok Logs)
- From: Attila Kinali
- References:
- [tlug] Help on a script...
- From: Bruno Raoult
- [tlug] Help on a script...
- From: Stephen J. Turnbull
- Re: [tlug] Help on a script...
- From: Bruno Raoult
- [tlug] But too much logs kills the logs (was Re: Help on a script...)
- From: jep200404
- Re: [tlug] But too much logs kills the logs (was Re: Help on a script...)
- From: Bruno Raoult
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: jep200404
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: Attila Kinali
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: Braoult
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: Raymond Wan
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: Bruno Raoult
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: Raymond Wan
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: Bruno Raoult
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: Raymond Wan
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: Bruno Raoult
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: Raymond Wan
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: Bruno Raoult
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: Raymond Wan
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: Bruno Raoult
- Re: [tlug] But too much logs kills the logs: How to Grok Logs
- From: Stephen J. Turnbull
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] narisumashi mail?
- Next by Date: Re: [tlug] Tokyo ISP recommendations
- Previous by thread: Re: [tlug] But too much logs kills the logs: How to Grok Logs
- Next by thread: Re: [tlug] But too much logs kills the logs: How to Grok Logs
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links