-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFM - quaternion #1475
Comments
Package Request ValidationWe have finished some basic validation of this request. The result of this validation can be found below: Everything looks good to our automated checks, it is now up to a human to validate the remaining steps. No action is required yet Please note that this check is currently in alpha, and may not be able to detect everything correctly. |
As the last contact with the maintainer was 5 years ago, can you try again? |
He deleted his account from GitHub, and his packages were up for grabs even then. But I can try once again as a formality... |
If that's the case then it's reasonable to assume the maintainer has stopped maintaining their packages. There's no need, in my opinion, to contact them again, under these circumstances. |
Thae package is ready, i've asked to be added as maintainer. |
That's weird, as the other packages requestd later, i have been assigned as maintainer, this one, even with the contact admins on the 4th i still haven't received any answers. |
I don't know why that was missed. I see messages today, 7 and 4 March. I've added you as a maintainer. |
Thank you very much |
Done and approved |
I am the developer of this application; however, I'm not a Windows user so cannot honestly be a maintainer of a Chocolatey package. I reached out to a previous maintainer (xdimquax) but he did not return. Getting a Chocolatey package wasn't a priority for me so this was lying in the backyard for almost 5 years... anyway:
I'm happy to work together with whoever is willing to pick this package up - despite the passed years, an update process should be straightforward as the means of building the package didn't change much. Ultimately, generation of new Chocolatey packages can be incorporated into my CI pipeline for even lower maintenance; but someone will have to be around to reinvigorate the package first, and validate the artifacts from time to time.
I DON'T Want To Become The Maintainer
Checklist
Existing Package Details
Package URL: https://community.chocolatey.org/packages/quaternion
Package source URL: https://github.com/xdimquax/choco
Date the maintainer was contacted (in YYYY-MM-DD): 2019-08-12 (as I said, almost 5 years ago)
How the maintainer was contacted: https://community.chocolatey.org/packages/quaternion/0.0.9.4-beta1/ContactOwners
The text was updated successfully, but these errors were encountered: