Modules for MAR

[SydneyhSmith]

Which modules are most important for MAR and why?

[vandre]

What does MAR mean in this context? March? :) @SydneyhSmith

[SydneyhSmith]

https://mcr.microsoft.com/en-us/catalog?search=psresource&type=partial Microsoft Artifact Registry

[gaelcolas]

Not sure this is the right place to track this @SydneyhSmith and @anamnavi, but where do you track the following issue:
As a community module author (publishing in PSGallery), I need to depend on Microsoft-published modules for my owned authored modules.

1. If the Microsoft modules are published to MAR, and I publish to the PowerShell gallery, how can we manage cross feed dependencies?
   (the fact it's different technologies is questioned in point 4.)
   I know you intend to publish to both for now, but I haven't heard a good story for the long term.

2. Now assuming I'm a vendor, and I also publish to my Artifact registry, but I have a dependency in MAR. How does that work?

3. I know I could create a virtual AR that "funnels" my AR + the MAR, is that fine in terms of "redistribution" ? If so could you document that use case so we know it's "legal"?

And add another one:
I'm a vendor, I publish to my own Artifact Registry, but I have a dependency on a community module from the PSGallery (nuget).
4. I now have a a cross technology dependency... how does that work?

For my customers to use my modules, either I need them to do some MAR/AR/PSGallery gymnastics (and they'll say it's too hard), or I need to do that gymnastics myself and "redistribute" third party modules from my AR.
The gymnastics here probably means pulling a package from one technology (nuget) and repackage/republish to another (AR).