As for the compliance testing project I don't see the benefit of this
since most projects already have issue trackers of there own. Just
report the protocol compliance issues in those trackers so that they get
tracked together with other bugs of that software. Imho, a protocol
compliance issue shouldn't be handled differently than other bugs.
The difference is that Jabber clients are created, maintained, and run in completely different trackers for different people, some will even be developed as closed source.
Compliance issues affect *everyone* in the Jabber community, rather than just affecting the users of that particular client. Users of the particular client may even begin to think that Jabber itself is broken when they attempt to communicate with users of other clients, depending on the exact protocol issue.
I didn't think I needed to argue the case for public compliance testing to the JSF, but I guess I do...
As for the <show>online</show> stuff, yeah, thanks for the replies, but that was an example, not my point.
Julian
_______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
