@Blort I very well remember days back then when FLOSS hosting mostly happened on Sourceforge until at some point github appeared. Maybe it's the same here as it is about other network services indeed: We need new, cooperative, collaborative approaches not just to developing software but also about running and delivering software to users in a quality and reliability on par with Amazon AWS, Github, Twitter, ... .
@Blort True. We should keep people from simply moving to the next proprietary silo, but to do that, we need to find an approach that offers the ease-of-use, the straightforward accessibility and availability of #github and #gitlab and *still* is open and controllable. This is where I see not just development but hosting as extremely important.
@z428 Couldn't agree more. As in most other network services we need the combination of federation, open code, community governance and ease of use for the code that runs our hosting.
As per usual, the perfect option may not exist yet, but as soon as the FOSS community feels a strong need, we have the skills to make it happen. Let's take what we've learned from federated social networks, to the current open source code repository software, while encouraging diverse hosting solutions for it.
@z428 Exactly. What we *don't* want is for everyone to just stay and roll with whatever Microsoft decides is best for themselves. Equally, we don't want is for everyone to just jump over to some other proprietary coded silo, as happened with the SourceForge to GitHub migration.
This time we need to control the platform, make it as forkable as git and as based around our own goals and itches as every other FOSS project.