3 ms·
Forking the code is "easy" (OK, maybe not based on the other comments), but anyway... Another (persistent) problem has been the crates.io namespace. You can f
by ansible 7y ago
Forking the code is "easy" (OK, maybe not based on the other comments), but anyway...
Another (persistent) problem has been the crates.io namespace.
You can fork actix, but then you'll need to come up with a new name for it, and then educate the wider community of that. It is a big hassle, and slows adoption.
Adding onto the issue is that crates.io does not (yet) support the username/projectname naming scheme as on github and other popular code repositories. So it isn't enough to just people to go to a different username, you must use a new project name.
- hobofan 7y agoI don't see that as a major problem in this situation. Given that the actix author already wanted to take a step back after the last incident, and also seems to be generally okay with giving the project away, a fork could also be officially advertised. Word also travels fast in communities, and if a viable fork does come up, people will quickly start to recommend it.