One of our maintainers, @fintohaps, will be speaking at the Ubuntu Summit this week in London!
He will be talking about "The Future Home of Open Source"
Hint: it may involve Radicle 馃槒
#Tag
One of our maintainers, @fintohaps, will be speaking at the Ubuntu Summit this week in London!
He will be talking about "The Future Home of Open Source"
Hint: it may involve Radicle 馃槒
One of our maintainers, @fintohaps, will be speaking at the Ubuntu Summit this week in London!
He will be talking about "The Future Home of Open Source"
Hint: it may involve Radicle 馃槒
Is there anyone using Radicle for collaboration (as a git forge)? I really like the idea of decentralised git hosting. By quickly trying out radicle-desktop, it seems to have most of the features I need (namely, issues and patches). I'm still looking if there's CI/CD, but maybe that needs to be done separately.
#git #forge #radicle
Finally #unsynn v0.2.0 is out. With plenty new features and improvements (and few breaking changes).
https://docs.rs/unsynn/0.2.0/unsynn/index.html
The 'unsynn!' macro got a lot improvements, it can parse a lot more rust code, including (some) generics. (Marker-)Traits can be defined and implemented with convenient syntax extensions.
We now have our own 'quote!' macro. Some 'format_ident! | format_literal!' etc. macros got added as well.
'transform.rs' adds types that can transform an AST while parsing.
The infrastructure got a big overhaul. Everything is on #radicle now, 'cehgit' got replaced by 'bar' (https://seed.pipapo.org/nodes/seed.pipapo.org/rad:z3WhBdHt1VVNyeQ61zpY66pNzuSrP) which automated this release!
Finally #unsynn v0.2.0 is out. With plenty new features and improvements (and few breaking changes).
https://docs.rs/unsynn/0.2.0/unsynn/index.html
The 'unsynn!' macro got a lot improvements, it can parse a lot more rust code, including (some) generics. (Marker-)Traits can be defined and implemented with convenient syntax extensions.
We now have our own 'quote!' macro. Some 'format_ident! | format_literal!' etc. macros got added as well.
'transform.rs' adds types that can transform an AST while parsing.
The infrastructure got a big overhaul. Everything is on #radicle now, 'cehgit' got replaced by 'bar' (https://seed.pipapo.org/nodes/seed.pipapo.org/rad:z3WhBdHt1VVNyeQ61zpY66pNzuSrP) which automated this release!
Is there anyone using Radicle for collaboration (as a git forge)? I really like the idea of decentralised git hosting. By quickly trying out radicle-desktop, it seems to have most of the features I need (namely, issues and patches). I'm still looking if there's CI/CD, but maybe that needs to be done separately.
#git #forge #radicle
A while ago I stumbled on #radicle a peer to peer forge, and thought it looked neat. The possible involvement of people from the crypto currency space gave me (and other people) a bad feeling. But I thought "It's open source (MIT & Apache), I should just read it."
So I read it (heartwood, and radicle-git repositories) , with a pause to go read the rust tutorial first.
I don't really know rust, having mostly just read the tutorial so I have no business commenting about vulnerabilities, but I can still have opinions about their code style and readability.
I found it readable, functions tend to be short with good function names, there are periodic comments explaining why their choices in the code base.
The software is broken up into a number of logical modules.
There's a bunch of code dealing with serializing and deseralizing their collaborative objects (cob) datatypes
They have a bunch of test code for most of the modules, and a suite of tests for checking the end to end behavior of the system.
I started reading 1.3.0, but they had released 1.4.0 when I was done so I looked through the commits as well. Those tended to be short except for one big rewrite where they reimplemented their quorum voting method.
On the whole the project looks like it does what it claims to do, wraps git in a peer to peer forge.
An unusual choice was they decided to use ssh keys for git signing, but they don't seem to use ssh for the replication part, that's through their daemon process using a gossip protocol.
Currently their methods of connecting to other hosts are ipv4, ipv6, dns, or tor addresses, though the underlying library looks like it also supported i2p.
Sadly there's no fancy DHT method for finding other peers, there's just a couple of hosts radicle hosts for the initial bootstrapping.
heartwood https://seed.radicle.xyz/z3gqcJUoA1n9HaHKufZs5FCSGazv5.git
radicle-git https://seed.radicle.xyz/z6cFWeWpnZNHh9rUW8phgA3b5yGt.git
It does have the typical problem of crypto heavy systems of offering terrible names.
Edited: to mention test code and repository names
I offer free CI capacity for open source Rust projects that have a Radicle repository. The blog post below explains at length.
I'm in the process of making https://callisto.liw.fi/ public. It's an experimental Radicle CI server using my Ambient CI engine. Blog post will be out later, but summary: I will run CI for open source Rust projects that want me to. Instructions at https://callisto.liw.fi/callisto/
I want to see how well I can run CI for others.
Code must be on Radicle (technical requirement), and you need to add a file to specify what actions CI should take.
I offer free CI capacity for open source Rust projects that have a Radicle repository. The blog post below explains at length.
Temptation to find a way to run #Radicle increases.
I'm in the process of making https://callisto.liw.fi/ public. It's an experimental Radicle CI server using my Ambient CI engine. Blog post will be out later, but summary: I will run CI for open source Rust projects that want me to. Instructions at https://callisto.liw.fi/callisto/
I want to see how well I can run CI for others.
Code must be on Radicle (technical requirement), and you need to add a file to specify what actions CI should take.
The next #Radicle CI office hour will happen at
Wed, Sep 10, 2025, 18:00 (that's in two days minus one hour) at https://meet.jit.si/RadicleCI
This time, there's no agenda or demo planned. I'll be there to answer questions and to chat about any topic that comes up.
If continuous integration in a distributed Git hosting system interests you at all, please join.
cc @radicle
The next #Radicle CI office hour will happen at
Wed, Sep 10, 2025, 18:00 (that's in two days minus one hour) at https://meet.jit.si/RadicleCI
This time, there's no agenda or demo planned. I'll be there to answer questions and to chat about any topic that comes up.
If continuous integration in a distributed Git hosting system interests you at all, please join.
cc @radicle
I stumbled upon #Radicle, a decentralized #Git hosting/sharing solution: https://radicle.xyz. It provides a really good guide at https://radicle.xyz/guides/user.
Even as a hardcore fan of #Forgejo, I have to admit Radicle feels extremely well thought out. Might even be better than ForgeFed. Any thoughts? e.g. @Codeberg @jwildeboer
I stumbled upon #Radicle, a decentralized #Git hosting/sharing solution: https://radicle.xyz. It provides a really good guide at https://radicle.xyz/guides/user.
Even as a hardcore fan of #Forgejo, I have to admit Radicle feels extremely well thought out. Might even be better than ForgeFed. Any thoughts? e.g. @Codeberg @jwildeboer
A space for Bonfire maintainers and contributors to communicate