search

windward-studios / ikvm8

Other
173 stars 36 forks source link

IKVM.* package ID reservations on NuGet.org #19

Closed NightOwl888 closed 2 years ago

NightOwl888 commented 2 years ago

Hi, now that we are releasing new packages on NuGet.org from https://github.com/ikvm-revived/ikvm, we have run into a snag. It seems someone has reserved the IKVM.* package IDs so we cannot upload new packages. There are new features in the works that we would like to release, but as things stand we cannot do so without coming up with a new name for the project that isn't already taken (instead of IKVM).

Given the fact that you released as IKVM.WINDWARD, my suspicion is that you were the party that reserved the package IDs (since clearly you were there to release that package). But being that you were instrumental in setting up https://github.com/ikvm-revived/ikvm, this isn't really a conflict of interest. It is documented that there is a way to delegate package IDs to 3rd parties. If you were the party that reserved the IDs, could you please provide access to the ikvm-revived organization to use them?

And of course, if you did not reserve the package IDs, do you have an idea who might have? We have already contacted NuGet.org support, but not sure whether they will respond favorably to our claim over these IDs. We aren't trying to stir up trouble, just trying to keep the IKVM community intact as much as possible.

NightOwl888 commented 2 years ago

Never mind, we got a reply from NuGet.org support and they said it was reserved for "security reasons". Trying to resolve this with them.

NightOwl888 commented 2 years ago

@windwardadmin - No need. NuGet has granted the IKVM.* package IDs to us. If you intend to continue using the IKVM.WINDWARD.* package IDs and you wish to release additional packages, let us know and we'd be happy to delegate them to you.

But now that we have a production release that supports .NET Core, maybe it would be better if you migrated to the IKVM package so we can pool development resources.