I have a DSC v3 LCM and pull server demo if there is time.

Not sure if there's a better place to raise this, but it would be great to hear from the PSResourceGet/PSGallery team this month about how the PowerShell package management ecosystem will look like after the default-enablement of MAR in v1.3.0 (PowerShell/PSResourceGet#1955).

Right now, the ecosystem has one masthead package management service (Gallery), exposing one API dialect (NuGet v2), with one package format (nupkg). Over the years, enterprise package managers have built upon preexisting NuGet mirroring patterns to provide private package manager mirrors in isolated network environments. Some, like JFrog, have customer-facing documentation on setting this up for PowerShell.

MAR doubles all of those (two services, plus OCI API shape and image format) - 1P PowerShell modules on MAR will mean mirror operators have to stand up an OCI mirror for MAR (in addition to NuGet mirrors for Gallery) to continue receiving 1P modules in isolated environments.

@jborean93 has already highlighted that PSRG's OCI implementation depends on Azure (PowerShell/PSResourceGet#1946), which doesn't hold for other enterprise OCI mirrors (or even public OCI registries, like GHCR).

Some more specific questions that might help guide the discussion:

• Following the default-enablement of MAR in PSRG v1.3.0, is there a timeline for migrating MSFT 1P packages to MAR?
• Will packages migrated to MAR continue to be dual-published to PSGallery for some period of time?
• For customers who need to "mirror the mirror" (set up an OCI mirror for MAR alongside NuGet mirrors for Gallery), is there guidance for doing so with MAR/PSResourceGet so PowerShell users can still consume packages through the mirror?

If there is time, i would love to hear the plans to bring back the availability of the daily build.

Is the call at the normal time 9:30 AM PDT or is this the 7 PM PDT call.

Any updates on the status of ARM packages?