saz
Is this module dead?
This module's Puppet Forge page lists the module as "approved" which indicates that this module is actively maintained; however the last update was well over a year ago and the issues and pull requests are stacking up. The download count for this module on Puppet Forge is very high and people are still deploying it, but it is now buggy.
Has this module been abandoned? If so, it would be nice to know for sure, so I can look at the other forks or make a new one myself.
No :) I'm currently in the process of merging all PRs on all of my modules and I'd like to move those modules to vox pupuli
@saz We'll need to compare features you have and see if there is anything we can import as there is already a voxpupuli/puppet-rsyslog that we migrated from @crayfishx
Hey @saz
Is has there been any movement in the comparison with the voxpupuli module. I can see that there has been no merges or releases in over 2 years.
We have recently received a ticket to consider puppet/rsyslog for approval. I am interested to hear your thoughts before we progress with this ticket.
A reply as soon as possible would be greatly appreciated.
Many Thanks Puppet Modules Team.
Due to lack of response and activity, the approvals team have made the decision to remove the approved status from this module in favor of puppet/rsyslog
We would like to thank you for taking the time to contribute to modules on the Forge.
@pmcmaw Why is there a deprecation message shown on the forge? https://forge.puppet.com/saz/rsyslog
It looks like, as if this was a decision I made, which is not the case.
I don't have a problem if the approved flag gets removed, but I think it still should be my decision, if or how this module will continue.
Hey @saz
Apologies, this seems to have been a mistake on our side as the initial plan was just to remove the approved badge. I can ensure you this will be resolved within the next day or so. I want to take the time to apologize for that oversight on our behalf.
Many Thanks Puppet Modules Team.
@saz This has now been resolved. We would like to thank you for highlighting this and we will ensure it does not happen in the future :-)