-
Notifications
You must be signed in to change notification settings - Fork 6
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
🚨 🚨 🚨 🚨 THIS REPO IS NOT MAINTAINED 🚨 🚨 🚨 🚨 #6
Comments
not maintained, but still working (for now) |
The Maintainers website does not seem to work, so I am assuming they have gone out of business and left this repo behind. As you already implied, it is only a matter of time for this to stop working. I am considering to fork this and maintain my own version but since I am not a very good programmer I probably shouldn't. Then again it still might be better than nothing. It really depends on how well I can understand the code. |
@notslang I found you in a comment in compatibility/wp-sync-db-compatibility.php, do you know anything about what happened, would you even be willing to maintain this? |
@jayhybrid - Sorry, I haven't worked with PHP or WordPress in several years. Nowadays I'm doing Elixir work. I haven't found anyone willing to maintain the repo either. See: https://github.com/wp-sync-db/wp-sync-db#looking-for-a-maintainer |
@notslang Just so I'm clear: it's legal to fork the original code from DB Pro, and remove all of the license-checking code? |
@trobriander Yep, it's licensed under the GPL. You just need to remove the branding, because that's trademarked. |
I just came form Here: wp-sync-db#167 and it looks like I've ended up at another graveyard.
The text was updated successfully, but these errors were encountered: