Many common actions need to happen in pre or post-scripts across several applications like modifying the registry and copying files to user profiles or system locations, among many others. Furthermore, there are often actions to license software in these scripts specific to each application or vendor. It would be nice to not have to reinvent the wheel on this and crowdsource the effort by allowing PMPC customers to contribute their Powershell code to a community repository that could be used as a starting place. Of course, any proprietary or confidential information would need to be stripped out.
This kind of exists at https://github.com/PatchMyPCTeam/Community-Scripts/tree/main. However, it could be significantly expanded upon.
It looks like one can participate and submit pre/post-scripts to the repository: https://github.com/PatchMyPCTeam/Community-Scripts/blob/main/CONTRIBUTING.MD But the use of a specific template might not be appropriate for all use case.
That being said, I agree that the organization of files and folder could be revised (for example: could have something like "Scripts\<Vendor>\<ProductName>\<Activity>" for anything specific to an application). If scripts were added to that path in the repo, then a link like "Explore community scripts" could be added to the right-click options of that app in the Publisher.
Definitely agree that community involvement could be leveraged more. :)
+999