[Debian-med-packaging] Bug#893247: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

[Andreas Tille]

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 (which I uploaded today) once
pkg-java has moved to Salsa (or did I missed the move?)
 
> 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
> designated guest account

Hmmm, I admit I prefer a real team since I have the impression that the
love a package receives is higher than for packages that end up in the
collab-maint / debian "dustbin".
 
> OR
> 
> (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 found out this will be
established.
 
> OR
> 
> (c) configuring any other mechanism that would allow the union of these
> two teams (and others!) to contribute to the packaging.

Definitely.
 
> As for which team is listed in the Maintainer field, I don't think it
> matters much as long as we have a suitable set of interested Uploaders.

I agree that it does not matter much.  We have some lib*-java as well as
python-* and lib*-perl packages maintained in Debian Med team if there
are only Debian Med rdepends.  If we think about it like in the
libjbzip2-java case we should not only move back this one but also other
packages to the Java team.  That would be fine for me but there are
always cases where one needs to decide between (at least) two teams.

Kind regards

       Andreas.

-- 
http://fam-tille.de