[Tkabber as an example]
Stop bashing Aleksey's client already, will ya. ;-D
a 'recommended' feature might end up being a 'required' feature the next year
I wonder: will there be any way to include _customer_ expectations in the decisions of what will be listed in the certification feature requirements, or will this rely entirely on the experience and/or personal judgements of those Jabber community members assigned with assembling said list?
Don't get me wrong, I'm not talking "classic market research" here ;) ; but IMHO the overall direction of Jabber should _not_ be based _solely_ on the decisions of technically inclined folks (like us Jabber developers), either.
GreetinX,
Jochen.
-- "Our gut-level distaste for something new is less about our reaction to the thing in question than it is about our fears of abandoning the familiar and comfortable." -- Andy Ihnatko
_______________________________________________ jdev mailing list [EMAIL PROTECTED] https://jabberstudio.org/mailman/listinfo/jdev
