Add DOAP usage

[melvo]

There is no overview of XEPs ejabberd supports. It could be solved by creating a DOAP file which can be rendered in order to create an overview page.

Here are the needed steps:

1. Create a DOAP file like QXmpp's DOAP file
2. Update the DOAP file URL in xmpp.org's listing

Once your changes are merged and deployed, you should see the supported XEPs after clicking Show Supported XEPs on ejabberd's overview page.

[melvo]

@weiss Here is the issue we talked about :)

[badlop]

Erlang modules in ejabberd use a custom module attribute -protocol to define what XEPs and RFCs that module implements (and general protocols are listed in ejabberd.erl). This was first implemented in 0c725b5. I am not aware this was used anywhere, it was just simply defined for our human knowledge and consulting.

Now in 4542bcb I've written a script that extracts this information from -protocol attribute and generates ejabberd.doap. It includes protocol number, protocol version, and in what source file it is declared.

I've pushed this URL to xmpp.org git repository as you explained, and now this information is listed in XMPP Servers: ejabberd

It doesn't fill the status (partial | complete), software version, or any other arbitrary comment about the implementation. Maybe that could be defined as additional, optional arguments in the -protocol attribute.

That would require a smarter script to parse properly the -protocol attribute. Let's keep this issue open to track that improvement.

[badlop]

Ok, now the script that extracts information from modules into ejabberd.doap can parse status, software version and comments. I also added version information since 2014. All those news will appear in xmpp.org when the website gets automatically updated in the next days I guess.

[melvo]

@badlop Really great, thanks!