Jabber Progress Report discusses how

Jabber Progress Report discusses how the recent complexity is being handled by the Jabber Foundation, the group now responsible for defining the Jabber protocol, and Jabelin, the team now responsible for producing the reference implementation (starting with custody of the current 1.4 server).

Of the six-month goals given therein, here are the ones important to client authors (from the POV of a client author who hasn't finished a truly usable client yet):

  • Document and standardize the new conferencing protocol. I would complain about yet another conferencing protocol, but if it's documented, I think that'll be a different story. Also all the documentation on the old "groupchat" and "conferencing" systems should be thrown out to end the conferencing insanity.
  • Create a project index for clients. Like the existing clients list, only better, sounds like.
  • Establish client development/interface guidelines. Not sure what I think yet.
All of these are certainly good on paper. Client dev/interface guidelines will be interesting to see--does that mean something like the existing Jabber Programmer's Guide that defines a common set of jargon and concepts, or will it be something (reasonably) more like the Macintosh or Java interface guidelines, such as suggesting using this widget for this and that for the other?