Bug#760485: Jitsi meet packaging
Ok. As expected, there are indeed reasons for the Jitsi-meet's absence. We shouldn't expect it to arrive soon. On the other hand Jitsi has called a lot of attention lately, and it is used in DebConf and Debian Social. I'm not saying it will be easy, but I think we're in a way better position in 2020 that we were a few years ago. On top of that, the amount of dependencies might be reducing and although Kotlin isn't there yet either, it is reported to be 'almost' there. And although Jitsi might be a fast-moving target for the moment, I guess most of the underlying libraries aren't. Libraries are usually useful in broader contexts than user-applications, so we might perhaps be able to pool resources with other users interested in different use-cases for the same libraries. Do you think it would make sense to start packaging these libraries first, in order to pave the way for a future adoption of Jitsi-meet? El dom., 27 sept. 2020 a las 16:41, Damian Minkov () escribió: > Hi all, > > Thanks for the interest in the project. There are a few concerns I have, > first is that we do not have the resources to maintain this. > > The second one is that the project sometimes follows the pace of the > browsers to do new releases. Which means a new version every 6 weeks. We > had two or three occasions in the last few years where everyone needs to > update due to a breaking change in the browsers, like a mandatory field > being added in SDP, or the old bridge not supporting the new DTLS version. > And because of the pace of how things evolve, we do not support old release > doing backports. This means that if a package goes in stable it may happen > to soon be unusable. > And sometimes backporting a change is even not possible :) Like the DTLS > change, the update was moving of using a complete re-write of the bridge > ... new dependencies and totally new project ... > > And if someone chooses the path of doing the job we are talking about > 150-200 dependent libraries, I'm not sure how many of those are already in > Debian, I would guess not much ... This was the main problem when we did > the Jitsi Desktop submission to the Debian repos, It took us, one > person, fulltime for almost six months. > Nowadays the video bridge had been rewritten and has fewer dependencies. > I'm also not sure about the state of Kotlin, is it yet in the repos, cause > it is one of the dependencies? > > Regards > damencho > > > On Sun, Sep 27, 2020 at 8:11 AM Ko Ko Ye` wrote: > >> May I help you ? >> >> Mentoring or RFP / RFS >> >> with regards >> >> On Sun, Sep 27, 2020 at 6:57 PM Sudip Mukherjee < >> sudipm.mukher...@gmail.com> wrote: >> >>> On Sun, Sep 27, 2020 at 11:49 AM Mathias Behrle wrote: >>> > >>> > * Fioddor Superconcentrado: " Jitsi meet packaging" (Sun, 27 Sep 2020 >>> 12:10:17 >>> > +0200): >>> > >>> > Hi, >>> > >>> > > As user I'm interested in having Jitsi Meet available in FreedomBox. >>> Since >>> > > it is a pure Debian blend we need an official Debian package. So I'm >>> > > considering to step forward and take over it. >>> > > >>> > > But >>> > > 1) I've never ever packaged any Debian package. >>> > > 2) According to this bug, previous attempts have failed, so I guess >>> there >>> > > are reasons for that. >>> > > >>> > > So, any guidance would be welcome. >>> > > >>> > > I've seen that upstream already provides a .deb file. I guess it >>> needs >>> > > further debianisation to be accepted in the archive. >>> > >>> > At least the original owner of #760485 seems to be the same person >>> that is >>> > currently active and in Uploaders at >>> > https://github.com/jitsi/jitsi-meet/blob/master/debian/control >>> > >>> > Best will be to ask him directly why he didn't push to get the >>> packages into >>> > Debian main. I have added him on CC. >>> >>> I had the same interest and mailed Damencho around March and he >>> mentioned about lack of resources to maintain jitsi in Debian as its a >>> lot of work. >>> >>> >>> -- >>> Regards >>> Sudip >>> >>> >> >> -- >> >> with regards *Ko Ko Ye`* >> >> +95 97989 22022 >> +95 94500 22022 >> +95 9731 47907 >> kokoye2...@gmail.com >> kokoye2...@ubuntu.com >> >> skype: kokoye2007 >> jitsi: kokoye2007 >> >> http://ubuntu-mm.net >> http://wiki.ubuntu.com/kokoye2007 >> http://wiki.ubuntu.com/MyanmarTeam http://loco.ubuntu.com/teams/ubuntu-mm >> >
Bug#760485: Jitsi meet packaging
* Damian Minkov: " Re: Jitsi meet packaging" (Sun, 27 Sep 2020 09:41:31 -0500): Hi Damian, > Thanks for the interest in the project. There are a few concerns I have, > first is that we do not have the resources to maintain this. > > The second one is that the project sometimes follows the pace of the > browsers to do new releases. Which means a new version every 6 weeks. We > had two or three occasions in the last few years where everyone needs to > update due to a breaking change in the browsers, like a mandatory field > being added in SDP, or the old bridge not supporting the new DTLS version. > And because of the pace of how things evolve, we do not support old release > doing backports. This means that if a package goes in stable it may happen > to soon be unusable. > And sometimes backporting a change is even not possible :) Like the DTLS > change, the update was moving of using a complete re-write of the bridge > ... new dependencies and totally new project ... > > And if someone chooses the path of doing the job we are talking about > 150-200 dependent libraries, I'm not sure how many of those are already in > Debian, I would guess not much ... This was the main problem when we did > the Jitsi Desktop submission to the Debian repos, It took us, one > person, fulltime for almost six months. Thanks a lot to give some precious insights in the packaging effort, it is a good thing to have it documented on this bug. It seems really to be a difficult task to provide a stable version with changing browser compatibility. Cheers Mathias -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6 AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6 pgpuYpIwYsEQ7.pgp Description: Digitale Signatur von OpenPGP
Bug#760485: Jitsi meet packaging
On Sun, Sep 27, 2020 at 3:41 PM Damian Minkov wrote: > > Hi all, > > Thanks for the interest in the project. There are a few concerns I have, > first is that we do not have the resources to maintain this. > > Nowadays the video bridge had been rewritten and has fewer dependencies. I'm > also not sure about the state of Kotlin, is it yet in the repos, cause it is > one of the dependencies? Not yet. :( https://bugs.debian.org/892842 -- Regards Sudip
Bug#760485: Jitsi meet packaging
Hi all, Thanks for the interest in the project. There are a few concerns I have, first is that we do not have the resources to maintain this. The second one is that the project sometimes follows the pace of the browsers to do new releases. Which means a new version every 6 weeks. We had two or three occasions in the last few years where everyone needs to update due to a breaking change in the browsers, like a mandatory field being added in SDP, or the old bridge not supporting the new DTLS version. And because of the pace of how things evolve, we do not support old release doing backports. This means that if a package goes in stable it may happen to soon be unusable. And sometimes backporting a change is even not possible :) Like the DTLS change, the update was moving of using a complete re-write of the bridge ... new dependencies and totally new project ... And if someone chooses the path of doing the job we are talking about 150-200 dependent libraries, I'm not sure how many of those are already in Debian, I would guess not much ... This was the main problem when we did the Jitsi Desktop submission to the Debian repos, It took us, one person, fulltime for almost six months. Nowadays the video bridge had been rewritten and has fewer dependencies. I'm also not sure about the state of Kotlin, is it yet in the repos, cause it is one of the dependencies? Regards damencho On Sun, Sep 27, 2020 at 8:11 AM Ko Ko Ye` wrote: > May I help you ? > > Mentoring or RFP / RFS > > with regards > > On Sun, Sep 27, 2020 at 6:57 PM Sudip Mukherjee < > sudipm.mukher...@gmail.com> wrote: > >> On Sun, Sep 27, 2020 at 11:49 AM Mathias Behrle wrote: >> > >> > * Fioddor Superconcentrado: " Jitsi meet packaging" (Sun, 27 Sep 2020 >> 12:10:17 >> > +0200): >> > >> > Hi, >> > >> > > As user I'm interested in having Jitsi Meet available in FreedomBox. >> Since >> > > it is a pure Debian blend we need an official Debian package. So I'm >> > > considering to step forward and take over it. >> > > >> > > But >> > > 1) I've never ever packaged any Debian package. >> > > 2) According to this bug, previous attempts have failed, so I guess >> there >> > > are reasons for that. >> > > >> > > So, any guidance would be welcome. >> > > >> > > I've seen that upstream already provides a .deb file. I guess it needs >> > > further debianisation to be accepted in the archive. >> > >> > At least the original owner of #760485 seems to be the same person that >> is >> > currently active and in Uploaders at >> > https://github.com/jitsi/jitsi-meet/blob/master/debian/control >> > >> > Best will be to ask him directly why he didn't push to get the packages >> into >> > Debian main. I have added him on CC. >> >> I had the same interest and mailed Damencho around March and he >> mentioned about lack of resources to maintain jitsi in Debian as its a >> lot of work. >> >> >> -- >> Regards >> Sudip >> >> > > -- > > with regards *Ko Ko Ye`* > > +95 97989 22022 > +95 94500 22022 > +95 9731 47907 > kokoye2...@gmail.com > kokoye2...@ubuntu.com > > skype: kokoye2007 > jitsi: kokoye2007 > > http://ubuntu-mm.net > http://wiki.ubuntu.com/kokoye2007 > http://wiki.ubuntu.com/MyanmarTeam http://loco.ubuntu.com/teams/ubuntu-mm >
Bug#760485: Jitsi meet packaging
May I help you ? Mentoring or RFP / RFS with regards On Sun, Sep 27, 2020 at 6:57 PM Sudip Mukherjee wrote: > On Sun, Sep 27, 2020 at 11:49 AM Mathias Behrle wrote: > > > > * Fioddor Superconcentrado: " Jitsi meet packaging" (Sun, 27 Sep 2020 > 12:10:17 > > +0200): > > > > Hi, > > > > > As user I'm interested in having Jitsi Meet available in FreedomBox. > Since > > > it is a pure Debian blend we need an official Debian package. So I'm > > > considering to step forward and take over it. > > > > > > But > > > 1) I've never ever packaged any Debian package. > > > 2) According to this bug, previous attempts have failed, so I guess > there > > > are reasons for that. > > > > > > So, any guidance would be welcome. > > > > > > I've seen that upstream already provides a .deb file. I guess it needs > > > further debianisation to be accepted in the archive. > > > > At least the original owner of #760485 seems to be the same person that > is > > currently active and in Uploaders at > > https://github.com/jitsi/jitsi-meet/blob/master/debian/control > > > > Best will be to ask him directly why he didn't push to get the packages > into > > Debian main. I have added him on CC. > > I had the same interest and mailed Damencho around March and he > mentioned about lack of resources to maintain jitsi in Debian as its a > lot of work. > > > -- > Regards > Sudip > > -- with regards *Ko Ko Ye`* +95 97989 22022 +95 94500 22022 +95 9731 47907 kokoye2...@gmail.com kokoye2...@ubuntu.com skype: kokoye2007 jitsi: kokoye2007 http://ubuntu-mm.net http://wiki.ubuntu.com/kokoye2007 http://wiki.ubuntu.com/MyanmarTeam http://loco.ubuntu.com/teams/ubuntu-mm
Bug#760485: Jitsi meet packaging
On Sun, Sep 27, 2020 at 11:49 AM Mathias Behrle wrote: > > * Fioddor Superconcentrado: " Jitsi meet packaging" (Sun, 27 Sep 2020 12:10:17 > +0200): > > Hi, > > > As user I'm interested in having Jitsi Meet available in FreedomBox. Since > > it is a pure Debian blend we need an official Debian package. So I'm > > considering to step forward and take over it. > > > > But > > 1) I've never ever packaged any Debian package. > > 2) According to this bug, previous attempts have failed, so I guess there > > are reasons for that. > > > > So, any guidance would be welcome. > > > > I've seen that upstream already provides a .deb file. I guess it needs > > further debianisation to be accepted in the archive. > > At least the original owner of #760485 seems to be the same person that is > currently active and in Uploaders at > https://github.com/jitsi/jitsi-meet/blob/master/debian/control > > Best will be to ask him directly why he didn't push to get the packages into > Debian main. I have added him on CC. I had the same interest and mailed Damencho around March and he mentioned about lack of resources to maintain jitsi in Debian as its a lot of work. -- Regards Sudip
Bug#760485: Jitsi meet packaging
* Fioddor Superconcentrado: " Jitsi meet packaging" (Sun, 27 Sep 2020 12:10:17 +0200): Hi, > As user I'm interested in having Jitsi Meet available in FreedomBox. Since > it is a pure Debian blend we need an official Debian package. So I'm > considering to step forward and take over it. > > But > 1) I've never ever packaged any Debian package. > 2) According to this bug, previous attempts have failed, so I guess there > are reasons for that. > > So, any guidance would be welcome. > > I've seen that upstream already provides a .deb file. I guess it needs > further debianisation to be accepted in the archive. At least the original owner of #760485 seems to be the same person that is currently active and in Uploaders at https://github.com/jitsi/jitsi-meet/blob/master/debian/control Best will be to ask him directly why he didn't push to get the packages into Debian main. I have added him on CC. > I plan to: > - Review some introductory videos and documentation on Debian packaging > that I read/watched ago and need a second check. > - Take a look at other installation traces (Yunohost installs it on Debian > and I want to check how they do it, and there's a number of hot to posts > out there). > - Then take the upstream package itself and try to identify the roadblocks. > - Document them before I try to solve them, so that if I bun out someone > can take over and not have to start all over again. > > I'm responding to both the bug tracker and the mentors list. Is the list > for mentors and mentored pupils ment for pupill support or Is it just > mentors-only for coordination? My underlying question is: Should I join > that list? This list is for responding to all kinds of packaging questions, probably best to subscribe. Cheers Mathias -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6 AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6 pgpBpcMFYlbG9.pgp Description: Digitale Signatur von OpenPGP
Bug#760485: Jitsi meet packaging
Hi. As user I'm interested in having Jitsi Meet available in FreedomBox. Since it is a pure Debian blend we need an official Debian package. So I'm considering to step forward and take over it. But 1) I've never ever packaged any Debian package. 2) According to this bug, previous attempts have failed, so I guess there are reasons for that. So, any guidance would be welcome. I've seen that upstream already provides a .deb file. I guess it needs further debianisation to be accepted in the archive. I plan to: - Review some introductory videos and documentation on Debian packaging that I read/watched ago and need a second check. - Take a look at other installation traces (Yunohost installs it on Debian and I want to check how they do it, and there's a number of hot to posts out there). - Then take the upstream package itself and try to identify the roadblocks. - Document them before I try to solve them, so that if I bun out someone can take over and not have to start all over again. I'm responding to both the bug tracker and the mentors list. Is the list for mentors and mentored pupils ment for pupill support or Is it just mentors-only for coordination? My underlying question is: Should I join that list? Thanks in advance
