Facebook
Twitter
HHawk
Regular Pleskian
Hi Anthony / Anton,
Thank you for taking the time to address my concerns directly as Director of Plesk Product Management. I appreciate your transparency regarding the development challenges related to PMT-4938, and I acknowledge the effort involved in rewriting the Migrator functionality to Python 3 for security reasons. That said, I would like to provide some clarifications and feedback based on your response.
First, while I understand the constraints of limited resources and the prioritization of issues, it remains disappointing that a bug reported almost two years ago, with clear impact on migrations—a core feature of Plesk—was left unresolved due to difficulties in reproduction and perceived low demand. This delay underscores a broader concern about how Plesk allocates resources and manages longstanding issues. Customers paying a premium price expect not only innovation but also the timely resolution of bugs, especially when these are acknowledged in the Knowledge Base.
Second, while I appreciate your willingness to engage in a constructive dialogue, I would like to point out that my tone has been shaped by the frustration of feeling unheard—an experience shared by many Plesk users, as evidenced in various forums. If my words have come across as harsh or overly critical, it is because I, like others, am invested in Plesk as a platform and have high expectations for its reliability and responsiveness. Constructive criticism is not meant to be dismissive but rather to highlight areas where improvement is clearly needed.
I will gladly compile a list of outstanding technical issues affecting my business and submit them in a separate thread for further discussion. However, I would also like to highlight that Plesk’s value proposition as a premium solution is tied to its ability to address these concerns proactively, without requiring customers to repeatedly escalate issues to the highest levels of management.
Lastly, regarding your warning about tone and conduct, I acknowledge the importance of maintaining civility on public platforms and will ensure my feedback remains professional moving forward. However, I also hope Plesk recognizes that frustration stems from unmet expectations, and the best way to mitigate this is by demonstrating a strong commitment to addressing customer pain points in a timely manner.
I look forward to continuing this dialogue and seeing even more meaningful improvements in both the Plesk platform and its engagement with customers!
//edit: forgot to take a screenshot of this thread
Thank you for taking the time to address my concerns directly as Director of Plesk Product Management. I appreciate your transparency regarding the development challenges related to PMT-4938, and I acknowledge the effort involved in rewriting the Migrator functionality to Python 3 for security reasons. That said, I would like to provide some clarifications and feedback based on your response.
First, while I understand the constraints of limited resources and the prioritization of issues, it remains disappointing that a bug reported almost two years ago, with clear impact on migrations—a core feature of Plesk—was left unresolved due to difficulties in reproduction and perceived low demand. This delay underscores a broader concern about how Plesk allocates resources and manages longstanding issues. Customers paying a premium price expect not only innovation but also the timely resolution of bugs, especially when these are acknowledged in the Knowledge Base.
Second, while I appreciate your willingness to engage in a constructive dialogue, I would like to point out that my tone has been shaped by the frustration of feeling unheard—an experience shared by many Plesk users, as evidenced in various forums. If my words have come across as harsh or overly critical, it is because I, like others, am invested in Plesk as a platform and have high expectations for its reliability and responsiveness. Constructive criticism is not meant to be dismissive but rather to highlight areas where improvement is clearly needed.
I will gladly compile a list of outstanding technical issues affecting my business and submit them in a separate thread for further discussion. However, I would also like to highlight that Plesk’s value proposition as a premium solution is tied to its ability to address these concerns proactively, without requiring customers to repeatedly escalate issues to the highest levels of management.
Lastly, regarding your warning about tone and conduct, I acknowledge the importance of maintaining civility on public platforms and will ensure my feedback remains professional moving forward. However, I also hope Plesk recognizes that frustration stems from unmet expectations, and the best way to mitigate this is by demonstrating a strong commitment to addressing customer pain points in a timely manner.
I look forward to continuing this dialogue and seeing even more meaningful improvements in both the Plesk platform and its engagement with customers!
//edit: forgot to take a screenshot of this thread
