[Members] Feature list

Abhinav Singh mailsforabhinav at gmail.com
Tue Sep 4 18:39:17 UTC 2012


+1

Our goal must be to automate things at XSF end. It can be done manual or
automatic on server/client vendor side (since they want XSF to advertise
their code/library). With proper workflow in place, it won't be too tough
for server/clients vendors (who write thousand line of code) to automate
this little info for XSF. Once done we all can focus on more important
tasks and not bother about periodic review of such comparison tables.

A few attributes that we can ask vendors (extending what Dave suggested):

   1. url to xep specs - can be a link to
xmpp.org/extensions/xep-xxxx.htmlor a custom url assuming server is
implementing a custom spec of it's own
   (details of which are yet available on xmpp.org)
   2. version - xep's have their own versioning, it's important to know
   what version a particular server support
   3. state - alpha, beta, stable or we can come up with new terms which
   define this best
   4. official name

If we agree to go ahead with this, there can be more attributes which will
help us automate things on our end and which can be helpful for the xmpp
community overall.

Regards,
------------------------------------------------------
Abhinav Singh,
Bangalore, India
http://abhinavsingh.com
------------------------------------------------------


On Tue, Sep 4, 2012 at 11:38 PM, Dave Cridland <dave at cridland.net> wrote:

> This is more or less what Kim and I were discussing, but the idea was that
> the XSF would define what the tags might mean, and explicitly not verify
> them.
>
> Canonical instances don't really work because that means first supporting
> some new protocol to say what's supported - some things just won't map to
> the kinds of features we want. For example, you'll never be able to query
> an exclusively anonymous domain to see it supports XEP-0175.
>
> I'm happy for vendors (client and server both) to submit a URI we feed
> into the system, which hosts a file containing the claimed feature tags -
> and probably the official name, version, and URIs for human consumption,
> why not.
>  On Sep 4, 2012 7:00 PM, "Abhinav Singh" <mailsforabhinav at gmail.com>
> wrote:
>
>> We already have a list of XMPP servers listed here:
>> http://xmpp.org/xmpp-software/servers/ . Each listed server have it's
>> own destination url. Will it be possible to ask server vendors (when they
>> request XSF to list there server on this page) to have relevant meta tags
>> on destination url indicating what XEP's  and XMPP features they support. A
>> bot can then be set to collect this info periodically (end of every day)
>> and update comparison table as and when required.
>>
>> To take into account concerns raised by Kevin over how stable those
>> features are, we can ask server vendors to include a custom attribute which
>> says "alpha", "beta", "stable", .... for each supported feature. I
>> understand setting this up will require some initial effort, but once in
>> place this will become smooth and automated.
>>
>> This surely needs to be automated (if possible).
>> Otherwise this becomes a never ending task for XSF.
>>
>> Regards,
>> ------------------------------------------------------
>> Abhinav Singh,
>> Bangalore, India
>> http://abhinavsingh.com
>> ------------------------------------------------------
>>
>>
>> On Tue, Sep 4, 2012 at 11:09 PM, Tuomas Koski <koski.tuomas at gmail.com>wrote:
>>
>>> Hi,
>>>
>>> On 4 September 2012 16:42, Kim Alvefur <zash at zash.se> wrote:
>>> > Hi!
>>> >
>>> > So, Dave suggested something like this[1] could be hosted on the XSF
>>> > site.  What do other people think?
>>>
>>> +1
>>>
>>> Cheers,
>>> --
>>> Tuomas
>>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/members/attachments/20120905/e3039a8c/attachment.html>


More information about the Members mailing list