search

reststate / reststate-vuex

Zero-configuration web service client for Vuex
https://vuex.reststate.codingitwrong.com
Other
72 stars 19 forks source link

Change npm & GitHub ownership #283

Open geoidesic opened 3 years ago

geoidesic commented 3 years ago

Hi @CodingItWrong could you please give me ownership? I'd be happy to take this over.

If you could give me ownership over the reststate GitHub account and the npm account I'd be happy to take over, maintain and grow this library. I think that may be better for existing users than me creating a fork that then has to have a new npm registry account etc. (my npm username is the same as my GitHub handle).

Please let me have your thoughts.

CodingItWrong commented 3 years ago

I'm not comfortable passing maintainership of this library to someone else, because I want to ensure users make their own decisions about whether to trust a new maintainer.

But since you have a solid track record using the library, if you publish a fork I would be comfortable linking to it at the top of the readme.

issa commented 3 years ago

May I enquire why you decided to no longer maintain it? Just because of time and resources? Or are there some fundamental problems with the library?

CodingItWrong commented 3 years ago

@issa Yes, because of time and resources, related to the fact that I'm no longer actively developing in Vue, so not getting a chance to use the library actively. No real fundamental problems with the library, no.

lucianholt97 commented 3 years ago

There's also a typed alternative which is worth looking at: https://www.npmjs.com/package/@anny.co/vue-jsonapi-orm

freelock commented 3 years ago

Just stumbled across this library, which seems to be such an elegant solution compared to the alternatives. Sad to see it marked unmaintained -- @geoidesic are you planning to pick this up?

geoidesic commented 3 years ago

I'm not comfortable passing maintainership of this library to someone else, because I want to ensure users make their own decisions about whether to trust a new maintainer.

But since you have a solid track record using the library, if you publish a fork I would be comfortable linking to it at the top of the readme.

Ok thanks. I'll do that then. What do you suggest wrt npm? Most people will install this via npm and currently that will install yours. Should I start a new npm repo for my fork?

CodingItWrong commented 3 years ago

Yes, I'm recommending both a separate npm package name and a separate GitHub repo.