Are you supporting Metrics.net?
stephanstapel opened this issue · comments
Hi etishor,
I was just wondering if you are still supporting Metrics.NET. It'd be great to see a sign of life for this great library!
Cheers,
Stephan
+1
+1
I used to work with etishor. Sadly, I must inform you that he will not be continuing to support this library. While there is a chance a few of us (his former work colleagues) may support a fork of it sometime in the future, things are uncertain.
Right now, the best thing would be if those who are interested made a spin-off of Metrics.NET, so the community around it can go on. Etishor would have liked that immensely.
Thanks for the info. Your note makes it sound like something bad happened to Etishor. Is he okay? There's a growing community who appreciates the work he's done & will surely carry the torch!
On Jan 23, 2016, at 3:46 AM, Bogdan Galiceanu notifications@github.com wrote:
I used to work with etishor. Sadly, I must inform you that he will not be continuing to support this library. While there is a chance a few of us (his former work colleagues) may support a fork of it sometime in the future, things are uncertain.
Right now, the best thing would be if those who are interested made a spin-off of Metrics.NET, so the community around it can go on. Etishor would have liked that immensely.
—
Reply to this email directly or view it on GitHub.
I'd be open to helping maintain a (new) "official" fork of Metrics.NET. Anyone else interested?
I am very sad to hear that bad things happend to etishor. Thanks a lot for letting us know!
Is there a chance to open this repository for new collaborators so that we can re-unite the forks under the original umbrella?
I propose we move the repo to an organization so that no one person has exclusive access.
I just forked the repo into this org:
https://github.com/metrics-net
I've been maintaining a repo containing an updated InfluxDB integration for Metrics.NET. I'll move that to this organization as well.
Not sure what we can do with NuGet besides renaming the package?
On Jan 23, 2016, at 1:14 PM, Stephan notifications@github.com wrote:
I am very sad to hear that bad things happend to etishor. Thanks a lot for letting us know!
Is there a chance to open this repository for new collaborators so that we can re-unite the forks under the original umbrella?—
Reply to this email directly or view it on GitHub.
Concerning NuGet: maybe we can just write to support@nuget.org ?
That's not good to hear. I also have a fork for an asp. Net 5 adaptor
@bogdangaliceanu is there anyway to get this news pushed a bit higher on the project. I don't think people are aware of the status.
@amccool I don't know. I will have a talk with some people at work to come up with a plan.
If anyone knows what GitHub's protocol is regarding the accounts/repos of deceased members, please let me know. I haven't been able to find anything. I guess the only thing to do is just contact GH support directly.
I (or someone else who knew Etishor) will let you know once we have news.
That is very sad news, @bogdangaliceanu. I am so sorry to hear this.
Will you ask GH for help or shall I?
@bogdangaliceanu https://help.github.com/articles/transferring-a-repository/ and probably need to use the "contact a human" button at the bottom
OK, I spoke to the team at work and we decided we'd like to at least try to continue this project.
Etishor was the one managing the company account and so we need to talk to GH to give us access and have the project transferred there.
We will contact support soon and get things started. Expect updates from either myself or @hinteadan @LatisVlad @PaulParau
Thank you all for your help and interest
I tried using "contact a human" twice but got a 405 Not Allowed when submitting the request.
Will try again later today or tomorrow.
This is what they told me:
Thanks for reaching out. As you can imagine, in cases such as this our first priority is to protect the privacy and security of the account of the deceased.
In order to make any changes in ownership or access to the account, we would need to collect the information below from the person requesting access. Is there a family member or business associate of the deceased who would be best suited to request access to the account? Please note that we do ask for documentation to prove that the requesting party is lawfully allowed to access the account. If that is someone other than yourself, you may want to forward this information to them.
I hope this helps. If you have any other specific questions, feel free to ask.
Cheers,
Matt
Deceased or incapacitated information
Full name
Address
GitHub account name
If a paid account, last four digits of the credit card on file for verification
Email address(es) used on the account
Requestor information
Full name
Address
Relationship to deceased or incapacitated (co-worker, business partner, next of kin, etc.)
Photocopy of the requesting party's photo ID (Government issued ID or Driver's License)
Documentation to prove that the requesting party is lawfully allowed to access the account
GitHub account of the requesting party, if applicable
Request information
Details about what you are requesting to be done with the account (eg. access to the account, deletion, stopping payments, information about the account etc.)
Verification
Proof of Death or Incapacitation, eg. Official, government issued death certificate or certified document signed by a medical professional in charge of the care of the user, if the user is incapacitated; or, obituary or news article about the death
Contact information for local authority for verification
Please also provide a statement given under penalty of perjury that the information that you are submitting is true to the best of your knowledge and that (again, to the best of your knowledge) you are not aware of any other third-parties that might have an ownership or copyright interest in the account or its contents.
Thank you. I'll start chasing down those things.
Good progress!
Did you contact nuget.org as well or shall I cover that?
I sent an email to support@nuget.org
@stephanstapel any response from nuget.org ?
@mnadel @bogdangaliceanu did you guys come to a consensus on where this repo might transfer to? @bogdangaliceanu was your company going to become the maintainer?
@amcool I received a reply from Nuget. Transferring the ownership of the nuget package shouldn't be a problem, they suggested that the new owner is the same as the new github owner. So the github ownership should be progressed first!
Thank you all for showing interest in continuing this project.
We are still working on this issue, retrieving all the information required to gain ownership has proven to be more difficult than anticipated. I am also awaiting a response from support to see what can be done about our company's organization. We are trying to get to the bottom of this quickly and we'll let you know as soon as we have more to share.
Hi everyone,
We finally made some progress and solved the issues with our organization's account.
We forked the project there Recognos/Metrics.NET and going forward, we intend to maintain and support this as an 'official' fork. Anyone who wants to contribute is of course welcome to do so.
Regarding open pull requests and issues, does anyone know of a way to copy them to a forked repository? I guess an alternative would be to manually recreate them on the forked repo.
We have not yet solved the nuget situation; most likely we'll have to create a new package. We'll keep you posted.
Hi Paul,
the message I received from nuget (yigalatz@microsoft.com) was:
It will probably easiest to pass ownership to a maintainer if the github repo. If that issue was resolved please let us know who should own it and we will work on validating the identity and ownership
So it shouldn't be too difficult to take over the existing nuget package (or at least to remove it).
Cheers,
Stephan
One last update: we also solved the nuget situation and are able to push updates to the original packages (we also published a new prerelease version yesterday). So everything's set to continue the project.
@PaulParau : that is great news, thanks a lot for your effort!
Thanks guys. Most appreciated. Sorry about your loss.