It's written in python, so Luke (& other sysadmins) should have an easier time with emergency maintenance. I couldn't find information on how much resources it uses. There are packages available for debian, but, since they are currently using a rolling release model, nothing in debian stable.
anything that we replace the current system with needs to be peer distributable: no dependence on any central service. full independence means being able to reliably communicate under unreliable circumstances.
jean-paul has restricted internet access both at work and where he is now, on holiday.
i have mobile internet access *only* and it is both costly and unreliable.
initially i was delighted to see that sourcehut is "distributed" however this applies inter-service not at the level *of* each service.
sourcehut looks unfortunately like it would be a step in the wrong direction in terms of centralisation, complexity, server utilisation and more.
samuel runs this. it is a bit of a jump. it can import and export to git: however it stores everything in a sqlite database as blockchain records and by everything i mean everything. it therefore cannot export the bugtracker to git for exampke because git doesn't understand the concept of bugs.