• Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • None

      There is a proposal to create a messaging platform within MusicBrainz (and other MetaBrainz projects) that would allow editors to communicate between each other. It is still unclear what kind of functionality is actually needed and going to be useful.

      Some context:

          [MBS-8721] Messaging platform for editors

          Robert Kaye added a comment -

          We're asking for public feedback on this bug report:

          http://blog.musicbrainz.org/2016/01/29/notifications-and-messaging-in-metabrainz-projects/

          If you care about this ticket, please comment on the blog!

          Robert Kaye added a comment - We're asking for public feedback on this bug report: http://blog.musicbrainz.org/2016/01/29/notifications-and-messaging-in-metabrainz-projects/ If you care about this ticket, please comment on the blog!

          There was some discussion in IRC about dropping the ability for external clients to use the XMPP server: http://chatlogs.metabrainz.org/brainzbot/metabrainz/2016-01-06/?msg=3464354&page=2

          Personally, this is fine to me, since I don't think it's an essential feature that many (any?) people have asked for, and we still have emails.

          But if we're only going to use XMPP to pass messages around within our private LAN, I have to wonder what the point was. The main benefit of XMPP, to me, was that it was interoperable with different client apps. (Are there other important benefits?)

          That seems like an important question to me, because as Gentlecat pointed out, there are a lot of things we need (authentication, storage) that we'd have to implement ourselves on top the of XMPP server anyway.

          Michael Wiencek added a comment - There was some discussion in IRC about dropping the ability for external clients to use the XMPP server: http://chatlogs.metabrainz.org/brainzbot/metabrainz/2016-01-06/?msg=3464354&page=2 Personally, this is fine to me, since I don't think it's an essential feature that many (any?) people have asked for, and we still have emails. But if we're only going to use XMPP to pass messages around within our private LAN, I have to wonder what the point was. The main benefit of XMPP, to me, was that it was interoperable with different client apps. (Are there other important benefits?) That seems like an important question to me, because as Gentlecat pointed out, there are a lot of things we need (authentication, storage) that we'd have to implement ourselves on top the of XMPP server anyway.

          Roman added a comment -

          Marking this as related to MBS-1801, because we might use the same platform to fix both issues.

          Roman added a comment - Marking this as related to MBS-1801 , because we might use the same platform to fix both issues.

          Roman added a comment -

          After some discussion and looking at platforms that can help implement this kind of feature, we decided that XMPP might be a good protocol to use. The alternative was Layer.

          I'm still not sure whether we want to have an actual real-time private chat for editors. Maybe it would be more useful to have more simpler messaging system (like on reddit, for example) even if it's needed at all.

          Another thing to keep in mind is that we encourage open communication. I don't know what editors might want to discuss on MusicBrainz apart from actual editing process. We already have a separate IRC channel for MusicBrainz users (#musicbrainz on Freenode). Perhaps what people actually want is a way to have wiki-style comment sections on entities.

          Roman added a comment - After some discussion and looking at platforms that can help implement this kind of feature, we decided that XMPP might be a good protocol to use. The alternative was Layer . I'm still not sure whether we want to have an actual real-time private chat for editors. Maybe it would be more useful to have more simpler messaging system (like on reddit, for example) even if it's needed at all. Another thing to keep in mind is that we encourage open communication. I don't know what editors might want to discuss on MusicBrainz apart from actual editing process. We already have a separate IRC channel for MusicBrainz users (#musicbrainz on Freenode). Perhaps what people actually want is a way to have wiki-style comment sections on entities.

            Unassigned Unassigned
            roman Roman
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:

                Version Package