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


#1

Hi,

I respect your view what is open source and use of github repository. As I have mentioned in my previous message, I feel that the source is not ready to be released to the community. I am sorry to decline your request at this moment. I will however continue to enhance aTalk and release the apk on regularly basic. The apk will remain free to anyone who wish to use it. Certainly any bug feedback is most welcome to help improve aTalk.

Lastly, I would like to thank the jitsi team excellent effort in developing jitsi.

cmeng

···

-----Original Message-----
From: dev [mailto:dev-bounces@jitsi.org] On Behalf Of dev-request@jitsi.org
Sent: Thursday, January 12, 2017 7:00 PM
To: dev@jitsi.org
Subject: dev Digest, Vol 46, Issue 47

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) (Ingo Bauersachs)

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

Message: 1
Date: Thu, 12 Jan 2017 08:58:18 +0100
From: "Ingo Bauersachs" <ingo@jitsi.org>
To: "'Jitsi Developers'" <dev@jitsi.org>
Subject: Re: [jitsi-dev] Jitsi Android Questions (Ingo Bauersachs)
Message-ID: <002601d26ca9$a35f2480$ea1d6d80$@jitsi.org>
Content-Type: text/plain; charset="utf-8"

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

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

Subject: Digest Footer

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

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

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


#2

Hello,

Thank you for the feedback on my original question about the Android Jitsi. I see a very solid business case for this app - looking at WhatsApp which can send text video and voice is the most popular chat client around. Also, Bria which supports SIP and XMPP and sells a large number of softphones each year on desktop and mobile. My opinion is that Jitsi is/could be even better that Bria or WhatsApp! SIP (video, text, presence) and XMPP (video, video bridge, text, file xfer, presence). There is already more features and one can use their own server. That's pretty great for medium to large sized businesses.

I would love to contribute to the code, but I have not developed in Java for quite a while. It would be pretty nice if the project imported straight into Android Studio - and Android Studio doesn't use Ant. I've always hated the Java build environment LOL

I'm sure I can figure it out, but ^ would be nice.

One thing I would like to contribute is the GEO spec for XMPP and a plugin for desktop Jitsi to interface with the mobile devices (maps, etc...). And also a 'dispatch' feature that would allow a user of the software to see a map of all received GEOs in the last 12 hours. This could give a bird's eye view of which job sites a company's workers are currently located.

To me, Jitsi Android and desktop are the best option for modern communication.

Also, on the topic of aTalk. Your update looks very good. I have read the comments about the source code, but maybe you could shoot me a line? athompson@successos.com

Thanks!
Adrian

···

-----Original Message-----
From: dev [mailto:dev-bounces@jitsi.org] On Behalf Of cmeng.gm
Sent: January 12, 2017 7:46 AM
To: dev@jitsi.org
Subject: [jitsi-dev] Jitsi Android Questions (Ingo Bauersachs)

Hi,

I respect your view what is open source and use of github repository. As I have mentioned in my previous message, I feel that the source is not ready to be released to the community. I am sorry to decline your request at this moment. I will however continue to enhance aTalk and release the apk on regularly basic. The apk will remain free to anyone who wish to use it. Certainly any bug feedback is most welcome to help improve aTalk.

Lastly, I would like to thank the jitsi team excellent effort in developing jitsi.

cmeng

-----Original Message-----
From: dev [mailto:dev-bounces@jitsi.org] On Behalf Of dev-request@jitsi.org
Sent: Thursday, January 12, 2017 7:00 PM
To: dev@jitsi.org
Subject: dev Digest, Vol 46, Issue 47

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) (Ingo Bauersachs)

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

Message: 1
Date: Thu, 12 Jan 2017 08:58:18 +0100
From: "Ingo Bauersachs" <ingo@jitsi.org>
To: "'Jitsi Developers'" <dev@jitsi.org>
Subject: Re: [jitsi-dev] Jitsi Android Questions (Ingo Bauersachs)
Message-ID: <002601d26ca9$a35f2480$ea1d6d80$@jitsi.org>
Content-Type: text/plain; charset="utf-8"

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

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

Subject: Digest Footer

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

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

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

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#3

Thank you for the feedback on my original question about the Android Jitsi.
I see a very solid business case for this app - looking at WhatsApp which can
send text video and voice is the most popular chat client around.

There wasn't a case for BlueJimp back then and there apparently isn't for Atlassian right now. This might change of course, but it isn't up to me.

Whatsapp btw. is very different: they also run the service, not just the app. This is a very important fact: only with running such a service you'd be able to a) gain a substantial user base and b) have a way of generating revenue (e.g. with a service to make landline calls). Just having the app as a paid item in the Play Store wouldn't work: everybody would just install a freely available fork - it's open source after all.

Also, Bria
which supports SIP and XMPP and sells a large number of softphones each year
on desktop and mobile. My opinion is that Jitsi is/could be even better that
Bria or WhatsApp! SIP (video, text, presence) and XMPP (video, video bridge,
text, file xfer, presence). There is already more features and one can use
their own server. That's pretty great for medium to large sized businesses.

I would love to contribute to the code, but I have not developed in Java for
quite a while. It would be pretty nice if the project imported straight into
Android Studio - and Android Studio doesn't use Ant. I've always hated the
Java build environment LOL

I'm sure I can figure it out, but ^ would be nice.

Give it a try :slight_smile:

One thing I would like to contribute is the GEO spec for XMPP and a plugin
for desktop Jitsi to interface with the mobile devices (maps, etc...). And
also a 'dispatch' feature that would allow a user of the software to see a
map of all received GEOs in the last 12 hours. This could give a bird's eye
view of which job sites a company's workers are currently located.

Start in a fork on Github. If you're willing to sign the Jitsi CLA, we could probably also arrange that your modifications could go back into the main project (despite the note saying that we won't address pull requests).

To me, Jitsi Android and desktop are the best option for modern
communication.

Thanks :slight_smile:

Also, on the topic of aTalk. Your update looks very good. I have read
the comments about the source code, but maybe you could shoot me a line?
athompson@successos.com

Thanks!
Adrian

Ingo