incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <nsla...@tumbolia.org>
Subject Re: IRC channels
Date Thu, 20 Sep 2012 10:21:49 GMT
Again, the focus is on mirroring the lists and the list's respective
purposes. When the channels get a bit more busy, people will start to
appreciate the split.

On Thu, Sep 20, 2012 at 10:57 AM, Lu Heng <h.lu@anytimechinese.com> wrote:

> Hi
>
> I don't think that is a good idea, because now we don't even have a
> very active IRC discussion, split into 3 will make even more quite in
> the discussion.
>
> On Thu, Sep 20, 2012 at 11:49 AM, Noah Slater <nslater@tumbolia.org>
> wrote:
> > Hi,
> >
> > Not sure who runs the IRC channels, so I thought I'd put this here.
> >
> > At the moment we have:
> >
> > #cloudstack
> > #cloudstack-meeting
> >
> >
> > Are there any others that I am missing?
> >
> > Can I suggest that we create channels that map to mailing lists:
> >
> > #clouststack (user)
> > #cloudstack-dev
> > #cloudstack-private
> > #cloudstack-security
> >
> >
> > The main channel is for general user chat and support.
> >
> > The dev channel can be reserved for people hacking on CS itself.
> >
> > (My suggestion stems from wanting to ask a question on IRC about CS
> > organisational stuff, without polluting the main channel.)
> >
> > -private should have an ACL that matches private@, and -security is
> just a
> > suggestion.
> >
> > We have a security@ list on CouchDB, but it may be premature for CS.
> >
> > Is the #cloudstack namespace registered? If not I can probably help to
> > expediate the GCF registration at Freenode.
> >
> > If it is, who is the group contact?
> >
> > Thanks,
> >
> > --
> > NS
>
>
>
> --
> --
> Kind regards.
> Lu
>
> This transmission is intended solely for the addressee(s) shown above.
> It may contain information that is privileged, confidential or
> otherwise protected from disclosure. Any review, dissemination or use
> of this transmission or its contents by persons other than the
> intended addressee(s) is strictly prohibited. If you have received
> this transmission in error, please notify this office immediately and
> e-mail the original at the sender's address above by replying to this
> message and including the text of the transmission received.
>



-- 
NS

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message