[jitsi-dev] Decoupling jitsi-meet XMPP modules

Archive
#1

There are a few references to the UI and the global APP object in xmpp.js
and some of the other xmpp related modules. Is there any interest in
decoupling those to make the XMPP modules not depend on the UI at all? I'm
willing to do the work, but would that effort be supported/welcome?

Devin Wilson

#2

Hello Devin,

ยทยทยท

On Wed, May 27, 2015 at 5:47 AM, Devin Wilson <dmwilson6@gmail.com> wrote:

There are a few references to the UI and the global APP object in xmpp.js
and some of the other xmpp related modules. Is there any interest in
decoupling those to make the XMPP modules not depend on the UI at all? I'm
willing to do the work, but would that effort be supported/welcome?

Yes, sure ! A pull request will be welcome.

Please note that once we're at that point we'll need you to sign, scan
and send to us our contributor agreement[1] before we can merge.

[1]: http://bluejimp.com/bca.pdf

Regards,
Pawel

#3

Thanks for the reply Pawel! A couple other questions:

Would you guys be open to publishing the javascript modules from jitsi-meet
as a library to npm?

I'm thinking of adding some unit tests as well to add confidence around the
refactoring and would be willing to contribute those. Is there a preferred
place for those? A few options that come to mind: a separate repo, test dir
in jitsi-meet, beside source in jisti-meet.

Devin

There are a few references to the UI and the global APP object in xmpp.js
and some of the other xmpp related modules. Is there any interest in
decoupling those to make the XMPP modules not depend on the UI at all? I'm
willing to do the work, but would that effort be supported/welcome?

Devin Wilson