On Not | Mo Chit

June 17, 2004

Jabber Client Certification
jabbericon.jpg Rachel Blackman raised the issue of client certification on the Jabber Development mailing list. On the surface it sounds like a really good idea, but then Justin Karneges pointed out some problems with the proposed solution. (I'd point to the actual conversation but the Jabber Dev archive isn't up to date, and gmane isn't responsive.)

The problem is that the certified clients proposal would be slam dunk if it weren't for the state of some of the JEPs that are considered essential for a standard Jabber client. Since we're working on a Jabber client full-time, having a certification would be a great badge to set easily set our client apart from the hordes of other clients that haven't been maintained in quite some time. It's also a good way for people to gage the reliability and compatibility with Jabber/XMPP.

My personal gut feeling is that the timing isn't right for certification. Getting to the point of certifying clients is a process not a decision. The first step would be to invest in tools so that clients developers can verify their compliance -- it shouldn't be left to some board member to eyeball compliance. The second step is for everyone to knuckle down and spend some effort getting the essential JEPs standardized before moving on. With those two things out of the way, the Jabber community could easily setup a process for certification.

Creative Commons License
This site is licensed under a
Creative Commons License