From b25e9f775ebf7591b4feff2bbcbf47cc2e874f09 Mon Sep 17 00:00:00 2001 From: Steve Kille Date: Wed, 2 Nov 2016 10:22:39 +0000 Subject: [PATCH] Resolve questions on future capabilities. --- xep-0369.xml | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/xep-0369.xml b/xep-0369.xml index b8017fe8..e846fb48 100644 --- a/xep-0369.xml +++ b/xep-0369.xml @@ -2092,21 +2092,17 @@ Allowed and Banned lists may be read by PubSub query of the Banned and Allowed N

- &xep0045; describes how to convert from a 1:1 chat to a MUC room. Conversion from 1:1 chat is a straightforward and useful capability, that is not described in this version of the MIX specification. Options that may be considered in the future are: + &xep0045; describes how to convert from a 1:1 chat to a MUC room. Conversion from 1:1 chat is a straightforward and useful capability, that is not described in this version of the MIX specification. This capability may be added in a future version of this XEP or as separate XEP. +

-
    -
  1. Describe in a new separate XEP.
    2. -
  2. Describe in an updated version of this XEP.
    3. -
  3. Do not specify in a XEP and leave to implementer.
    4. -
-

QUESTION: Input on these choices is solicited. Dave Cridland votes for new XEP.

+

- &xep0045; defines a mechanism so that MUC moderators can control who is able to send messages to a MUC room using a "voice" mechanism. The current version of MIX does not include this. + &xep0045; defines a mechanism so that MUC moderators can control who is able to send messages to a MUC room using a "voice" mechanism. The current version of MIX does not include this. This might be added to a future version of this XEP or as a separate XEP if this capability becomes an agreed requirement.

-

AUTHOR'S NOTE AND QUESTION: Input on the desirability of adding voice control to MIX is solicited. It would appear reasonably straightforward, and probably be achieved by adding two additional nodes to the MIX channel.

+