Uploaded image for project: 'Request For Comments'
  1. Request For Comments
  2. RFC-140

Replacing Hipchat with Slack as chat solution

    XMLWordPrintable

    Details

    • Type: RFC
    • Status: Implemented
    • Resolution: Done
    • Component/s: DM
    • Labels:
      None

      Description

      This RFC covers the proposal of adopting Slack for our chat platform (in lieu of hipchat).

      The current user arguments in favour are:

      • User preference (as expressed frequently to me) due to familiarity with other projects using Slack
      • More finely tuned notifications, client read message synchronisation (mobile/desktop) and similar superior usability features
      • Perceived poor performance of Hipchat (in terms of service availability, connection management, buggy clients)

      The community support arguments are:

      • Interface with standard protocols (IRC, XMPP) and fee structure make it more approachable to eg. students needing urgent help rather than the more "gatekeeper" model required from hipchat
      • The adoption trend seems to favour Slack, so likely to be more popular as we onboard more external collaborators in the coming yers

      The SQuaRE arguments in favour are:

      • More actively supported integrations platform
      • An opportunity to normalise chat usernames to match Github usernames, which would simplify implementation of a much requested feature to @ users for their build failure notifications
      • No need to cull inactive usernames

      The arguments against are:

      • Disruption of change
      • No 1:1 video facility

      RFC Process:

      • There is a separate question of whether to join Slack with the free (but limited history search) plan, or the per-user plan with unlimited history plan (which would still need some gatekeeping). The argument is that the successful introduction of Discoursed-base c.l.o should lead us to treating chat as a more transient platform and flush substantive conversations to Discourse.
      • In the event this RFC passes, implementation needs to lag until SQuaRE can move the current integrations (eg. Jenkins) over.
      • Despite a SQuaRE preference for Slack for the reasons stated, we feel like a minor stakeholder in this questions compared to user preference. Also, this RFC affects more users than typical. For this reasons, I encourage you to fill this poll unless you really want to add something to the arguments.

      https://www.surveymonkey.com/r/R5TKNBB

      Poll Results as of 2016-02-12 (see [^Data_Q1_160212.pdf] attachment):

      "I actively prefer Slack","36.4 %"
      "I actively prefer Hipchat","4.5 %"
      "I don't mind, let the people who care choose","50.0 %"
      "I don't have a preference but don't want to have to change.","9.1 %"

      Answers: 22

        Attachments

        1. Data_Q1_160225-2.pdf
          28 kB
        2. Data_Q2_160225.pdf
          28 kB
        3. Slack.png
          Slack.png
          85 kB

          Activity

          Hide
          frossie Frossie Economou added a comment -

          Steve Ritz absolutely, as mentioned in the RFC I consider this an important feature

          Show
          frossie Frossie Economou added a comment - Steve Ritz absolutely, as mentioned in the RFC I consider this an important feature
          Hide
          gpdf Gregory Dubois-Felsmann added a comment -

          I see from http://bluejeans.com/support/release-notes that BlueJeans has integrations for both Slack and Hipchat. That may help address the lack of direct video support once we move to Slack.

          Show
          gpdf Gregory Dubois-Felsmann added a comment - I see from http://bluejeans.com/support/release-notes that BlueJeans has integrations for both Slack and Hipchat. That may help address the lack of direct video support once we move to Slack.
          Hide
          gpdf Gregory Dubois-Felsmann added a comment -

          Slack released its audio chat support this week:

          https://slackhq.com/calls-come-to-slack-ad333ce98acf

          Anyone can make one-on-one calls, while paid teams can also make group calls in any channel or group DM. When someone initiates a call, a message will appear, inviting you to join the call.

          Show
          gpdf Gregory Dubois-Felsmann added a comment - Slack released its audio chat support this week: https://slackhq.com/calls-come-to-slack-ad333ce98acf Anyone can make one-on-one calls, while paid teams can also make group calls in any channel or group DM. When someone initiates a call, a message will appear, inviting you to join the call.
          Hide
          ktl Kian-Tat Lim added a comment -

          I believe this is now a done deal from the project standpoint, so I suggest that it be marked as Adopted after implementation tickets are created.

          Show
          ktl Kian-Tat Lim added a comment - I believe this is now a done deal from the project standpoint, so I suggest that it be marked as Adopted after implementation tickets are created.
          Hide
          tjenness Tim Jenness added a comment -

          We are all using Slack so is this now so we need to work out what needs to be done before this can be marked as implemented.

          Show
          tjenness Tim Jenness added a comment - We are all using Slack so is this now so we need to work out what needs to be done before this can be marked as implemented.

            People

            Assignee:
            frossie Frossie Economou
            Reporter:
            frossie Frossie Economou
            Watchers:
            Andrew Connolly, Brian Van Klaveren, Chris Walter, Dominique Boutigny, Donald Petravick, Frossie Economou, Gregory Dubois-Felsmann, Jason Alt [X] (Inactive), J Matt Peterson [X] (Inactive), John Swinbank, Jonathan Sick, Kian-Tat Lim, Mario Juric, Russell Owen, Simon Krughoff, Steve Ritz, Tim Jenness, Trey Roby
            Votes:
            0 Vote for this issue
            Watchers:
            18 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Planned End:

                Jenkins

                No builds found.