You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ensures that developers don't waste time implementing your package or creating pull requests that you will never merge, and ensures that the active fork gets the attention it deserves (and the pull requests and donations).
That is valid feedback. While we use this library extensively for our core products and have ambitions of revitalizing and improving it, during the last few years our organization hasn't had the resources to regularly maintain or upgrade the package. On and off I've brought it up that we need to either dedicate resources, find a new maintainer, or archive it. The conversation never really goes anywhere. I'll bring it up again and push a little harder on a final decision. Thank you for the feedback.
@rpenfold I would be very happy to add you or some others of your company as maintainer to my fork and we work on the lib together!
Saves resources on both sides and best for the community.
If you want to we also can have a chat about it - feel free to contact me any time
Joltup, when you forked the original
react-native-fech-blob
package the owner of the repo agreed to archive it and link to your project.Now that you have abandoned the project too, please have the same courtesy - archive it and link to the latest fork, probably https://github.com/RonRadtke/react-native-blob-util/
This ensures that developers don't waste time implementing your package or creating pull requests that you will never merge, and ensures that the active fork gets the attention it deserves (and the pull requests and donations).
Tagging the last committer @rpenfold
The text was updated successfully, but these errors were encountered: