matplotlib
diff --git a/‎doc/devel/api_changes.rst
Lines changed: 21 additions & 5 deletions b/‎doc/devel/api_changes.rst
Lines changed: 21 additions & 5 deletions
diff --git a/‎doc/devel/color_changes.rst
Lines changed: 0 additions & 136 deletions b/‎doc/devel/color_changes.rst
Lines changed: 0 additions & 136 deletions
@@ -12,11 +12,6 @@ visualization the user sees; therefore, the appearance of the figure is part of
 the API and any changes, either semantic or :ref:`aesthetic <color_changes>`,
 are backwards-incompatible API changes.
 
-.. toctree::
-   :hidden:
-
-   color_changes.rst
-
 
 Add new API and features
 ------------------------
@@ -37,6 +32,27 @@ take particular care when adding new API:
   __ https://emptysqua.re/blog/api-evolution-the-right-way/#adding-parameters
 
 
+.. _color-changes:
+
+Add or change colormaps and styles
+----------------------------------
+Visual changes are considered an API break. Generally, we do not modify existing
+colormaps or styles.
+
+We put a high bar on new colormaps and styles to prevent excessively growing them.
+Decision is case by case, but in general:
+
+- new styles and colormaps should bring something new to the table, not just being
+  a slight variation of what's already available in Matplotlib.
+- colorblindness and - in case of colormaps - perceptual uniformity should have
+  been considered.
+- colormaps should have a track record, i.e. have been officially published
+  somewhere and have proven usage scenarios.
+- copyright must be considered. Some commercial visualization tools claim
+  rights on their styles. We we cannot include them if the legal situation is
+  unclear.
+
+
 .. _deprecation-guidelines:
 
 Deprecate API