-
Notifications
You must be signed in to change notification settings - Fork 42
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
Is Papagayo still alive? #11
Comments
If you examine https://github.com/LostMoho/Papagayo/network you can see that there are six branches, The most recent commit is august 2016. None of these have been merged into master. Most or all of them should be. If you look at master, its called "initial commit" and it dates back to Jul 2014 -- and nothing after that. I.e. it was born dead -- it was stillborn! This project needs a project leader who will take over from LostMoho, merge the outstanding bug-fixes and branches, and move it forward. That could be you! Assuming, that is, that papagayo is worth moving into the future. I guess it is, but what do I know. |
I found that someone has taken it over! 😄 this Papagayo repo contains a rewrite of original in Qt and Papagayo-ng is fork of the original wxPython version. |
You may want to leave this issue in the open state, maybe so that its more visible to people. |
Right on. |
You should note that this Papagayo repo contains a rewrite of original in Qt and Papagayo-ng is fork of that original wxPython version. |
I hope it is!
The text was updated successfully, but these errors were encountered: