PowerShell
*Typically* All modules should have their own repo
Whilst I understand the benefit of shared items like CI/CD definitions and issue templates, I think that having these modules all in 1 repo & using folders to segregate them within 1 repo isn't the right way to go.
I have commented similar previously as per https://github.com/PowerShell/PowerShell/issues/1979
Unless there are any benefits in them sharing a common location can I ask is coupling them like this of any beneficial use
The current plan is to move all modules that ship or potentially ship with PowerShell to this repo. Think of this as the equivalent of the dotnet/runtime repo. This will make it easier for contributors/maintaineres to make changes to different modules (although only a single PR should be for a single module) while keeping things consistent. Having individual repos for each module will mean that some modules get under-serviced and harder to maintain/triage across multiple repos.
Having individual repos for each module will mean that some modules get under-serviced and harder to maintain/triage across multiple repos.
On the contrary, Core team has consolidated repositories to reduce overhead and simplify contributions. Why not in PowerShel/PowerShell repo? There is a ready-made infrastructure. You only need to add packaging and publication these modules.
