Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why is this fork required? #16

Open
0atman opened this issue Dec 3, 2024 · 1 comment
Open

Why is this fork required? #16

0atman opened this issue Dec 3, 2024 · 1 comment

Comments

@0atman
Copy link

0atman commented Dec 3, 2024

Hi @wrenger, I assume this fork was needed because the last commit upstream was 10 months ago? That'd be fair enough.

If there's anything more official about the upstream plugin being abandoned, I couldn't find it quickly.
Thank you for your work!

@wrenger
Copy link
Owner

wrenger commented Dec 3, 2024

Hi @0atman, the primary reason for this fork was the number of changes I wanted to make. With the low frequency of updates to the original plugin, all the new features, fixes, refactoring changes would have taken a while to be merged. They might even be too big to be accepted, especially as the author stated that he stopped actively developing the plugin.

The first minor fixes actually were submitted and merged to the original.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants