@frahergal I see. Just wanted to mention that with XMPP it would be convenient for operators/support agents to chat using native desktop and mobile clients. For instance, at [Olark][1] they went this way. We are using their chat for our web-store and we really find XMPP compliance very useful.
@vrms Yes, we want to hear the opinion of the community but also to prioritize with our needs and development ideas. So it will depend on complexity, our work load, etc.
@strixaluco I will have a look at it then! It looks an interesting approach Thank you!
do you have any intention to revive this project and make it work/integrate with the core code? As far as I know this is not a finalized project and has been abandoned by it’s creators. I think a sophisticated chat functionality may be benificial to ERPNext, so if anyone would continue this it would serve a good cause.
As you are new to this community … generally there is a tendency to try to merge everything which is not complete niche functionality to the mainline codebase rather then maintaining many apps (quite the opposite approach then odoo).
I personally am undecided yet whether that’s the best way to go, but it’s the policy of the core team.
That being said … still separate Apps can exist, they will just not be available for users of the hosted (xxx.erpnext.com) instances and someone will have to maintain them so they’ll be working continuously.