Regarding the advancement (to Final) of some XEPs, here's my opinion (as a developer/user of your XEPs):
 
184 Delivery Receipts could be clear about the message type, which must be used for receipts, although no type implies "normal".
 
224 Attention: No concerns for Final. I also find it useful, e.g. if you want to request user attention by making the dock icon bounce on Mac or making the Window blink in Windows' taskbar.
 
198 Stream Management: As far as I know it has been rarely implemented by servers and clients. Are you sure it's mature enough?
 
280 Message Carbons: I've only read it, not implemented it. I only wondered, why it is only used for chat messages. We use XMPP to send "normal" messages with some extensions and also wanted these messages to get distributed to all other resources, so that all resources are "synchronized". 280 would meet that requirement, but as is, it's only for chat. Otherwise it looks fine.
 
45 MUC: I raised some questions recently and it turned out, that there are some inconsistencies and open issues. So, I'd hesitate to move it to Final.
 
-- Christian
 
 
Gesendet: Freitag, 04. April 2014 um 08:34 Uhr
Von: "Kevin Smith" <[email protected]>
An: "XMPP Standards" <[email protected]>
Betreff: [Standards] Fwd: Minutes 2014-04-02
FYI


---------- Forwarded message ----------
From: Kevin Smith
Date: Fri, Apr 4, 2014 at 7:34 AM
Subject: Minutes 2014-04-02
To: XMPP Council


http://logs.xmpp.org/council/2014-04-02/

1) Roll call
Kev, Matt, Fippo, Lance, Tobias present.

2) Date of next meeting
2014-04-09 15:00 UTC

3) Any other business
No formal items. Discussion of moving more XEPs to Final,
standards-track component protocol and pubsub forms (see room logs for
details).

Fini

Reply via email to