So WPRIG is dead ? #840
Replies: 2 comments
-
Who said it was dead or dying? That would be news to me, and I am the lead maintainer. I think you might be making a bit of an assumption. Just because there hasn't been any commits in 3 or 4 months doesn't mean it's dead. When I joined the team, nobody had committed anything for 2 years. 8.2 is relatively new, so I am not surprised that things are not working there. Perhaps submit an official issue for any failures you are seeing on 8.2? I can't help fix issues I don't know exist. With that said, if you would like some transparency, I am happy to provide some. I have been the only person contributing any significant amount of code to the project for over a year now. Unfortunately, all other maintainers/contributors have either left due to other interests or have silently gone incognito. I wish there were more of us, but there is not. I've given up on recruiting efforts. Now I just fix things that are within my skillet as they arise. I led a team of devs last Winter that had a lot of success using WP Rig to build out high traffic corp website. So no, it's not dead. |
Beta Was this translation helpful? Give feedback.
-
Thanks for answering! To my defense I did phrase it as a question. :-) I am grateful to you that you are holding out, as it seems, on your own. I based what I said on non-responses to my questions, as well as to a bug report (#837 (comment)) that I have experienced as well. I am not a heavy-duty developer so I have no need for new features. Just keeping dependencies current would receive five stars from me. I think @zedebugger did submit an official issue (quite serious from a UX perspective but easily fixed with some z-index trickery) that never received any attention (link above), but I'll try to figure out how to submit a pull request and propose a code addition to deal with the "invisible menu issue". I am happy you are still committed to the project. |
Beta Was this translation helpful? Give feedback.
-
I ask because apart from the batch of updated packages on 2 April there has really been no activity here. Attempts at discussion, bug reports and questions are left blowing in the wind since June it seems.
I have loved wprig ever since I discovered it 3 or 4 years ago. I'd love to continue using it, but I currently can't launch new projects because in Debian 12 I can't get it to run as
gulp-phpcs
plugin throws an error. I think it is due tophp 8.2
, but I don't know and no-one seems interested in assisting or even saying they don't wish to assist. 8.1 is not available in Debian 12.The lack of code activity and the lack of indications that code maintainers are even reading this forum suggests to me that wprig is silently dying.
It's open source, people move on or don't have the time, and I respect that. Personally I don't have the skills to step in as a maintainer.
But one of the tenets of open source is also transparency, so let's be transparent about the status of wprig and allow adopters (who would like to stay on if there were life in the project) to move on if the project has been abandoned.
It's only fair to be up-front about it.
Beta Was this translation helpful? Give feedback.
All reactions