I discussed this with the rest of the team here while awaiting your reply.
- This was in Forum Preview for almost 6 months before becoming production. There was low-moderate feedback but generally all positive. Nothing about the name came up.
-
I have authored several threads related to this packaging
-
I opened this thread on June 29 to address other issues which came up since launch to overcome the technical issues.
-
I provided three months of Preview status and opportunity to suggest before committing to final production status.
-
If you have a docker container, what it does or doesn’t do is your responsibility. Imho, it is unreasonable for hold Plex accountable for any unwanted interaction by some unknown third-party app .
-
By default, No permissions were assigned to the PlexData share. Assigning any would have been overstepping boundaries about the security needs of our customers.
-
Since launch, technical differerences / discrepancies with different QNAP models have forced a change. As disussed in this thread and a few others,
a. The PlexData share use will be completely optional. I, as package engineer, will no longer create one.
b. If I do find one, I will place the symbolic link.
Regrettably, I cannot honor the request for name change.
- More than 3 months of Forum Preview to voice concerns
- Initial release in PMS 1.19.5 . We are now PMS 1.20.1.
- It it the responsibility of the user to know the interactions of software on his/her system. Plex can’t be held accountable for arbitrary third-party applications.
Again, I’m sorry. This is the sole dissenting voice out of all those raised from the thousands of downloads so far… It is felt that ample time was granted . Had this issue been raised earlier, I would gladly have changed it. At this point, however, changing the name impacts everyone who has it setup and integrated into their home Plex systems / support mechanisms.
