Hash: SHA1

On 02/18/2015 05:07 PM, Michael Krotscheck wrote:
> You got my intention right: I wanted to understand better what
> lead some people to create a private channel, what were their
> needs.
> I'm in a passworded channel, where the majority of members work on 
> OpenStack, but whose common denominator is "We're in the same 
> organizational unit in HP". We talk about openstack, we talk about
> HP, we talk about burning man, we talk about movies, good places to
> drink - it's a nice little backchannel of idle chatter. There have
> been a few times when things related to OpenStack came up, and in
> that case we've booted the topic to a public channel (There was an
> example just yesterday). Either way, in this case a private channel
> was created because we could potentially be discussing corporate
> things, it's more analogous to your Teams' internal Hipchat or IRC
> server (in fact, it started in HipChat, and then we were all 'why
> do we have to use another chat client' and that ended that).
> So there's one use case.
> Michael

I think the use case is very valid. I think most (all?) companies have
internal channels. That said, those should be concerned about
downstream only work and burning men. If an upstream topic arises,
people should have discipline to move discussion to upstream channels.
AFAIK that's what we try to do in Red Hat, and I guess it's a valid
approach that helps both a company in question to get attention to
issues downstream teams are interested in, and the community.

Version: GnuPG v1


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

Reply via email to