Project needs new maintainer

[p3root]

Hey bro!

You created something the community loves and needs. But leaving pull request unanswered and ignore issues is a horror!

Your repository is used by 1.4k other packages. Therefore please fix the issues! It is a pain in the ass for all developers out there getting errors just because someone thought it would be could to write some OSS and doesn't maintain it.

That's not how OSS should work!

cheers

[dazoe]

I agree, this project needs a maintainer. Any nominations?

[ChildishForces]

@p3root whilst I completely agree that it's a shame this project hasn't been maintained since 2015. @dazoe is under no obligation to work for you or any other developer for free. If you want this project to be maintained, either do it yourself or find an alternative.

[p3root]

@ChildishForces!

Don't get me wrong. Every OSS library I use in a commercial way gets some kind of sponsoring from me (except big company projects), in form of money or working time. That's how OSS should work.

But if I own a repository with 1.4k dependencies and about ~70 dependents on NPM, I should handle that kind of power responsible.

A new maintainer should have been chosen a couple years earlier. Also don't forget to allow the mantainer to access the npm repository as well to publish new releases.

I would like to mantain this project, but only with support from other too.

@dazoe thanks for your fast response :)

[palasinio]

https://techgaun.github.io/active-forks/index.html#dazoe/ed25519

[gmahe]

I've noticed master...gaoxiangxyz:master
They have done a good job!
@Erikma has added the Node v12 compatibility as well.

It would be nice to check out if their code is safe and correct and merge it?

[palasinio]

I have this one in use:
https://github.com/pokt-network/ed25519/commit/351baecc4611bb014390b44c6bbee417ec1bd82d

More interesting is the conversion of curve25519.
@volschin managed to replace nan with node api:
volschin/node-curve25519@80af96f

This seems a lot more elegant and maybe run with node 13 & 14.

[erikmav]

@dazoe I'm willing to become a maintainer.

[erikmav]

Note for those watching this issue, I accepted Dave's collaboration request on this repo, awaiting permissions to publish the package on npmjs.org. Please note I have a (very busy) day job in the software industry so this will be free time meaning high latency. Given that, my priority list for updates:

• Reduce or eliminate dependency on OpenSSL (Build error on Node 10 and OpenSSL 1.1.1a #21 , Path for "C:\OpenSSL-Win64\lib\libeay32.lib" is hard-coded. #22 , changes in some forks)
• Node 12 & 14 support (synthesize various commits and PRs across the forks) for Add support for Node 12.0.0 #23
• Add GitHub Actions based build, packaging, regression testing
• Reduce or eliminate build warnings that have increased since the code was created

[gmahe]

Good to hear @Erikma and all the best!

[dazoe]

I do not have permissions to add @Erikma to the package on npmjs.org. the package is owned by an organization. I have reached out to npmjs support to try to resolve this.

[erikmav]

@dazoe Any motion on the permissions issue? I'm merging changes from various forks and getting ready to push an update for Node 12.

[erikmav]

One alternative if that's unresolvable is to publish under a new package name like "ed25519.new" under a new "ed25519" npmjs org, and advertise the change in as many places as possible. Far less satisfactory though as breaking package naming is a big deal.