Hi Holger,
> But I think we want to move something distro agnostic, and salsa.d.o
> is very much Debian centric, so I think we should look for something
> else. I'd be fine to using github.com or gitlab.com or foobar.
Let's try and enumerate some of the potential options here so we aren't
lost or confusing each other in paragraphs (or otherwise letting this go
on for too long):
a) Some hybrid where we have the code remain on salsa yet mirror it on
Github. Somewhat like the situation ~12 months ago.
b) Another frankenstein hybrid where we have the code remain on salsa
& mirror on Github, but move issue tracking to salsa.
c) Make salsa the canonical location, enable issues on it and use it
for MRs. "Forward" issues upstream to salsa from the BTS.
d) Make GitHub the canonical location and use it for PRs and issues.
Remove diffoscope entirely from salsa & "forward" issues to GitHub
from the BTS.
e) Make GitLab the canonical location for both code and use it for MRs
and issues. Remove diffoscope entirely from salsa and forward
"issues" here from the BTS.
I'm not *really* that fussed philosophically but as someone who has
done a lot of the diffoscope coding over the past years I just want to
remove as much day-to-day infrastructure overhead with respect to
collating, collapsing, merging issues and suchforth.
It is very easy to overloop what a big mental barrier and annoyance it
is to have to do this extra work.
(... not to mention how OCD-triggering it is to have duplicates, etc.)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
