incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament" <johndam...@apache.org>
Subject Re: Slack support?
Date Wed, 29 Mar 2017 11:29:07 GMT
Ted,

So far it looks like the key components are:

- Registering the org
- Creating a sign up page/setting up a valid domain name for emails.

I would recommend the sign up is ASF committers only.  After that, its all
automated (similar to hipchat). Assuming that we create a single org, and
limit the automatic registrations to @apache.org then I think there's
really not much extra administration effort.

I wouldn't mind listing my name as a contact for such a need, and having
back ups on other email lists (e.g. creating a slack-admin@apache.org list)

John

On Tue, Mar 28, 2017 at 11:12 AM Ted Dunning <ted.dunning@gmail.com> wrote:

> A single org would be fine if we have foundation-wide buy-in and central
> administration.
>
> We don't have that now, so individual organizations makes more sense.
>
>
>
> On Tue, Mar 28, 2017 at 5:03 AM, John D. Ament <johndament@apache.org>
> wrote:
>
> > 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.dunning@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 <gstein@gmail.com> wrote:
> > >
> > > > On Wed, Mar 22, 2017 at 9:59 PM, Evan Hughes <wisebaldone@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
> > > >
> > >
> >
>

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