[Jenkins-infra] Slack for Jenkins project?
o.v.nenashev at gmail.com
Fri Jun 12 10:31:42 UTC 2015
+1 regarding community risks. IRC chats are not very helpful, because we
have already splitted the community to mailing lists and chats.
jenkinsci-users mailing list in extremely ineffective, because it's almost
impossible to monitor all messages or to subscribe for a particular area
due to the fat structure we use.
We also cannot migrate the INFRA stuff (Jenkins IRC bot, meetings bot,
etc.) to another chat easily.
I would -1 regarding the chats migration. If we have enough resources, I'd
consider the migration from jenkinsci-users to a forum engine instead.
2015-06-12 12:09 GMT+03:00 Richard Bywater <richard at byh2o.com>:
> No opinion either way but on a more positive side to those kinds of
> services (which I guess could be negative to some people), those services
> tend to be better at catching up with discussions that have happened whilst
> you weren't around.
> With IRC, of course, unless you leave a client connected all the time you
> can't really easily see and respond to previous discussions whereas with
> services like Slack/Hipchat/Flowdock/etc. the whole history is there to see.
> I'd have to (cheekily) argue with the "if you want real time communication
> about Jenkins, #jenkins is where you go" as every time I go there its like
> a ghost town with a lot of nicks hanging around but no answers or talk :)
> (Wonders of being in the NZ timezone I guess...)
> On Fri, 12 Jun 2015 at 20:28 Daniel Beck <ml at beckweb.net> wrote:
>> On 12.06.2015, at 04:37, Craig Rodrigues <rodrigc at FreeBSD.org> wrote:
>> > 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?
>> What about the risk of fragmenting communication in the community?
>> Right now, if you want real time communication about Jenkins, #jenkins is
>> where you go. If we join all kinds of other services, where would you go?
>> It also looks like that requires an account, a further barrier to entry.
>> Jenkins-infra mailing list
>> Jenkins-infra at lists.jenkins-ci.org
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Jenkins-infra