Path: csiph.com!xmission!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From: Ghislain Vaillant <ghisvail@gmail.com>
Newsgroups: linux.debian.maint.python
Subject: Re: Move to salsa? Merge modules and apps team?
Date: Wed, 07 Feb 2018 10:20:01 +0100
Message-ID: <vgu3v-3fZ-3@gated-at.bofh.it>
References: <vgsuJ-27T-5@gated-at.bofh.it> <vgtK9-2QF-3@gated-at.bofh.it>
Old-Return-Path: <ghisvail@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Approved: robomod@news.nic.it
Lines: 33
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:10111

2018-02-07 8:58 GMT+00:00 Matthias Klose <doko@debian.org>:
> On 07.02.2018 08:37, W. Martin Borgert wrote:
>> Hi,
>>
>> how about moving the Python team(s) to salsa?
>> And how about merging the modules and apps teams into one?
>>
>> Moving git packages (modules team) is very easy using
>> import.sh from https://salsa.debian.org/mehdi/salsa-scripts.git
>>
>> Moving svn packages (apps team) is probably more work.
>>
>> Any opinions? Any doubts?
>
> I don't think that is a good idea.  Both teams are not very active when it comes
> to address RC issues and updating to new upstream versions.

How does that affect moving our hosting to salsa? Or is your point
against merging both teams? I am confused.

>  From my point of
> view the apps team is worse than the modules team in this regard.  Currently
> both teams really don't care about packages which are uploaded by other team
> members.  Maybe it's time to clean up the teams before any considerations to
> merge them?  For single maintainers we do have process for MIA, and for QA
> uploads, however both python teams are escaping such efforts.

Still unclear what all of this has to do with the salsa migration. I
understand your concerns, but imo they are orthogonal to the
transition.

Cheers,
Ghis