Maintainers

[perry-mitchell]

It's quite clear that this repository is lacking maintainers to help review and merge PRs.

I can't offer a day-to-day availability to do so, but I would definitely have time each week to dedicate to helping keep this library alive and help merge the occasional bugfix etc.. I use it very regularly in many projects, both personal and work. I'd love to become a maintainer of ulid/javascript, and I'm sure there are others that would readily do the same.

@alizain would you consider adding someone as a maintainer? I'd be happy to discuss the responsibility further if you'd accept help for this project.

[jpbourgeon]

@alizain
Hello ! ULID is a great piece of software. I use it for all my uid needs and I am also willing to help you make it last ! I agree with @perry-mitchell that you should add (a) maintainer(s) to the repos and/or the organisation. To help you sort and handle the opened issues and PRs.

You may also consider archiving the whole project to make it official that it is not supported anymore. The community (we) would then be free to fork the repo and keep it alive there.

Please, take a few minutes today to, at least, configure @perry-mitchell and/or me as maintainers of the javascript package.

I look forward to your answer !

[jpbourgeon]

You may also consider archiving the whole project to make it official that it is not supported anymore. The community (we) would then be free to fork the repo and keep it alive there.

It would be a real shame because the project is downloaded 277,353 times per week on NPM, on a steadily increasing trend!

[jpbourgeon]

In the meantime or as a replacement, there is a maintained implementation of the ULID specs in https://github.com/aarondcohen/id128

[perry-mitchell]

I've built a replacement, which I'll be maintaining from here on out: ulidx. It'll adhere to the same spec, and is more or less a transposition of this library (but with the inclusion of some PRs). It also has almost all of the same tests, to confirm that it's functional.

ulidx because it's designed to target node/web/webworker environments.. and eventually react-native.