On 09/01/15 12:11 -0800, Joshua Harlow wrote:
So the only comment I'll put in is one that I know not everyone agrees with but might as well throw it out there.

http://freenode.net/channel_guidelines.shtml (this page has a bunch of useful advice IMHO).

From that; something useful to look/think over at least...

If you're considering publishing channel logs, think it through. The freenode network is an interactive environment. Even on public channels, most users don't weigh their comments with the idea that they'll be enshrined in perpetuity. For that reason, few participants publish logs.

If you're publishing logs on an ongoing basis, your channel topic should reflect that fact. Be sure to provide a way for users to make comments without logging, and get permission from the channel owners before you start. If you're thinking of "anonymizing" your logs (removing information that identifies the specific users), be aware that it's difficult to do it well—replies and general context often provide identifying information which is hard to filter.

If you just want to publish a single conversation, be careful to get permission from each participant. Provide as much context as you can. Avoid the temptation to publish or distribute logs without permission in order to portray someone in a bad light. The reputation you save will most likely be your own.

(Joshua, the below is not about what you posted, I really appreciate
you bringing the above into the discussion)

FWIW, I kind of feel that channel logging should become an OpenStack
thing and not a per-project thing. Log all openstack "official"
channels, make it clear in the
wiki/homepage/HoToContribute/WhateverYouWannaCallIt and move on.

Nothing, absolutely nothing, prevents the above from happening right
now. I've local (as in my ZNC server) logs of the last 1y 1/2 and I
could just make them public.

Really, IRC is basically(?) public by default and I - I know this is
probably personal opinion - don't think there's a difference between a
logged channel and a not logged one. If we wanted to make the channel
private, we should password protect it and invite few people, make
them sign a contract where they swear they won't publish logs and

Anyway, I think a good way to avoid these discussions for future
projects is to simply enable logging on all openstack- channels.


Brian Rosmaita wrote:
The response on the review is overwhelmingly positive (or, strictly
speaking, unanimously non-negative).

If anyone has an objection, could you please register it before 12:00
UTC on Monday, January 12?


*From:* David Stanek [dsta...@dstanek.com]
*Sent:* Wednesday, January 07, 2015 4:43 PM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [Glance] IRC logging

It's also important to remember that IRC channels are typically not
private and are likely already logged by dozens of people anyway.

On Tue, Jan 6, 2015 at 1:22 PM, Christopher Aedo <ca...@mirantis.com
<mailto:ca...@mirantis.com>> wrote:

   On Tue, Jan 6, 2015 at 2:49 AM, Flavio Percoco <fla...@redhat.com
   <mailto:fla...@redhat.com>> wrote:
   >  Fully agree... I don't see how enable logging should be a limitation
   >  for freedom of thought. We've used it in Zaqar since day 0 and it's
   >  bee of great help for all of us.
   >  The logging does not remove the need of meetings where decisions and
   >  more relevant/important topics are discussed.

   Wanted to second this as well. I'm strongly in favor of logging -
   looking through backlogs of chats on other channels has been very
   helpful to me in the past, and it sure to help others in the future.
   I don't think there is danger of anyone pointing to a logged IRC
   conversation in this context as some statement of record.


   OpenStack-dev mailing list

blog: http://www.traceback.org
twitter: http://twitter.com/dstanek
www: http://dstanek.com

OpenStack-dev mailing list

OpenStack-dev mailing list

Flavio Percoco

Attachment: pgp_rNqy0Akht.pgp
Description: PGP signature

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to