Bug #11702

Define requirements for an XMPP server for our support channel

Added by muri 2016-08-23 12:32:19 . Updated 2019-03-08 15:32:55 .

Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:

Affected tool:
Deliverable for:


Before sending out a call, we should define the requirements for hosting our XMPP support channel


Related issues

Blocks Tails - Feature #11317: Pass a call to host an XMPP server for Tails support Confirmed 2016-04-04


#1 Updated by muri 2016-08-23 12:32:51

  • blocks Feature #11317: Pass a call to host an XMPP server for Tails support added

#2 Updated by sycamoreone 2016-08-23 12:35:58

  • is duplicate of Bug #11686: Replace Pidgin: refine blueprint added

#3 Updated by sycamoreone 2016-08-23 12:36:25

  • has duplicate deleted (Bug #11686: Replace Pidgin: refine blueprint)

#4 Updated by sycamoreone 2016-08-23 12:37:30

Sorry for not reading properly. I didn’t saw that this was about XMPP servers instead of clients.

#5 Updated by muri 2016-08-30 07:13:33

  • Status changed from Confirmed to In Progress
  • Assignee changed from muri to sycamoreone
  • % Done changed from 0 to 20
  • QA Check set to Ready for QA

there are two problems we need to be solved; those problems don’t have to be solved together- this means that these problems can also be solved by two independent servers managed by two independent entities;
first set of requirements:

  • the server MUST provide conference rooms for tails related work; ist MUST be possible for tails contributors to create such conference rooms
  • the server MAY also provider conference rooms for other purposes (meaning: the server does not have to be tails specific)
  • the server MUST provide a way of storing the permissions of conference rooms; permissions are roles, affilations and privileges of jabber ids

the second set of requirements (could be a bit harder to solve):

syscamore, i’m assigning to you for review, i hope thats oke.
one think thats not clear to me is if the torproject setup can work with pidgin? (if so, maybe we should add this as an requirement to the second part)

#6 Updated by intrigeri 2018-03-01 08:10:10

  • Subject changed from Define requirements for an XMPP server to Define requirements for an XMPP server for our support channel

#7 Updated by Anonymous 2018-08-17 15:24:20

  • Assignee changed from sycamoreone to muri
  • QA Check changed from Ready for QA to Pass

Review passes. Not sure where this ticket came from, reassigning to muri for clarification.

#8 Updated by muri 2018-09-01 11:22:48

  • Assignee deleted (muri)

this came from the discussions about moving the support channel from IRC to XMPP. we are using XMPP for (more than?) two years now though only some of the requirements are fullfilled, but apparently we are fine with that (i haven’t heard any negative comments about the choice of XMPP server so far).

i think the ticket and Feature #11317 can be closed (i’m leaving it open though, i’m not confident enough to just close it, but if another set of eyes agrees they can close it or maybe during the triaging…)

#9 Updated by intrigeri 2019-03-08 15:32:55

  • Status changed from In Progress to Resolved
  • % Done changed from 20 to 100
  • QA Check deleted (Pass)