You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Some components of the playbook have been officially declared as unmaintained/deprecated, while others apparently seem to have been abandoned for years after the playbook was born and components actively developed at that time were added, such as ma1sd.
Describe the solution you'd like
I think it should be no problem to keep those services in the playbook as long as they work properly for the most cases, but a friendly disclaimer on the documentation that the upstream project seemingly has been inactive for a certain period of time (a year, for example?) should help us to figure out where to look at when an unknown error occurs.
As it is possible that the component is so stable that it has not received an update for a long time, such a disclaimer would be proper for the inactive project which has received a bug report, which is the case for ma1sd: #2663
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Some components of the playbook have been officially declared as unmaintained/deprecated, while others apparently seem to have been abandoned for years after the playbook was born and components actively developed at that time were added, such as ma1sd.
Describe the solution you'd like
I think it should be no problem to keep those services in the playbook as long as they work properly for the most cases, but a friendly disclaimer on the documentation that the upstream project seemingly has been inactive for a certain period of time (a year, for example?) should help us to figure out where to look at when an unknown error occurs.
As it is possible that the component is so stable that it has not received an update for a long time, such a disclaimer would be proper for the inactive project which has received a bug report, which is the case for ma1sd: #2663
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: