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 15:44:57 +0900
- From: "Stephen J. Turnbull" <stephen@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>
Bruno Raoult writes: > > Moreover, if someone gave a technical talk, I don't think > > TLUG "owns" the materials. No, they don't. By the Berne Convention, the author owns the presentation and all the supporting materials. For spontaneous recorded speech (eg, Q&A), the speker owns his or her words. > > 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. (But it's rude to do that. Good luck getting favors from me in the future if I catch you using my material without telling me first, and in idiomatic American that's normally expressed as a request for permission such as "I hope you won't mind if ...". N.B. The answer in idiomatic American is nearly forced to be "of course not", but some people are jerks.) > I was hoping that people making a speech would make it "free" > (as "free speech"), as well as supporting documents... 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. > PS. It is interesting to see some technical TLUG video on Youtube, > Video (including presentations by Stephen). But no support available... > So video is public, and *only* video... > Public, or not public?? No, it's not "public". It's owned by the author(s). 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. > PS. I am no more living in Japan, so I am surely not at the right place > to discuss "politics", but, except in case of external speakers, who could > have some reasons to preserve some rights, wouldn’t a good idea to > publish all the support documents? 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.
- 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: Bruno Raoult
- Re: [tlug] 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
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] Tokyo ISP recommendations
- Next by Date: Re: [tlug] But too much logs kills the logs: How to Grok Logs
- 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