> Firstly, there are basically no potential colaborators for the areas i work on That's correct. On the other hand, this is a network effect, and the Nest, in

> Firstly, there are basically no potential colaborators for the areas i work on That's correct. On the other hand, this is a network effect, and the Nest, in its current incarnation, is only 3 weeks old. It's getting better every day, though. The two main features I'm working on at the moment are: - CI/CD. This is almost ready to go, it is "sort of" working. One issue that I fixed recently is that Pijul versions are tricky to compute: change A, followed by B, is the same state (guaranteed by design) as B, followed by A. Our version identifiers handle that now (try `pijul log --state`). - Social features, like discoverability, recommendation of collaborations. We're really just getting started at this, and figuring out what works best. I should add that until two weeks ago, the Nest would stop accepting connections at random times, or crash. It's much more stable now, and we can finally think of adding features. > Secondly, it is much less mature ass a platform There are tags for issues. You can configure them in the "Admin" page of your repositories. They're not used very much for Pijul itself, because most issues so far have been closed within minutes or hours after their creation. > Which is a mind twise of an idea. But they say they solved it, so nice. As one of the authors, I can tell you it wasn't easy to get everything to work together, especially for conflicts. But the theory is clear and sound now (and I have good confidence that the implementation is, too): any two patches that could have been created independently can be pushed to a remote repository independently from each other.