[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [jitsi-dev] Jitsi in Debian



Hi,

On Sun, Oct 18, 2015 at 12:49 PM, Tobias Frost <tobi@debian.org> wrote:
> Am Samstag, den 17.10.2015, 16:40 -0500 schrieb Damian Minkov:
>>
>> Will try that. There were a lot of modifications lately and the
>> debian
>> src packaging needs some love, time we didn't have to continue
>> investing, as last two attempts ended with no results.
>>
>
> Well, Damian....
>
> I was one of the reviewers (together with Diane) at that time but I had
> the impression that out of the review no actions have followed from
> your side; at least I could not find any reference in my mailbox.
>
> One suggestion was to file a RFS bug to keep easier track of the
> progress while tackling one issue after the other. The RFS bug workflow
> has been established as quasi standard for sponsorship, so without RFS
> its not so likely that someone will pick up.

There was no RFS, and no progress after your review, cause we need to
find time and power to do all the updates. The 'no progress' mentioned
was on two times before your mails.

>
> (Also, you need tackle the embedded code libraries. At least show some
> progress! And to avoid getting you on the wrong path, as you mentioned
> maven on jitsi-dev -- you cannot download dependencies at build time.)

If you mean to get the dependencies out of jitsi, I havn't seen any
interest of that from anybody so not sure it is worth the effort at
this point.
I'm aware of the downloading while building problem, but you mean
there is no way to reuse maven stuff while packaging, as the list of
dependencies is maybe 30-40 libraries?

>
> Maybe do that as the first step, then bounce the mail exchanges we had
> so far to the bug. (There were in private conversation, so you need to
> ask the involved people before; my mails are ok)
>
> Maybe you could ask the java-packaging team if they are interested in
> the package? You could join them and maybe someone also will help you
> on packaging.
>
> To find a sponsor, you need to bring the package in shape first;
> frankly, your changes to find a sponsor are very low if the package is
> in a bad shape.
> I understand thats lots of work, but it needs to be done; of course
> Rome isn't built in a day, but so it might be also okish "iterate" to
> it (depending on the sponsor); Howerver this won't work without some
> commitment from your side -- to get the best packaging quality and a
> Policy compliant package. Also to maintain this quality in the future.

The problem is that the packaging of such complex project, cannot keep
up with the rapid development that happens which at some point is a
big problem.

Regards
damencho

>
> Tobi
>
>
>
>
>


Reply to: