getkaiwa / kaiwa

[UNMAINTAINED] A modern XMPP Web client
http://getkaiwa.com
MIT License
1.34k stars 154 forks source link

Is kaiwa alive? #96

Open Senset opened 7 years ago

Senset commented 7 years ago

Hello! I'm trying to install kaiwa on Ubuntu 14.04 Server and have some problems with it. On step "npm install". So before paste logs \ debugs I want to know: is Kaiwa alive (still have a people who can help?)

jbreitbart commented 7 years ago

Are there any good alternatives?

Senset commented 7 years ago

I'm using Jappix now (https://github.com/jappix/jappix). Installed on Ubuntu 14.04 Server, apache2+php v.5.5.9+prosody 0.9.10 via BOSH. My server not in production, still testing... Seems to be OK (Only haves slows by getting shared roster (250+ users))

djmaze commented 7 years ago

Notice: the Jappix project is no longer maintained. We still accept PR (Pull Requests) though.

Senset commented 7 years ago

Yep! But it works from box... that can not be said about the kaiwa, bcs my skills very low for nodejs (and npm) yet. And kaiwa creates more questions for me, like: "node server" command - how to create a service for it (cron via root... etc)? why it needs ldap lib (some manuals tells it: http://freedif.org/kaiwa-modern-xmpp-web-client/)? And more for talk: (imho) many users haves problem with install it (see the comments on link above)

djmaze commented 7 years ago

Yes, Kaiwa is also hardly maintained.

I believe Movim is the successor to Jappix. Probably worth trying it out.

Senset commented 7 years ago

Thx, I'll try

rzr commented 7 years ago

what about xmpp bridge for matrix.org ?

jarbro commented 7 years ago

Looks like this fork of Kaiwa is still getting development https://github.com/ForNeVeR/Kaiwa

jcrben commented 6 years ago

The README was updated to point out that it is unmaintained - looks like ForNeVeR's work is mostly happening on the develop branch https://github.com/ForNeVeR/Kaiwa/tree/develop

alexanderadam commented 4 years ago

@digicoop / @maximebf / @sebu77 maybe it would make sense to create an organisation (i.e. kaiwacommunity or kaiwachat or so).

You could add developers like @ForNeVeR, @albjeremias or @patelvanita360 to it and move this project including it's website to that organization.

This way the website wouldn't point to the unmaintained project. :wink:

Because as an end user it is pretty difficult to chose from various and changing forks.

Or otherwise it might be better just to directly switch to converse.js (and maybe apply a fancier theme to it) because it supports even encryption with OMEMO.

rzr commented 4 years ago

If there is any traction to have this project community maintained check: https://github.com/abandonware/abandonware.github.io/issues/5

Nyco commented 4 years ago

Hey @all, good idea @alexanderadam and @rzr, maybe we can send a call for community maintenance? Probably, sometihng will happen?... :)

ForNeVeR commented 4 years ago

Probably it would be better to develop a new client based on the same underlying stanza.io, but built with more modern tech. Old good Kaiwa, while truly old and good, is hardly maintainable I'd say.

alexanderadam commented 4 years ago

Kaiwa, while truly old and good, is hardly maintainable I'd say.

Okay, good to know.

Probably it would be better to develop a new client

What's wrong with existing clients like converse.js? It's actively maintained and has modern features. The default design is not my taste although you can theme it by using the mockup.

maximebf commented 4 years ago

Indeed we can create an organization. But as mentioned, I believe it has become hard to maintain and a major update of the dependencies would be needed.

ForNeVeR commented 4 years ago

converse.js looks very cool. If it supports modern tech, then I'd suggest that all possible Kaiwa contributors better focus their attention on it :)

alexanderadam commented 4 years ago

@maximebf / @sebu77 could you please pin this issue?

Otherwise people somehow still seem to ignore that this project is unmaintained (although it should IMHO be clear by the README).

Maybe it would also be better to change the title of this issue to something like kaiwa is UNMAINTAINED or so.

Senset commented 4 years ago

@alexanderadam, lol I start that issue while unmaintained status wasn't declared in readme. And now we know: it's dead =)

alexanderadam commented 4 years ago

@Senset I guess you misread my issue. :wink: I just wrote the comment because issues like 107 were referenced last month and people who might stumble about it might won't see that this project is unmaintained.

Your issue on the other hand is probably the (only) one that's still relevant. :wink: So I would actually keep it open so that others can see that the project is unmaintained.

Senset commented 4 years ago

Okay

Neustradamus commented 4 years ago

Thanks for some messages about kaiwa, it will be nice to move to another organization...

rzr commented 4 years ago

Are any current maintainer able to join this org: https://github.com/abandonware and then transfer the project (to keep history) ?

Any volunteer to help reviewing/merging pending patches ?

maximebf commented 4 years ago

The project has been moved to a new dedicated org. @Neustradamus is an owner of this org.