Suddenly, my 'List Of Ethical Code Hostings by 3rd-Parties' above got reshared a lot once again. Thanks for everyone involved here!

Wow, even @ReverseEagle retooted my post. Thank you very much for bringing up @codeberg and everything to the mainstream.

Hello @dibi58, long time no see and glad to find you again. Hope you are in healthy and fine condition.

Wow, how lively today is. I just came back to Mastodon and I saw many retoots on my Ethical Code Hostings. Even @datenschutzratgeber helped me retoot. Thank you very much for you all!

Hello @drh, thanks for resharing my post about ethical alternatives!

Hello my new frien @nukosu, thanks for resharing my Ethical Code Hosting List. Greetings from Indonesia!

@codeberg @Joachim_Rees hello Codeberg! I really love your slogan in software freedom. I respect that!

I learn about several new comers in ethical code hosting field and so far I really admire you. You are very clear, you have Legal/Impressum, TOS, and Privacy Policy accessible straight on the main page.

But could I ask 2 features, if I permitted to do? I think Codeberg needs a clear user guide & explanation of each account features.

Greetings from Indonesia!

(I'm not a programmer)

@ademalsasa @Joachim_Rees hi!

Thank you, this is great feedback. We want to improve here, and also mention that we are completely community-driven, whomever wants to contribute, can do so in form of feedback, content, config, and code!

Greetings to Indonesia!

@codeberg looking at this post I just realised that there is a typo in your slogan. I suppose it should be: Give *your* free project a free home.

@ademalsasa
Very interesting list! Thanks for sharing. We looked around for git hosting + coding community - venture capital. We didn't find many options. But we are also happy we spotted and went for salsa.debian.org

@ademalsasa Is this a ranking in some order, or is this an unordered list of things?

@cadence hello cadence, this is not ranking and only an unordered list.

@ademalsasa though not exactly the same, a bare bones git server on VPS can come in handy.

@travisshears @ademalsasa

That's what I started using a few days ago and I'm SO happy I did it.

This tutorial is perfect for anyone: invidio.us/watch?v=9qIK8ZC9BnU

@ademalsasa There's only one problem with all of these - survivability. Self hosted platforms are amazing (I run and love Gitea myself) but what happens when someone stops paying the hosting bills? Critical open source software could be lost forever. Not suggesting everyone should use Github, just that it's a problem worth thinking about.

@feoh @ademalsasa

provided they all allow you to import/export data with an open protocol that may not be such an issue.

Remember Nokia, Microsoft and Windows Mobile? (They weren't even particularly bad mobile phones, had good cameras and I used them for many years myself).

Microsoft walked away from that after just a few years in spite of pouring millions of dollars into the venture...

@vfrmedia Open protocols are important, but I'm not talking about data mobility, I'm talking about data *retention*. Being able to look at old source code, old versions of things, even projects no longer maintained or used can be a super important part of doing quality engineering. Why do you think people are still zealously hoarding V7 UNIX 30 years after it's become technically irrelevant? Because it's an important learning tool.

@feoh I agree with this, but to some extent the two are interlinked, if there's a way of storing this old data in multiple locations its more likely to survive - I have noticed in hobbies like amateur radio, restoring electronics, and retrocomputing there does seem to be at least some attempt to preserve useful historical data (including taking note that the humans who curate it aren't immortal and many are getting on in years)

@vfrmedia For sure! What I'd love to see is a Github *LIKE* thing that could serve as a central hub for development funded by some company with very big pockets that can easily handle the associated costs, and a distributed protocol where the data can be federated so we don't lose the whole enchilada if the hub goes down :)

@feoh @ademalsasa

The nature of Git itself mitigates a lot of this.

Any developer with a Git clone has the full history of the project. (This includes the person who submitted a three-line patch to fix something nobody else was bothered by.)

If there are no developers at all then it is an unmaintained project and the lack of source is the least of the problems. It needs to be pulled from use ASAP.

@yam655 Wow oh wow do I disagree with this. Being able to examine historical source code is IMPORTANT. It's one thing to say "This is old. Don't use it. Go use THIS instead" but saying "Anything not in regular use should be erased from the face of the earth" feels like a VERY dangerous tack to take.

@feoh

I see places for active development and business use as being distinct and different from data museums that don't see code changes and don't expect people to be using them in production.

Code as art. Code as history. Code as research ideas for new code. All are good, valid use-cases.

But they don't need functioning repositories that can be confused with things that are safe to have as core technology stacks for public use.

@yam655 I was a release engineer for just shy of two decades. You're NEVER gonna get me to sign up to that being a good idea. Let's agree to disagree.

@yam655 Also I see things like BitTorrernt as providing a refutation of your claim. Have you ever encountered a torrent which was still listed as active but didn't have enough people actually seeding it such that it was in effect no longer available? I have.

@feoh

Linus Torvalds didn't use source control at all for the Linux kernel for decades. He operated with the knowledge that enough people already had the source downloaded so that there was built-in redundancy.

If nobody has been making changes to the code, it has been abandoned. Abandoned code still in use is extremely dangerous and should be replaced ASAP.

Folks should be replacing abandoned code well before the source disappears. If it were important, it would have a maintainer.

@feoh

Basically: The survivability of unmaintained code is a bug, not a feature.

@ademalsasa Hello, Thanks for your nice list. Ultimately, I realized that self-hosting is the best way. ❤️ from 🇯🇵

@nukosu wow, I got a new friend from Japan once again after @kapper1224. Thank you very much, Nukosu!

@nukosu ah, and I also interested in functional package manager (like Guix and Nix) too (a little bit, just as an end user).

Sign in to participate in the conversation
FLOSS.social

For people who care about, support, or build Free, Libre, and Open Source Software (FLOSS).