[Telepathy] [Bug 13157] support flag to indicate whether MUC subject is writable

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=13157


Simon McVittie <simon.mcvittie at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|telepathy at lists.freedesktop.|simon.mcvittie at collabora.co.
                   |org                         |uk
                URL|http://xmpp.org/extensions/x|http://git.collabora.co.uk/?
                   |ep-0045.html#disco-roominfo |p=user/smcv/telepathy-
                   |                            |gabble-
                   |                            |smcv.git;a=shortlog;h=refs/h
                   |                            |eads/08-subject
           Keywords|                            |patch
          QAContact|                            |telepathy at lists.freedesktop.
                   |                            |org




--- Comment #2 from Simon McVittie <simon.mcvittie at collabora.co.uk>  2009-10-22 10:33:35 PST ---
I have a branch for this. Not tested against a real server yet...

Comments in the branch describe how this is actually implemented in servers, in
practice (I looked at the source code of recent versions of Openfire, Tigase,
ejabberd and mu-conference; plus Prosody, which currently lets absolutely
anyone set the subject).

muc#roominfo_changesubject isn't actually implemented anywhere as far as I can
tell.

muc#roomconfig_changesubject is widely implemented, but it's ambiguous what it
should mean. In the branch I assumed that the server is Openfire, Tigase or
ejabberd, in which this setting is the difference between "you must be a
moderator" and "you must be a participant or moderator".

In mu-conference this setting is actually the difference between "you must be
an admin" and "anyone can set it"; due to us assuming the other interpretation,
users will find that Gabble won't let them change the subject with role
'visitor', only with 'participant' or 'moderator', even though it would
actually work.

This is not a regression, at least, since Gabble previously had a bug in which
it only ever allowed moderators to set the subject, despite a special case
designed to avoid that restriction...

I'm not sure whether this is a candidate for 0.8 or not, so to be safe, I
developed the branch against 0.8.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.