4 ms·
Tell me you don't read everything without telling me you don't read everything. That doesn't answer why he would clone a fork of his project and not just contri
by byteknight 3y ago
Tell me you don't read everything without telling me you don't read everything. That doesn't answer why he would clone a fork of his project and not just contribute to the main project
- Timon3 3y agoBecause the project got taken over by Canonical. The README states why it was forked, and contributing to a community-led version of a project swallowed by a commercial entity makes a lot of sense to me.
- catchnear4321 3y agowhat’s interesting is just that, the big name is contributing. not leading. at least not officially. at least not yet. this is a signal, an unusual one worthy of hn.
- birdyrooster 3y agoBecause they don’t want their repo cluttered with PR branches. It’s maybe not obvious, but in a public project anyone could branch and submit a PR which leads to a mess. This is how it’s done in many large companies as well, not just OSS. It saves you from scratching your head wondering if deleting this year old feature branch is actually throwing good work out. The news is that this person is working on the project, this clone is evidence of that.