Package source mapping is a smart concept when you have multiple package sources - which all Optimizely projects have by default.

It's been working pretty good for a while but with the latest releases we've had to tweak our config. 

This because the Optimizely.SDK (experimentation) nuget is distributed on nuget.org, but the new Optimizely packages (e.g. Optimizely.PaymentService.Client), which comes transitively with EPiServer.Commerce, are distributed on nuget.optimizely.com.

So this mapping does not work anymore:

<packageSourceMapping>
    <packageSource key="Optimizely">
        <package pattern="EPiServer.*" />
    </packageSource>
    <packageSource key="nuget.org">
        <package pattern="*" />
    </packageSource>
</packageSourceMapping>

...instead we need to resort to this "hacky" config, which seems to work for the moment....

<packageSourceMapping>
    <packageSource key="Optimizely">
        <package pattern="EPiServer.*" />
        <package pattern="Optimizely.*" />
    </packageSource>
    <packageSource key="nuget.org">
        <package pattern="Optimizely.SDK" />
        <package pattern="*" />
    </packageSource>
</packageSourceMapping>

I guess this stems from the confusion between the product formerly known as Optimizely and the company formerly known as Episerver.

Just wondering if anybody else is using package source mapping with Optimizely?