Link to a maintained repository in the README

[horyd]

This repository is very popular (over 5k stars as of mid '17) and issues and PRs are compounding as it is no longer maintained.

There are many forks to this repo which take care of some/all of these issues. It might be a good idea to add alongside "THIS IS NOT BEING MAINTAINED" a link to one of these repositories if the fork owner is comfortable moving it forward.

If you can recommend a working fork or run one yourself please mention that here, then we can create a PR to direct users to your repository instead.

[horyd]

This fork looks the most promising I think?
https://github.com/maicki/why-did-you-update

[garbles]

I think it's a good idea to forward developers to another repo; though I'd rather wait for a fork that is consistently referred to as an alternative. Feel free to stir up support for something else! - I don't care if it's a fork or not. Thoughts?

[neptunian]

why not just add a collaborator to help maintain this repo?

[Noitidart]

I really liked this, it's very useful. 5k stars shows a lot of people rely on it. Is there no alternative? @garbles are you looking for monetary incentive in order to keep maintaining it?

[garbles]

Definitely not. I wrote this has a hack to help me debug a client project and barely touched it after that. I have no interest in maintaining.

why not just add a collaborator to help maintain this repo?

Who?

[neptunian]

@garbles good question. perhaps you can create a help wanted issue and see if anyone responds?

[gwmccull]

@maicki any thoughts on this? I've been using your fork

[maicki]

We had a need for the project and so I forked it and integrated the fixes from all of the scattered forks as with latest changes from React as well as React Native support, it didn't play nicely with it back then.

It seems like people already using my fork, so if you all ok with it, we can remove the not maintained header from my fork and I will try to support it as good as possible.

First step I guess would be to push a new version to npm with the current master of my fork.

[sebinsua]

It seems like people already using my fork, so if you all ok with it, we can remove the not maintained header from my fork and I will try to support it as good as possible.
First step I guess would be to push a new version to npm with the current master of my fork.

This seems like a good idea.

[garbles]

@maicki thanks for replying. Would you rather I give you commit/publish access to this repo or add a note in this repo's README about your repo? Your call 😃

[garbles]

If you decided that you wanted commit access, it would be a small matter of merging your fork back into this.

[maicki]

@garbles I would propose for the sake of overhead now and in the future to detach my fork from original like described in here: https://help.github.com/articles/why-are-my-contributions-not-showing-up-on-my-profile/#commit-was-made-in-a-fork - And you could change the README and point to the repo on my side.

We can also take a look at the current open issues and decide which are still relevant and move them over.

Let me know if this would work for you.

[garbles]

@maicki this is fine with me. I will update the README to point to your fork. Is this you on npm?

[maicki]

@garbles Yep that's me. Thanks!

[jordie23]

Aly idea when we can get @maicki 's version as the NPM package ?

[jordie23]

Also, @maicki there is no way for people to raise an issue on your repo yet. (Not public?)

[gwmccull]

not quite the same, but I've been using the maicki fork in my project for a while

{
  "devDependencies": {
    "why-did-you-update": "github:maicki/why-did-you-update"
  }
}

[maicki]

@jordie23 I opened the issue section last week.

I will also work to get a new version (I would say 0.1.0) with the current head on to npm.

We may should also look into looking at the issues / PRs in this repo and see which are still valid and move them over or close them.