Closed bufferoverflow closed 5 years ago
I helped maintain this project while I still had repos on a gitlab instance, but this is no longer the case so my interest has dropped off.
The repo + npm name belongs to @moul though, its up to him if he wants to give it up.
I’m not specifically attached to the package name
What the best way to make the migration painless for people using this package today ?
a breaking change notice, info within this repo‘s README.md and bump major version number. API compatibility is something that has to be checked. However, it started as a fork und is now a rewrite so showing this with a major version change should be sufficient. See https://github.com/jdalrymple/node-gitlab-api/blob/master/README.md#contributors
I recommend to pass the gitlab npm package over to @jdalrymple , so he can publish 3.0.0 , his username on npm is https://www.npmjs.com/~jdalrymple and mark this repo here as deprected.
@bufferoverflow I added @jdalrymple as maintainer on npm, don't know if it's enough for him to continue?
I'll try tonight! Thanks :)
@moul I was able to publish the newest version under the gitlab npm package! Seemed to have worked well.
@moul , @jdalrymple awesome collaboration!
Yea :smile: thanks @moul !!!
A update in the README would be wicked if you find the time!
Not sure what to do about the source code repo, the node-gitlab group is a lil outdated with the most recent thing being since 2015 :(. I could rename the node-gitlab-api repo if it would make it easier to understand?
Hey! So what was the consensus ?
A lot of people started to use
node-gitlab-api
which is quite well maintained.There is a discussion about the name of the package, see https://github.com/jdalrymple/node-gitlab-api/issues/30
If this library here is unmaintained, the npm name could probably passed over to the more active project, so people can find the lib easily.
What do you think?