incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wade Chandler <wadechand...@apache.org>
Subject Re: Incubator chat on Hipchat?
Date Fri, 04 Nov 2016 11:04:43 GMT
Personally I tried gitter as GitHub was to come on-site at work, and
planned to use it, and the experience was quite horrible. Look at its app
reviews; I tend to agree with the low ones which get into its UX and
usability. Even creating a room or finding existing groups didn't seem to
work well (or at all) on mobile; at least Android. I may need to watch some
tutorials on it, but at least with Slack things just work; I agree the
limits etc can be annoying and working around them with bots or not relying
on logs etc. HipChat is OK from my experience, but Slack is unrivaled, but
certainly can be subjective.

Wade

On Nov 4, 2016 3:48 AM, "Stian Soiland-Reyes" <stain@apache.org> wrote:

> I think for external chats we should rather recommend Gitter, which has
> open rooms (anonymous lurking allowed) and "unlimited" searchable logs (and
> unlimited number of users) and don't require workarounds with a sign up
> bot.
>
> We did the same for Taverna, we tried an IRC chat, but its synchronous
> nature and lack of modern web support meant it was not too useful as we
> span timezones across the globe. We tried HipChat, but it somehow didn't
> kick off.
>
> Now that we tried Gitter (https://gitter.im/apache/taverna) we've seen a
> large increase in brainstorming and developer activity (and have to keep
> more of a watch to actively push decisions back to list. :-)). I think its
> email notifications is a good way to lure people back (or scare away!).
>
> The downside is that participation requires login with Twitter or GitHub,
> which some communities might have reasonable objections to.
>
> On 4 Nov 2016 2:33 am, "Wade Chandler" <wadechandler@apache.org> wrote:
>
> > For the NetBeans community we had been using IRC, but then setup Slack,
> and
> > it has seen an uptick over IRC which per logging and notifications had
> been
> > harder to support and stay connected. We setup a sign up bot at
> > https://netbeans.signup.team, and we also have a chat room
> hooked/bridged
> > to our IRC channel, so we service both as a collective; good on mobiles
> > too. We have as an item to talk to Slack about OSS and
> limits/restrictions.
> >
> > We don't intend it to replace mailing lists, Jira, nor the wiki, but look
> > at it as dynamic chats and community building allowing to have hack,
> help,
> > or real time hang time sessions. We didn't know about the Apache HipChat,
> > but I must confess I much prefer Slack having used both during my day
> job.
> >
> > Wade
> >
> > On Nov 3, 2016 10:50 AM, "Marvin Humphrey" <marvin@rectangular.com>
> wrote:
> >
> > > On Wed, Nov 2, 2016 at 3:23 PM, John D. Ament <johndament@apache.org>
> > > wrote:
> > >
> > > > Infra recently started leveraging hipchat.  A few PMCs have made use
> of
> > > > it.  I was wondering, would it be beneficial to anyone if we setup an
> > > > incubator room in hipchat?
> > >
> > > How about just promoting the #asf IRC channel on freenode.net?
> > >
> > >   https://kiwiirc.com/client/irc.freenode.net/#asf
> > >
> > > Better for podling contributors to make connections to the wider ASF
> > > rather than to limit themselves to the current incubator, and the #asf
> > > channel is already well established.
> > >
> > > We could even embed the Kiwi IRC client in an iframe on the Incubator
> > > website, at say http://incubator.apache.org/chat alongside guidance
> > > documenting how we expect real-time communications to be used.
> > >
> > > <iframe src="https://kiwiirc.com/client/irc.freenode.net/#asf"
> > > style="border:0; width:100%; height:450px;"></iframe>
> > >
> > > Marvin Humphrey
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> > >
> >
>

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