[jitsi-dev] [GitHub] Subscribed to jitsi/jitsi-universe notifications


#1

Hello

    jitsi/jitsi-universe created by lyubomir Parent Maven project for
    the whole family of projects of the Jitsi community
    https://github.com/jitsi/jitsi-universe

While we're sanitizing things I was thinking about libsrc. We initially set
that up when we were still using SVN and a new repository was a major thing.
Now weupnp, jain-sdp, lgpl-dependencies (whatever that means), otr4j, growl4j
already have a forked repository under /jitsi.

Proposal: deprecate libsrc and create/fork a repository for all the
dependencies we use. This makes it easier to browse the source and to maintain
patches (in branches).

Ingo


#2

+1 for me

I only have one external dependency, so not too much hassle, but I
wasn't even quite sure how/what to store exactly. So yeah, fork is way
more straight-forward.

Is debian packaging dependent on libsrc? Don't really know how this
works, but I'm quite sure @damencho needs some of this.

Danny

···

On 10-07-15 21:46, Ingo Bauersachs wrote:

Hello

    jitsi/jitsi-universe created by lyubomir Parent Maven project for
    the whole family of projects of the Jitsi community
    https://github.com/jitsi/jitsi-universe

While we're sanitizing things I was thinking about libsrc. We initially set
that up when we were still using SVN and a new repository was a major thing.
Now weupnp, jain-sdp, lgpl-dependencies (whatever that means), otr4j, growl4j
already have a forked repository under /jitsi.

Proposal: deprecate libsrc and create/fork a repository for all the
dependencies we use. This makes it easier to browse the source and to maintain
patches (in branches).

Ingo

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