[Bug 17219] Allow to set priority for available/away state

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=17219

--- Comment #8 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
Not sure why it didn't make it onto this bug, but Rob suggested a while ago
that the ideal thing would be for Gabble to adjust its priority automatically,
rather than needing explicit configuration or hard-coded priority numbers, with
these goals:

A. Gabble's priority is >= 0 (so we get messages at all)

B. Gabble's priority is lower than the priorities of any resources with
   a presence that is "more available" than Gabble's

C. Gabble's priority is higher than the priorities of any resources with
   a presence that is "less available" than Gabble's

D. If it isn't possible to satisfy A, B and C simultaneously, work out
   which is most important (I would guess A > B > C)

(for some definition of "more available": perhaps a very simple one, (chatty ==
available) > (away == busy == xa), or perhaps something more complicated.)

I seem to remember Google Talk has, or had, a good algorithm for that?

For that to happen, someone who uses multiple resources will need to write a
patch, and more importantly, justify why it's correct.

If someone wants to write a comprehensive patch for the simpler "offer some
configurable priorities" version, I wouldn't say no to that, but it will have
to cover all the statuses (perhaps just by dividing them into broad categories,
"available/chatty" and "away/busy") and have sensible defaults.

I'm sure the current "our priority is always the same" approach is pretty bad
for many use-cases, but it's at least easy to understand/describe :-)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.