29 ms·

I mean, why can't you? If it's actually openly licensed you're free to fork it and fix the bits you want and use what you need. The ability to allow contributo

I mean, why can't you? If it's actually openly licensed you're free to fork it and fix the bits you want and use what you need. The ability to allow contributors to conttibute code is a bonus of it being open source but even if it doesn't accept or merge pull requests, it's just as well imo.

httpsterio 4y ago
Can't edit, the "why can't you" was a reply to "you can't really do open source like that"
atombender 4y ago
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.
samsquire 4y ago
You must know how difficult and complicated projects such as databases are. You need to be an invested person to casually read the sourcecode of postgres or random database project. I have some ideas on HTTPS://GitHub.com/samsquire/ideas4 of how I would cause programming to be easier to pick up and run with a piece of mature software. There is inevitably A LOT to learn to onboard yourself with a large codebase, it takes months or years to get familiar at work so it would take the same or longer for open source.

httpsterio 4y ago

Can't edit, the "why can't you" was a reply to "you can't really do open source like that"

atombender 4y ago

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.

samsquire 4y ago

You must know how difficult and complicated projects such as databases are. You need to be an invested person to casually read the sourcecode of postgres or random database project. I have some ideas on HTTPS://GitHub.com/samsquire/ideas4 of how I would cause programming to be easier to pick up and run with a piece of mature software. There is inevitably A LOT to learn to onboard yourself with a large codebase, it takes months or years to get familiar at work so it would take the same or longer for open source.