Bug#893247: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team
Am 26.03.2018 um 07:55 schrieb Andreas Tille: > On Sun, Mar 25, 2018 at 11:56:18PM +0200, Emmanuel Bourg wrote: >> Le 25/03/2018 à 19:55, tony mancill a écrit : [...] >>> (b) relaxing the default pkg-java permissions to be like those of the >>> Debian Perl Team and allow all DDs by default >> >> +1, but note that this is basically how it already works today since any >> request to join the pkg-java group (or now java-team on Salsa) is always >> granted. > > Same for Debian Med. Its a bit sad that it can not easily be granted to > any DD any more to enable commits of team uploads / NMUs instantly but > require an extra step. > Apparently one can share single packages with the Debian group which contains all Debian developers. [1] [1] https://wiki.debian.org/Salsa/AliothMigration#Share_a_group_with_all_Debian_developers signature.asc Description: OpenPGP digital signature
Bug#893247: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team
On Sun, Mar 25, 2018 at 11:56:18PM +0200, Emmanuel Bourg wrote: > 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 > > designated guest account > > -1 :-) > > (b) relaxing the default pkg-java permissions to be like those of the > > Debian Perl Team and allow all DDs by default > > +1, but note that this is basically how it already works today since any > request to join the pkg-java group (or now java-team on Salsa) is always > granted. Same for Debian Med. Its a bit sad that it can not easily be granted to any DD any more to enable commits of team uploads / NMUs instantly but require an extra step. Kind regards Andreas. -- http://fam-tille.de
Bug#893247: 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 found out this will be
> established.
FWIW, the perl-team projects on Salsa are not DD-writable any more
because that's not as simple as it was on Alioth.
IIRC it's not possible to grant permissions ("share with ..") on a
group or sub-group level, only for each individual project, and that
takes ages via the API and whatnot.
I found my report from January:
https://lists.debian.org/debian-perl/2018/01/msg00045.html
Cheers,
gregor
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`- NP: Rolling Stones
signature.asc
Description: Digital Signature
Bug#893247: 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 > designated guest account -1 > (b) relaxing the default pkg-java permissions to be like those of the > Debian Perl Team and allow all DDs by default +1, but note that this is basically how it already works today since any request to join the pkg-java group (or now java-team on Salsa) is always granted. Emmanuel Bourg
Bug#893247: 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 (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
Bug#893247: 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 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 OR (b) relaxing the default pkg-java permissions to be like those of the Debian Perl Team and allow all DDs by default OR (c) configuring any other mechanism that would allow the union of these two teams (and others!) to contribute to the packaging. 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. Cheers, tony signature.asc Description: PGP signature
Bug#893247: 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
Bug#893247: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team
Hi, due to recently opened bugs (#893247 and #893268) I stumbled upon libjbzip2-java and libnanoxml2-java packages. Both have rdepends of Debian Med packages. Libjbzip2-java is maintained by Debian Med members anyway and libnanoxml2-java had the last maintainer upload in 2010. I consider the packages both better "observed" in Debian Med team and will take both over to salsa.debian.org/med-team. I hope this is OK for everybody. Kind regards Andreas. -- http://fam-tille.de
