Future of jabberd2 about jabberd2 HOT 6 OPEN

@smokku May I ask, if we can create a new release for jabberd2? I would volunteer to create one.

from jabberd2.

Building a release is trivial. I will do it.
(Also, you don't have my PGP key to generate the signatures ;-) )

• Cleanup configure.ac and the build system.
• Find a way to fuse the four daemons router, sm, c2s, s2s into one daemon called xmppd and add support for standard features of daemons like e.g. setuid. Add optional systemd support.

You may want to take a look at https://github.com/smokku/jabberd3/tree/master/src

from jabberd2.

Thank you. I will take a look at the link. I will also create more patches for configure.ac and probably for some things I mentioned in this bug report.

One question is openssl. I would strongly suggest to at least require 1.0.2, but this will require people to use a more recent distribution that Ubuntu 14, which is used in the Travis CI tests.

from jabberd2.

Please do.
I have no problem in adding repo write rights to the people submitting consistently good PRs.

And if you live up to your promises, I will gladly transfer the ownership of jabbed2 organization to you. :)

from jabberd2.

Any news?

from jabberd2.

I am sorry, but its too much work. I took another look at the code and I am quite sure, it is a lot more work than I thought. A great part of the code needs to be rewritten. Others need to contribute to keep support for Windows and other Unix-like OS working. I only use Linux. I guess everybody should switch to prosody or other xmpp servers. I guess, it would even be easier to write a new xmpp in c from scratch than to update jabberd2. jabberd2 should clearly be marked as unmaintained and people should be told not to use it anymore.

from jabberd2.