[Jenkins-infra] Slack for Jenkins project?

[Craig Rodrigues]

HipChat would be a logical choice, because the Jenkins CI project
uses a lot of Atlassian products.  However, there are some comparisons
out there between Slack and Hipchat that are worth looking at,
and at least the few I've seen, Slack comes out ahead:

https://www.google.com/search?q=slack+vs+hipchat

--
Craig

On Thu, Jun 11, 2015 at 11:48 PM, Adam Papai <apapai at cloudbees.com> wrote:

> or use HipChat. They have a Free plan as well.
>
> https://www.hipchat.com/admin/pricing
>
>
> On Fri, Jun 12, 2015 at 4:37 AM, Craig Rodrigues <rodrigc at freebsd.org>
> wrote:
>
>> Hi,
>>
>> Would the jenkins-infra team be interested in setting up an
>> official "jenkins-ci" community on Slack?
>>
>> Slack is very similar in its interface to IRC, but has a very
>> nice "modern" interface, accessible via web browser,
>> OS X application, IOS/Android app.
>>
>> Slack has an API and many people are integrating applications with it
>> such as Google Hangouts, Dropbox, and even Jenkins itself:
>>
>> https://slack.com/integrations/
>>
>> In terms of pricing, I think that the Jenkins project can get
>> by with the free pricing tier:
>>
>> http://slack.com/pricing/
>>
>> which offers unlimited users, 5 integrations, and 10,000 searchable
>> messages.
>>
>> A number of open source projects such as Socket.IO, Wordpress,
>> EmberJS have set up Slack communities, and have moved away
>> from freenode IRC and are generally happy with it:
>>
>> https://www.google.com/search?q=open+source+projects+using+slack
>>
>> I'm not suggesting that Jenkins CI project gets rid of IRC,
>> but since it is possible to use Slack for free, why not
>> set it up, and see how it goes for end users?
>>
>> --
>> Craig
>> _______________________________________________
>> Jenkins-infra mailing list
>> Jenkins-infra at lists.jenkins-ci.org
>> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20150612/ad229c4b/attachment.html>