Comments URL: https://news.ycombinator.com/item?id=47321035

Points: 2

# Comments: 0

And I know one more of those people already!

5 more to go.

And yet, that's technically not CI.

The whole point we started using automation servers as an integration point was to avoid the "it works on my machine" drama. (Have watched at least 5 seasons of it - they were all painful!).

+1 on running the test harness locally though (where feasible) before triggering the CI server.

IMHO, this shows the huge dependency of all of the world’s open source software on a single company. (Microsoft, who owns GitHub).

In this context, Radicle - as an alternative way of hosting the world’s OSS - makes a lot of sense to me.

Also, being old gives it a huge advantage: you can bet you won't need a major rewrite of your pipelines in a couple of years when e.g. GitLab sells, or Microsoft decides GH actions aren't so free (or fast) any more, etc.

Ok, they didn't kill the open source community which is what we feared at the time (because they found a way to make more money from it), but I'm still more skeptical of Microsoft essentially controlling the world's open source software than Datadog buying an open core company.

But with Microsoft now painting everything with its "AI" brush, aren't you, as open source maintainers, concerned about keeping the world's FOSS on a proprietary platform?

Exactly! It really makes me wonder how GitLab thinks Datadog can help them defend against this risk. Then again, they're not open source - just open core.

Not looking to convince you of that or anything though... :)

- finding what the domain name is ? - resolving the DNS to an IP address ?

Radicle solves both problems in theory, but more the latter than the former right now:

- there is some basic functionality to search for projects hosted on Radicle, to find the right repo id (I expect this area will see a lot more activity and improvements in the near future), - given a repo id, actually getting the code onto your laptop. This is where the p2p network comes in, so that the person hosting it doesn't always need to keep their computer/router/tv box on, etc.

Migrating GitHub Pull Requests (PRs) to Radicle Patches is somewhat more involved, but that should still be possible (even if it involves some loss of information along the way, due to potential schema mismatches) ...

[1] - https://github.com/cytechmobile/radicle-github-migrate

That is the default port for `radicle-httpd`: an HTTP API that would allow you to authenticate (using your public/private key pair, that is stored on your machine), so that you can perform actions on the web-based interface as a specific user, through your local radicle node.

[1] - https://www.inkandswitch.com/local-first/

But please note that you can also choose a "block everyone, follow just the good ones" (i.e. a selective) seeding policy [1]).

[1] - https://docs.radicle.xyz/guides/seeder#a-selective-seeding-p...

[1] https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3trNYnLW...

https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3trNYnLW...

look at DigitalOcean about how it should be done: http://www.fastcompany.com/3048196/greek-startups-cut-off-fr...