3 ms·

> Even if we've managed to rebuild and patch Hyper-V Manager from source, this is not enough for a real community project to take place. As much as I would like

> Even if we've managed to rebuild and patch Hyper-V Manager from source, this is not enough for a real community project to take place. As much as I would like to just upload the decompiled source code to GitHub to start making significant changes to it, there's no legal standing for this project. I can only go as far as streamlining the process of decompilation such that others can experiment making changes locally. I don’t know what I’m missing here but something about this whole idea rubs me the wrong way. Who in their right mind is going to do this in a production environment where there is no apparent possibility to have a shared repository for the updates? And no possibility of any support or warranty (for what it’s worth). It’s worth about the price of whatever clicks the blog post generated. It’s not like the software is that old. I don’t blame him for disliking the powershell interface but this isn’t the answer.

actionfromafar 2y ago
For years there were patches distributed for pine (or was it qmail?) back when it had a proprietary license, it kind of reminds me of that.
- prmoustache 2y ago
  This is also how Apache (hence the name) and the Berkeley Software Distribution (BSD) were born.
wolrah 2y ago
> I don’t know what I’m missing here but something about this whole idea rubs me the wrong way. Who in their right mind is going to do this in a production environment where there is no apparent possibility to have a shared repository for the updates? They said right at the beginning: > The primary goal of decompiling Hyper-V Manager is really to assess its value as a potential open source project, which is what I'm hoping Microsoft can be convinced to do.
- awakecoding 2y ago
  Thank you for clarifying - I am in no way suggesting that locally patching a decompiled Hyper-V Manager makes sense beyond its experimental value. Having gone through the exercise, it confirmed it's potential value as an open source project, but this can only realistically happen if Microsoft open sources Hyper-V Manager like they've done for many things in the past, especially software that is no longer actively developed.

actionfromafar 2y ago

For years there were patches distributed for pine (or was it qmail?) back when it had a proprietary license, it kind of reminds me of that.

prmoustache 2y ago
This is also how Apache (hence the name) and the Berkeley Software Distribution (BSD) were born.

wolrah 2y ago

> I don’t know what I’m missing here but something about this whole idea rubs me the wrong way. Who in their right mind is going to do this in a production environment where there is no apparent possibility to have a shared repository for the updates? They said right at the beginning: > The primary goal of decompiling Hyper-V Manager is really to assess its value as a potential open source project, which is what I'm hoping Microsoft can be convinced to do.

awakecoding 2y ago
Thank you for clarifying - I am in no way suggesting that locally patching a decompiled Hyper-V Manager makes sense beyond its experimental value. Having gone through the exercise, it confirmed it's potential value as an open source project, but this can only realistically happen if Microsoft open sources Hyper-V Manager like they've done for many things in the past, especially software that is no longer actively developed.