[jitsi-dev] Jitsi Android Questions (Ingo Bauersachs)


#1

Hi,

I have no intention of keeping aTalk as close source. I have once offer to release the source as Jitsi library via Pawel Domas in Sep 2015; but required to sign an agreement which I am not comfortable with. aTalk source will be released to the community once it is in a more stable condition, hopefully other community can then contribute to the project.

I apologize to mention aTalk in your forum. However it is not for any personal gain, but hope more public community will help to do beta testing and make aTalk a better application. Like jitsi, I am only an individual would like to contribute to the community.

Sorry for any inconvenience cause to the forum members

Regards

···

-----Original Message-----
From: dev [mailto:dev-bounces@jitsi.org] On Behalf Of dev-request@jitsi.org
Sent: Thursday, January 12, 2017 5:02 AM
To: dev@jitsi.org
Subject: dev Digest, Vol 46, Issue 45

Send dev mailing list submissions to
  dev@jitsi.org

To subscribe or unsubscribe via the World Wide Web, visit
  http://lists.jitsi.org/mailman/listinfo/dev
or, via email, send a message with subject or body 'help' to
  dev-request@jitsi.org

You can reach the person managing the list at
  dev-owner@jitsi.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of dev digest..."

Today's Topics:

   1. Re: Jitsi Android Questions (Ingo Bauersachs)
   2. Re: Jitsi Android Questions (Ingo Bauersachs)
   3. [jitsi/jitsi-videobridge] mvn: Updates ice4j. (#395) (bgrozev)
   4. Re: [jitsi/jitsi-videobridge] mvn: Updates ice4j. (#395)
      (Дамян Минков)
   5. Re: Restrict access to authorized users for Jitsi Meet
      (Daniel Bareiro)

----------------------------------------------------------------------

Message: 1
Date: Wed, 11 Jan 2017 19:32:44 +0100
From: "Ingo Bauersachs" <ingo@jitsi.org>
To: "'Jitsi Developers'" <dev@jitsi.org>
Subject: Re: [jitsi-dev] Jitsi Android Questions
Message-ID: <002301d26c39$1a35b9f0$4ea12dd0$@jitsi.org>
Content-Type: text/plain; charset="utf-8"

Hi

aTalk-android development is a fork based on jitsi-android.

I have just released a aTalk version 0.7.2 based on the latest Smack
version 0.4.2-rc (SNAPSHOT). aTalk is now able to support
XEP-0077:In-Band Registration and XEP- 0158:CAPTCHA Forms for captcha
protected online registration. If anybody of you is interested; the
released android apk is free and can be downloaded from:
http://atalk.sytes.net/releases/atalk-android/aTalk-release.apk

Note: the aTalk is still in beta release, and support only XMPP protocol.

Although the Apache License doesn't require you to publish the source code, we would appreciate it if you'd do so. In particular, the upgrade of Smack to 4.2 would be most welcome in Jitsi.

It really doesn't matter whether it's still in alpha/beta or whatever you want to call it. Please also note that some used libraries that aren't originally from Atlassian are GPL/LGPL/Eclipse licensed and mandate to release the source code if you modify them.

If you keep it closed source however, I don't think it's very appropriate to promote it on this list.

Regards,
CM Eng

Ingo

------------------------------

Message: 2
Date: Wed, 11 Jan 2017 19:35:45 +0100
From: "Ingo Bauersachs" <ingo@jitsi.org>
To: "'Jitsi Developers'" <dev@jitsi.org>
Subject: Re: [jitsi-dev] Jitsi Android Questions
Message-ID: <002401d26c39$86090740$921b15c0$@jitsi.org>
Content-Type: text/plain; charset="us-ascii"

I'm new to the list and I have a few questions about the discontinued
Jitsi Android port.
[...]
Why was this abandoned?

There was no viable business case for it and required to much work that was better spent on Jitsi Meet at the time.

[...]
Any feedback/status/reasons/red flags?

If someone from the community wants to pick up on development, they can.
Similar as to what cmeng did - it's just unfortunate that the source code of his work is unavailable.

Thank you very much
Adrian

Ingo

------------------------------

Message: 3
Date: Wed, 11 Jan 2017 11:39:58 -0800
From: bgrozev <notifications@github.com>
To: jitsi/jitsi-videobridge <jitsi-videobridge@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [jitsi-dev] [jitsi/jitsi-videobridge] mvn: Updates ice4j.
  (#395)
Message-ID: <jitsi/jitsi-videobridge/pull/395@github.com>
Content-Type: text/plain; charset="utf-8"

You can view, comment on, or merge this pull request online at:

  https://github.com/jitsi/jitsi-videobridge/pull/395

-- Commit Summary --

  * mvn: Updates ice4j.

-- File Changes --

    M pom.xml (2)

-- Patch Links --

https://github.com/jitsi/jitsi-videobridge/pull/395.patch
https://github.com/jitsi/jitsi-videobridge/pull/395.diff

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/jitsi-videobridge/pull/395
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jitsi.org/pipermail/dev/attachments/20170111/4dabd0f8/attachment-0001.html>

------------------------------

Message: 4
Date: Wed, 11 Jan 2017 12:10:13 -0800
From: Дамян Минков <notifications@github.com>
To: jitsi/jitsi-videobridge <jitsi-videobridge@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [jitsi-dev] [jitsi/jitsi-videobridge] mvn: Updates ice4j.
  (#395)
Message-ID:
  <jitsi/jitsi-videobridge/pull/395/issue_event/919707668@github.com>
Content-Type: text/plain; charset="utf-8"

Merged #395.

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jitsi/jitsi-videobridge/pull/395#event-919707668
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jitsi.org/pipermail/dev/attachments/20170111/5c074762/attachment-0001.html>

------------------------------

Message: 5
Date: Wed, 11 Jan 2017 17:56:40 -0300
From: Daniel Bareiro <daniel-listas@gmx.net>
To: dev@jitsi.org
Subject: Re: [jitsi-dev] Restrict access to authorized users for Jitsi
  Meet
Message-ID: <146035a7-a8a3-0d55-8415-e83648ff21c9@gmx.net>
Content-Type: text/plain; charset="utf-8"

Hi again.

On 07/01/17 15:11, Daniel Bareiro wrote:

I am thinking of using Jitsi Meet for the purpose of giving training
classes. For this I would like to restrict access only to the user
who will be the teacher and the students who have taken that course.

Is there any way to do this?

Investigating, I found this article [1], but I did not find the
moderator.js file on my installation from Jitsi Meet repositories for
Debian packages.

[1]
http://www.tothenew.com/blog/authorizing-creationentrance-of-a-confer
ence-in-jitsi/

In the mentioned scenario I think it would be good to have:

a) Users who have permissions to create conference rooms.
b) Users who have permission to participate in a specific conference room.

Is this possible? Is there any documentation to accomplish this? I was
researching but I still have not found a way to implement it.

I have made some progress with this and now all users are prompted for username and password. For this I have read this [1] document (Secure Domain).

Now I just need to get some kind of permissions for each user. Users who have permissions to create a new conference room, and users who can only join to a specific conference room (for example, userA and userB can only join to ConferenceX, and userC and userD can only join to ConferenceY).

Is this possible? I would appreciate any guidance/recommendation.

Thanks in advance.

Kind regards,
Daniel

[1] https://github.com/jitsi/jicofo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.jitsi.org/pipermail/dev/attachments/20170111/1c3e7dc4/attachment.sig>

------------------------------

Subject: Digest Footer

_______________________________________________
dev mailing list
dev@jitsi.org
http://lists.jitsi.org/mailman/listinfo/dev

------------------------------

End of dev Digest, Vol 46, Issue 45
***********************************


#2

Hi,

···

On Wed, Jan 11, 2017 at 4:41 PM, cmeng.gm <cmeng.gm@gmail.com> wrote:

Hi,

I have no intention of keeping aTalk as close source. I have once offer to release the source as Jitsi library via Pawel Domas in Sep 2015; but required to sign an agreement which I am not comfortable with. aTalk source will be released to the community once it is in a more stable condition, hopefully other community can then contribute to the project.

As far as I know you don't have to sign anything in order to release
the source on Github on your own fork/project. If I understand things
correctly you would only have to sign it in order to have it merged
with jitsi/jitsi-android project.

Regards,
Pawel


#3

I have no intention of keeping aTalk as close source.

Then please simply push it to Github.

I have once offer to
release the source as Jitsi library via Pawel Domas in Sep 2015; but
required to sign an agreement which I am not comfortable with.

That is unfortunate, but ultimately your decision.

aTalk source
will be released to the community once it is in a more stable condition,
hopefully other community can then contribute to the project.

As I said, there's no reason to hold back. You couldn't have continued with the development if BlueJimp had only would it after it was "finished". And it's simply not how open source works.

As far as I know you don't have to sign anything in order to release
the source on Github on your own fork/project. If I understand things
correctly you would only have to sign it in order to have it merged
with jitsi/jitsi-android project.

That is correct.
What one cannot do in any case is publishing something under the name Jitsi (e.g. in the play store). This isn't an issue if you continue naming it aTalk. You can also (but this isn't required) name you repo on Github aTalk.

Regards,
Pawel

Ingo