LykkeCity / NBitcoin.Indexer.BCC

MIT License
0 stars 0 forks source link

Nuget unlist #1

Open NicolasDorier opened 5 years ago

NicolasDorier commented 5 years ago

@bijakatlykkex can you unlist your package on Nuget, this show as me being the creator?

image

Also, NBitcoin.Indexer support natively altcoin now so it should not be needed.

bijakatlykkex commented 5 years ago

@NicolasDorier This is under consideration to be resolved. I will update accordingly.

bijakatlykkex commented 5 years ago

@NicolasDorier

Hello,

As it is apparent, the problem has not been solved yet. I first describe the situation in more detail and then present some possible solutions.

The situation:

I should first declare the reason for the usage of your name in Nuget.org for the component. It was not because, for example, to promote the component as being written by a recognizable author to increase its downloads, etc. It was just to fill the author field there (in Nuget.org), by some reasonable text, and not removing the name of the person who had done the most of the work, giving the appropriate credit, and also as stated in the license “The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software”. This is for the “Ni... Do...” part. Also since I wanted to mention, the fact that the component is not completely your work and it has minor changes (For instance, in the case there were bugs after your work, …), I added the “(For Original)” part.

Unfortunately your request here, was remained unnoticed by me for about a month, then I noticed it and started my actions. One major problem for honoring your request is as follows:

I have forgotten my password for the account created at Nuget.org and the account has been created with my Lykke email; since Lykke and I have stopped working together some months ago, I do not have access to my email account anymore; So no more password recovery and it seems the current situation for the package, falls under the “Orphaned packages” described here: https://devblogs.microsoft.com/nuget/managing-package-owners/

The other problem is the subject of ownership of the package at the current stage (besides the subject of management, when it is no more possible); Although it may be a good topic of discussion who owns what, when somebody is no longer working with a company, and it may be reasonable to study cases independently; for this particular case I mostly think, since the Nuget package is listed under a Nuget account created with a Lykke email account, using a github repository listed under Lykke name, by my role at Lykke; when that role ceases to exist, the new owner will be Lykke itself (some kind of inheritance).

With the above situation, I contacted Lykke, and the final status has been “we will delete the records in a while”.

Some possible solutions:

1- You can continue waiting for Lykke to take the ownership of the Nuget package, and Lykke will correct the problem.

2- You can contact Lykke support regarding this, in the process, you can reference my support request numbered 69671.

3- You can use the “Report” link on the component page on Nuget.org, and ask the component to get unlisted. If Nuget.org still counts me (as an individual not having my role at Lykke anymore) as the owner, I hereby declare, I am fine with the package being unlisted, author name removed or similar. I think since by unlisting the package, the package usage references (for example in project files) still remains intact, there will be no problem for package users.

I hope one of the above will fix the problem.

NicolasDorier commented 5 years ago

argh, pain in the ass. I will try report, we'll see.