[ 
https://issues.apache.org/jira/browse/OPENMEETINGS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431737#comment-13431737
 ] 

Vieri edited comment on OPENMEETINGS-399 at 8/9/12 11:16 AM:
-------------------------------------------------------------

I'm not a legal expert and I'm not sure how the licence works but the 
openmeetings files I'm attaching are NOT part of the OenMeetings source tree 
but are to be compiled within the Jitsi source tree. I don't think there are 
any legal issues so I'm just posting the patches here and hopefully someone 
will include them in OM SVN. Whether people will then compile it within Jitsi 
or not and under which licence is up to them.

In fact, I think that the Jitsi devs were at some point interested in merging 
the openmeetings-jitsi plugin into the Jitsi source tree.
                
      was (Author: vieri):
    I'm not a legal expert and I'm not sure how the licence works but the 
openmeetings files I'm attaching are NOT part of the OenMeetings source tree 
but are to be compiled within the Jitsi source tree. I don't think there are 
any legal issues so I'm just posting the patches here and hopefully someone 
will include them in OM SVN. Whether people will then compile it within Jitsi 
or not and under which licence is up to them.
                  
> jitsi openmeetings plugin
> -------------------------
>
>                 Key: OPENMEETINGS-399
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-399
>             Project: Openmeetings
>          Issue Type: Improvement
>            Reporter: Vieri
>            Priority: Minor
>         Attachments: OpenmeetingsConfigManager.java.diff, 
> OpenmeetingsConfigPanel.java.diff, OpenmeetingsPluginActivator.java.diff, 
> OpenmeetingsPluginMenuItem.java.diff, OpenmeetingsPluginSoapClient.java.diff, 
> openmeetingsplugin.manifest.mf.diff
>
>
> I'm attaching several patches for the Jitsi OpenMeetings plugin (against SVN 
> r1370136).
> New features:
> - enables provisioning properties
> - allows the user to force/set conference room ID instead of getting an 
> available room
> - allows the user to set a "display name" instead of the SOAP login user name 
> (in conjunction with provisioning it can be easy to set useful "display 
> names" based on one or more parameters such as client IP/MAC address, 
> "username" provided to Jitsi, corporate database lookup or even LDAP, etc.)
> - SOAP password is stored and loaded via 
> net.java.sip.communicator.service.credentialsstorage
> Fixes:
> - adapts to libjitsi/jitsi
> - createInvitationUrl should not hardcode "openmeetings" in the invitation URL
> - property names changed from plugin.openmeetings.* to 
> net.java.sip.communicator.plugin.openmeetings.* (for coherency)
> - displays Jabber chat window only when invitation URL has correctly been 
> generated
> - handles a null exception when no rooms are available in openmeetings
> New properties for resources.properties (not included in attached patches):
> plugin.openmeetings.DISPLAYED_NAME=Displayed name
> plugin.openmeetings.ROOM_ID=Room ID
> Sample PHP provisioning script:
> echo "net.java.sip.communicator.plugin.openmeetings=\${null}\n";
> echo "net.java.sip.communicator.plugin.openmeetings.DISABLED=false\n";
> echo "net.java.sip.communicator.plugin.openmeetings.DISPLAYED_NAME=My full 
> name\n";
> echo 
> "net.java.sip.communicator.plugin.openmeetings.SERVER=openmeetings.mydomain.org\\:5080\n";
> echo 
> "net.java.sip.communicator.plugin.openmeetings.PROTOCOL_PREFIX=http\\://\n";
> echo 
> "net.java.sip.communicator.plugin.openmeetings.OM_URI_CONTEXT=/webmeetings/\n";
> echo "net.java.sip.communicator.plugin.openmeetings.LOGIN=SOAPusername\n";
> echo "net.java.sip.communicator.plugin.openmeetings.PASSWORD=thisIsAsecret\n";
> echo "net.java.sip.communicator.plugin.openmeetings.ROOM_ID=3\n";
> Hopefully the code can be improved, merged into the official tree and be 
> useful to others.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to