Tim Hoffmann

@jklymak is there a way to detect such cases so that we can issue a waning, possibly with a hint what to do instead.

The detection does not have to be exhausting. We don't want false-positive alerts. But it's ok not to wan in every problematic situation. It's already helpful to detect some common...

IMHO we should move to an argparse-like specification of the rcParams, e.g. ``` rc.add_parameter( 'webagg.open_in_browser', type=bool, default=True, help="When True, open the web browser to the plot that is shown" )...

> This is updated based on the comments, including expanding the test names to tell what is tested. > > It is maybe not a good idea to test two...

The primary objective of the style sheet reference is to answer "How will my plot look like with this style". We need to show the basic appearance without any modifications...

IMHO we need to become better at theme-management - We need stability guarantees for those who need them. - We need a theme update strategy. - We need better ways...

Unfortunately, I'll not be on the call today. > If you have old code, and you understandably didn't realize you needed to pin, its still going to cause reproducibility problems...

Actually, no changes are required for the what's new. The content and structure is version agnostic. When the PR gets merged the content is put int the `next_whats_new` folder on...

I don't think we need extra separation when referencing types in `mpl_toolkits`. So https://matplotlib.org/stable/devel/documenting_mpl.html#referencing-types still applies.

> In #19572 you, @timhoffm , suggested to make `set_3d_properties` private. Is that still your standpoint? Yes. - It should be an implementation detail that our 3D artists are 2D...