Open donovantc opened 7 years ago
I was considering using this for a project, but it'd be good to know which fork is maintained. The network is all over the place.
I'm also going to try to use this project, and I could create a fork that I could at least keep up to date, and it might be a lot easier if we could get a hold of @KBLNY to transfer ownership to someone else. what does this library need? I really want to use a custom component for the message box, but I don't know if there are any other features missing?
I think, if you're going to be making another fork with the goal of keeping it maintained, the first thing I'd recommend doing is going through the existing network of forks (in the link I provided in my last comment) and either fetching/merging them yourself or leaving an issue on them for them to make a PR into your fork with any changes they deem helpful.
Based on what I saw, there are several forks, all of which have improved upon various different areas. If there's going to be a successful active fork, it should be the one which brings everyone together.
Alright I'll check this out, thanks
unfortunately all the forks I checked out have issues disabled. Anyone seeing this can feel free to leave an issue / PR on my fork: https://github.com/Talor-A/react-native-message-bar/tree/master
We can get their attention. :)
Also keep in mind, @Talor-A, there are 6 open pull requests which you could review and pull into your own fork.
thanks @jeaye ! I'll get busy on this.
I think I'll try emailing npm to get the package ownership transferred, since it seems that @KBLNY has left github completely...
edit: I've emailed @KBLNY and npm support. hopefully we can get this resolved pretty quick.
Good idea @jeaye and @Talor-A ! 👍
Btw, I'm 1 commit ahead but it can pretty much be dismissed since I didn't really do anything useful there. Was just trying out something...
so I've now merged #27 #21 #31 and @nikolay-radkov 's contribution. I'll merge any other pulls that come my way but those seem like a good start.
I find this component quite useful but it seems @KBLNY has stopped maintaining it. Has anyone considered maintaining a fork of this component?