We also plan on supporting new contributions from the community so
projects like the Jitsi Client can continue developing.
Does this mean that development of Jitsi client will in the future
solely depend on contributions from the user community only?
There's a lot in Jitsi that's shared with the WebRTC line of the
project: libjitsi is 100% shared between the two. Jigasi uses the XMPP
and SIP protocol providers. There's more. So all that we add to these
projects is inherited by Jitsi.
It is likely that some parts will get less attention from the BlueJimp
team (like for example the media acquisition parts of libjitsi or the
user interface) and that's where we'd appreciate more help from our
dev community. There are already a few people contributing to the
Jitsi client, who aren't BlueJimp employees. Also many people out
there are using the Jitsi client commercially and hopefully we'll get
fresh help from them as well!
I would also be keen to understand how BlueJimp / Jitsi will evolve in
relation to the open source community:
- VoIP federation issues, such as using ICE with SIP, will you still be
able to put effort into such objectives?
- is there a risk that commercial objectives will make libjitsi evolve
faster than Jitsi Client can keep up?
- are you still keen to be involved in the packaging of Jitsi Client?
- will Atlassian undertake any improvements funded by other companies or
funding sources? Or is Atlassian only interested in developing the
Jitsi products for their own use?
We also plan on supporting new contributions from the community so
projects like the Jitsi Client can continue developing.
Does this mean that development of Jitsi client will in the future
solely depend on contributions from the user community only?
There's a lot in Jitsi that's shared with the WebRTC line of the
project: libjitsi is 100% shared between the two. Jigasi uses the XMPP
and SIP protocol providers. There's more. So all that we add to these
projects is inherited by Jitsi.
It is likely that some parts will get less attention from the BlueJimp
team (like for example the media acquisition parts of libjitsi or the
user interface) and that's where we'd appreciate more help from our
dev community. There are already a few people contributing to the
Jitsi client, who aren't BlueJimp employees. Also many people out
there are using the Jitsi client commercially and hopefully we'll get
fresh help from them as well!
We also plan on supporting new contributions from the community so
projects like the Jitsi Client can continue developing.
Does this mean that development of Jitsi client will in the future
solely depend on contributions from the user community only?
There's a lot in Jitsi that's shared with the WebRTC line of the
project: libjitsi is 100% shared between the two. Jigasi uses the XMPP
and SIP protocol providers. There's more. So all that we add to these
projects is inherited by Jitsi.
It is likely that some parts will get less attention from the BlueJimp
team (like for example the media acquisition parts of libjitsi or the
user interface) and that's where we'd appreciate more help from our
dev community. There are already a few people contributing to the
Jitsi client, who aren't BlueJimp employees. Also many people out
there are using the Jitsi client commercially and hopefully we'll get
fresh help from them as well!
I would also be keen to understand how BlueJimp / Jitsi will evolve in
relation to the open source community:
- VoIP federation issues, such as using ICE with SIP, will you still be
able to put effort into such objectives?
Priority on this remains unchanged. It is still something we'd like to
have but other than personal interest there's not a lot of motivation.
So again, situations remains the same.
- is there a risk that commercial objectives will make libjitsi evolve
faster than Jitsi Client can keep up?
You mean in a way that would make them break? I think this should be
easy to avoid and fix if it happens.
- are you still keen to be involved in the packaging of Jitsi Client?
Yes.
- will Atlassian undertake any improvements funded by other companies or
funding sources? Or is Atlassian only interested in developing the
Jitsi products for their own use?
As has already been stated: the open source initiative remains fully
functional so yes: contributions will be most welcome. We just need to
sort out the logistics. We are currently working on this.
Emil
···
On Thu, Apr 23, 2015 at 11:27 AM, Daniel Pocock <daniel@pocock.pro> wrote: