Cool. Well, I am hanging out in all the channels anyway. Once I find out who the Group Contact is for Freenode is, I will hand over the registration.
As for #cloudstack-private, it would be used for the sort of thing we use private@ for. Typically quite low volume. But sometimes IRC is better for collaboration on issues. And sometimes you want to do it in private. :) On Thu, Sep 20, 2012 at 2:14 PM, Chip Childers <[email protected]>wrote: > On Thu, Sep 20, 2012 at 5:49 AM, Noah Slater <[email protected]> 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 > > I had suggested #cloudstack-meeting to avoid getting in the way of > user interactions on #cloudstack, so I have no issue with switching > that over to #cloudstack-dev. > > > 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. > > +1 - keep that one where it is > > > 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.) > > +1 - I'm good with this change > > > -private should have an ACL that matches private@, and -security is > just a > > suggestion. > > I'm not sure that the PPMC needs a channel. Do you guys use this > frequently for couchdb? > > > We have a security@ list on CouchDB, but it may be premature for CS. > > John, you had discussed starting up a security team. Any further > thoughts on that? > > > Is the #cloudstack namespace registered? If not I can probably help to > > expediate the GCF registration at Freenode. > > David, do you know? > > > If it is, who is the group contact? > > > > Thanks, > > > > -- > > NS > -- NS
