Forks are expensive, socially, organizationally, and so on; especially for a project that has no mindshare to begin win. Forking a project just to fix a build p

Forks are expensive, socially, organizationally, and so on; especially for a project that has no mindshare to begin win. Forking a project just to fix a build problem is productive. Too many projects just dump the code onto Github with no attempt to create a community around it. Community participation is ultimately what makes or breaks an open source project. I'm not saying one has an obligation to the world to service pull requests, but if you release something and make zero effort to engage, then don't be surprised if your project dies. In this case, the codebase is also sufficiently complex/arcane that it's hard for anyone to just pick it up and evolve it meaningfully without any aid from the original author. Without knowing all the details of Hyperdex's internals, I do think that it might be a worthwhile thing for someone with sufficient time and interest to resurrect it, though.