-
Notifications
You must be signed in to change notification settings - Fork 2
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
Ownership transfer request #9
Comments
Thanks for initiating this. My pull request was made > 1 year ago.
Kevin Gin
…On Mon, Oct 1, 2018, 10:08 AM Brian Mearns ***@***.***> wrote:
It looks like this project has been stale for quite some time; @gyllstromk
<https://github.com/gyllstromk> would you consider transferring the
project on both github and npm to me? I would certainly welcome any
additional contributions you care to make, but I can provide active
maintenance as well as forward development, including fixing a critical
issue (#5 <#5>), if you feel
like you're unable or uninterested in doing so.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#9>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AR0uZn3KIf4EB6X9xACPNVY24KPvOXAuks5ugkwFgaJpZM4XCfxv>
.
|
@mearns added you as a collaborator, is that sufficient? |
Thanks @gyllstromk , that would work fine for me. Github is showing me an error, however, that the invitation cannot be found.
|
@mearns, @KevinGin If you guys still positive about contributing to xrange, you're welcome at parzh/xrange. Since the ownership is tranferred to me, this will be the main repository for the package |
Cool, thanks @parzhitsky. Looks like my MRs were merged; appreciate you picking this up 👍 |
It looks like this project has been stale for quite some time; @gyllstromk would you consider transferring the project on both github and npm to me? I would certainly welcome any additional contributions you care to make, but I can provide active maintenance as well as forward development, including fixing a critical issue (#5), if you feel like you're unable or uninterested in doing so.
The text was updated successfully, but these errors were encountered: