Open Stack

I like this approach.

On Wed, May 4, 2011 at 1:19 PM, Ant Messerli <amesserl at rackspace.com> wrote:

> So it sounds like the better path would be to just keep two channels for
> now, see how that goes, and then maybe revisit splitting out by project if
> it comes to that in the future?
>
> #openstack - Help and Support
> #openstack-dev - All Openstack Development
>
> Anyone should be able to participate in any channel, so if someone wanted
> to learn by osmosis, they could still join the dev channel.  I just think
> there's quite a bit of repetition in the main #openstack channel from
> users setting up Openstack and that by separating the channels, it might
> be easier to parse depending on what project is being worked.  The Swift
> guys still might be overwhelmed a bit from all the Nova talk.
>
>
> -Ant
>
>
> On 5/4/11 1:29 AM, "Christian Berendt" <berendt at b1-systems.de> wrote:
>
> >> Can't we just have a #openstack-dev to cover them all ?
> >
> >+1
> >=
>
>
>
> Confidentiality Notice: This e-mail message (including any attached or
> embedded documents) is intended for the exclusive and confidential use of
> the
> individual or entity to which this message is addressed, and unless
> otherwise
> expressly indicated, is confidential and privileged information of
> Rackspace.
> Any dissemination, distribution or copying of the enclosed material is
> prohibited.
> If you receive this transmission in error, please notify us immediately by
> e-mail
> at abuse at rackspace.com, and delete the original message.
> Your cooperation is appreciated.
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20110504/30e36aa9/attachment.html>