Now that we have PowerShell Open Sourced we should really move to decouple all of the modules that are shipped "inbox" into their own repos so that updates to these can be make separately to the core engine and can also be pulled from the PowerShell Gallery

However this brings a number of additional challenges that warrants a detailed discussion and a plan of action as not to break the current build process.

Modules that should be decoupled and pulled in as submodules

• - PowerShellGet Priority
• - PackageManagement (this may already be out there in the OneGet Repo)
• - Microsoft.PowerShell.ODataUtils
• - PSReadline (already decoupled just needs to become a submodule)
• - PowerShell.Archive (as above)
• - Pester (as above but submodule to point to Pester not current submodule)
• - CimCmdlets
• - Microsoft.PowerShell.Diagnostics
• - Microsoft.PowerShell.LocalAccounts
• - Microsoft.PowerShell.Management
• - Microsoft.PowerShell.Security
• - Microsoft.WSMan.Management
• - PowerShell.Utility
• - PSDiagnostics
• - PSScheduledJob
• - PSWorkflow
• - PSWorkflowUtility

This is especially more important as in the differing subfolders in https://github.com/PowerShell/PowerShell/tree/master/src/Modules there are a number of code duplications due to the modules residing in multiple folders which is rather unnecessary and adds unneeded complexity for management of this repository going forward.