Bug#893268: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

On Sun, 25 Mar 2018 23:29:13 +0200, Andreas Tille wrote: > > (b) relaxing the default pkg-java permissions to be like those of the > > Debian Perl Team and allow all DDs by default > I'd prefer this a lot. We did so for Debian Med on Alioth - I'm not > sure how that works on Salsa but if we

Bug#893268: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

Le 25/03/2018 à 23:29, Andreas Tille a écrit : > I'm fine with moving libjbzip2-java (which I uploaded today) once > pkg-java has moved to Salsa (or did I missed the move?) I'm working on the migration, I haven't finalized the notification hooks yet. __ This is the maintainer address of

Bug#893268: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

Le 25/03/2018 à 19:55, tony mancill a écrit : > Multiple teams wanting to maintain a library is a good problem to have. > I propose we consider: > > (a) pulling these libraries into the "Debian" project on Salsa, which > replaces collab-maint and grants commit permissions to all DDs and any >

Bug#893268: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

Hi Emmanuel, On Sun, Mar 25, 2018 at 10:55:54AM -0700, tony mancill wrote: > On Sun, Mar 25, 2018 at 06:37:05PM +0200, Emmanuel Bourg wrote: > > These are quite generic non-med related libraries, I'd prefer keeping them > > under the Java Team umbrella. I'm fine with moving libjbzip2-java

Bug#893268: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

Hi Andreas, These are quite generic non-med related libraries, I'd prefer keeping them under the Java Team umbrella. Emmanuel Bourg __ This is the maintainer address of Debian's Java team . Please use

Bug#893268: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

On Sun, Mar 25, 2018 at 06:37:05PM +0200, Emmanuel Bourg wrote: > Hi Andreas, > > These are quite generic non-med related libraries, I'd prefer keeping them > under the Java Team umbrella. > > Emmanuel Bourg Hi, Multiple teams wanting to maintain a library is a good problem to have. I propose