React-native-fs: **DISCONTINUED** How to proceed anyways? I'd like to continue

Created on 2 Apr 2017  路  7Comments  路  Source: itinance/react-native-fs

This library was discontinued some days ago. Any ideas how to keep it alive? 18 open PRs, 44 Contributors... These numbers send a clear signal!

Since we make heavy usage of this lib in several projects, i'd like to continue this project. I know this code on all three layers (javascript, ObjectiveC, Java) very well and has debugged it quiet often. A switch to another library is currently not planned in our projects.

However, where to start to continue?

搂1 First i'd like to ask @johanneslumpe if he is interested to transfer the ownership to another person (e.g. me)? If not, am i allowed to continue this repo under a similar name like "react-native-fs2"?

搂2 Second i renamed my fork (which is updated to the very last commit here on master) to "react-native-fs2" as a working title for now to be able to publish it on npm in upcoming days until a solution is in sight (currently it isn't published anyways).

搂3 Third, if 搂1 isn't possible, i'd like to ask authors of the recent, unmerged contributions to submit their PR to the "new" library.

Any ideas? Answers? Questions?

Most helpful comment

@itinance @Antonhansel I am not using react-native actively at work and my day job takes a huge chunk of my time, thus leaving no extra time to maintain this library. I haven't been able to keep up with all the changes to react-native and the codebase became stale rather quickly. Long story short: I can transfer ownership to @itinance but it would be nice if original credit would remain in place somehow. How does that sound?

All 7 comments

I hope the community can continue to work on this but I think it will depend on the reasons @johanneslumpe stopped maintaining the project. Is it more about the time it takes ? Or is there something else ?

Thank you @johanneslumpe for your hard work and thank you @itinance for offering to maintain the project :)

Oh yes, thank you @johanneslumpe for this excellent work! I was totally shocked yesterday that i've forgotten to mention it separately in my opener :)

@itinance @Antonhansel I am not using react-native actively at work and my day job takes a huge chunk of my time, thus leaving no extra time to maintain this library. I haven't been able to keep up with all the changes to react-native and the codebase became stale rather quickly. Long story short: I can transfer ownership to @itinance but it would be nice if original credit would remain in place somehow. How does that sound?

Sounds great @johanneslumpe! Of course i will keep original credits. I sent you an invite on linkedin to introduce myself :)

@itinance
what's the progress on this? I gotta decide whether to stick with this or not. At this point this lib is in a rather bad condition

hi @br4nnigan I'm in contact with @johanneslumpe. He will transfer ownership to me in upcoming days.
As said before, we use this library very heavily in several projects and don't want to let it die :)

Transfer is done. Thank you very much for your trust, @johanneslumpe, and once more for the awesome work on this library!

Over the next days (and weeks for the complicated ones) i will view the open PRs and merge if valid and possible

Was this page helpful?
0 / 5 - 0 ratings

Related issues

PimDeWitte picture PimDeWitte  路  4Comments

1556173267 picture 1556173267  路  3Comments

onzag picture onzag  路  3Comments

AgNm picture AgNm  路  4Comments

npomfret picture npomfret  路  4Comments