Migrating to Salsa?

Stuart Prescott stuart at debian.org
Sat Feb 17 06:47:55 UTC 2018


>> There's also a tagpending webhook on salsa now too. Do we want to enable
>> that? (while you're poking around on salsa, can you add that to your
>> list?)
> 
> Seems like a good idea to me. Also trivial to configure, so I just did.

thanks!

>> There's a few things in the repo that are not uploaded yet and I had been
>> holding off doing an upload until the salsa migration had been done. I
>> can do an upload with fixed Vcs-* in the next few days if you like (or
>> you might beat me to it!).
> 
> Cool - I just cloned the existing repo into
> https://salsa.debian.org/python-debian-team/python-debian/. Looks like I
> caught your recent changelog commit. :) I probably won't beat you to an
> upload.

And now uploaded with existing changes already in git and updated Vcs-* 
headers; looking through the source afterwards I found a few more places 
where alioth was mentioned as a location for the source so I have updated 
them in git for whenever python-debian is next uploaded.

There are still plenty of places where alioth lists are mentioned; since 
there is no working replacement for that yet, I guess we stick with them for 
the time being. I think we should still have a place to have discussion 
about python-debian development (not everything is a bug for a bug tracker) 
but there is no place for that yet.

(Was someone contacted about migrating the alioth lists to new 
infrastructure?)

>> My initial thought is that we should disable the issue tracker on salsa
>> and only use the Debian BTS but I'm open to discussion on that. There is
>> perhaps merit in using salsa for 'upstream' issues but I doubt having
>> bugs in two places is a good plan.
> 
> I agree, one place to track bugs makes sense. That said, there seem to
> be some users of python-debian outside Debian itself (it's in PyPI), so
> it might make sense to consider enabling issue tracking if only to make
> it easier for external users to file bugs.

Indeed, I had wondered if that made sense as an "upstream" tracker, but 
having two separate trackers doesn't feel like much of a win for me. That 
said, anything that encourages new contributions is a good thing.

cheers
Stuart

 
-- 
Stuart Prescott    http://www.nanonanonano.net/   stuart at nanonanonano.net
Debian Developer   http://www.debian.org/         stuart at debian.org
GPG fingerprint    90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7




More information about the pkg-python-debian-maint mailing list