I feel like its a bit different.  I would rather see one apache
organization (and would expect users would see this as well).  I don't mind
if the call is to use separate accounts, but feel like it makes more sense
as a single organization.

On Thu, Mar 23, 2017 at 1:56 AM Ted Dunning <ted.dunn...@gmail.com> wrote:

> If you have a podling who wants to use slack, have them register under
> their podling name and deal with it. No impact on infra needed. It's like
> having yet another twitter account.
>
>
>
>
>
> On Wed, Mar 22, 2017 at 10:18 PM, Greg Stein <gst...@gmail.com> wrote:
>
> > On Wed, Mar 22, 2017 at 9:59 PM, Evan Hughes <wisebald...@apache.org>
> > wrote:
> >
> > > Another option could be asking infra to host a rocket.chat server so we
> > can
> > > control the instances.
> > >
> >
> > Sorry, Evan, but hosting a chat service is not an option for
> > Infrastructure. That would be contrary to our work on consolidating
> > services.
> >
> > We can have HipChat rooms for any/all projects. A simple Jira request,
> and
> > you're all set.
> >
> > In short, the ASF is happy to have duplicative topics/projects because
> each
> > community may approach a problem in different ways, with different
> focuses.
> > But our Infra resources are limited, so we can't/won't stand up duplicate
> > services. And even better when they can be outsourced (like HipChat, and
> > increasingly GitHub).
> >
> > Cheers,
> > Greg Stein
> > Infrastructure Administrator, ASF
> >
>

Reply via email to