Log #openstack-nova in Eavesdrop

Bug #1282629 reported by Scott Devoid
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure
Opinion
Medium
Unassigned

Bug Description

This is a proposal to start logging #openstack-nova conversations in Eavesdrop.

In order for this to happen, "the channel founders or other responsible parties need to ask to have it logged" (fungi).
I think in this case the nova PTL would be the responsible party for making the determination.

Revision history for this message
Russell Bryant (russellb) wrote :

I actually prefer not to have it logged.

Revision history for this message
Russell Bryant (russellb) wrote :

If enough people want it though, I don't care enough to -2 it. I do see that we're logging most other channels. I'm not sure how useful it really is, though.

http://eavesdrop.openstack.org/irclogs/

Revision history for this message
Burt Holzman (holzman) wrote :

+1 to have it logged. Lots of useful conversation happens there.

Revision history for this message
Clark Boylan (cboylan) wrote :

Marking this incomplete as it was not clear from Russell's comment if this should be enabled or not. Can the nova folks make a decision and update this bug? Thank you.

Changed in openstack-ci:
status: New → Incomplete
importance: Undecided → Medium
Revision history for this message
Sean Dague (sdague) wrote :

I'm +1 on logging. Mostly because a decent amount of design discussion that doesn't ever make it to the mailing list happens in the IRC channel, and it's good to have the history.

I think it's also completely valid to decide that we actively push people out from the channel and into the list for design discussions, and leave this more as the hangout channel.

Revision history for this message
Russell Bryant (russellb) wrote :

Cool, can others with an opinion one way or the other leave it here as feedback? I'm happy to go with what most people want on this.

Revision history for this message
Scott Devoid (scott-devoid) wrote :

I submitted this bug during the operators mini-summit while we were discussing the problem of operators tracking design decisions. With the blueprint process moving to nova-specs, I see less of a need to log IRC. I would just hope that any useful conversations in IRC result in artifacts in gerrit or mailing lists.

So I'm +0 on it at this point.

Revision history for this message
Andrew Laski (alaski) wrote :

I also prefer to not have it logged. The channel has a casual tone to it and I think we've been good about pushing anything that gets serious out the the mailing list. Essentially, I don't want to worry that something said in chat can be taken as a design decision since opinions can go back and forth relatively quickly.

Revision history for this message
Dan Smith (danms) wrote :

I'm -1.5 on logging #openstack-nova. Scrollback comes from running a proxy.

Revision history for this message
Matt Riedemann (mriedem) wrote :

-1

Revision history for this message
Michael H Wilson (geekinutah) wrote :

I'm -1 on this. I echo Andrew's sentiment.

Revision history for this message
Mathew Odden (locke105) wrote :

-1

Revision history for this message
Shawn Hartsock (hartsock) wrote :

-1 ... a number of people have a hard enough time sharing opinions on IRC as it is. If we make the channel searchable from the likes of Google that just makes it *even more* intimidating for those people. If you do need logging ... more logged meeting rooms and more formal discussion rooms are in order.

Revision history for this message
Scott Devoid (scott-devoid) wrote :

I think there are enough -1's out there to close this as wontfix. For folks wanting logs for personal use, ZNC [1] was reccomended during the nova meeting [2].

[1] http://wiki.znc.in/ZNC
[2] http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-03-27-21.00.html

Changed in openstack-ci:
status: Incomplete → Opinion
Revision history for this message
Russell Bryant (russellb) wrote :

I brought this up one week ago in the Nova meeting and asked those with an opinion to weigh in. I agree that the comments here mean we should leave it not logged.

Thanks for the comments, everyone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.