Merge "Rename DefCore Committee -> Interop Working Group"

reference/foundation-board-repos.yaml

@@ -1,7 +1,7 @@
 ---
 # List of repositories owned by Foundation board and subcommittes
-DefCore subcommittee:
-  - repo: openstack/defcore
+Interop Working Group:
+  - repo: openstack/interop
 
 Transparency subcommittee:
   - repo: openstack/transparency-policy

reference/projects.yaml

@@ -4228,7 +4228,7 @@ RefStack:
   service: Interoperability Test Report
   mission: >
     RefStack is a test result collection and reporting service to support the
-    DefCore interoperability testing process.
+    Interop Working Group interoperability testing process.
   url: https://wiki.openstack.org/wiki/RefStack
   deliverables:
     refstack:

reference/tags/assert_follows-standard-deprecation.rst

@@ -62,10 +62,10 @@ features deprecation:
    the cost is then very related to the number of people using the feature
    and how dependent they are to that feature.
 
-#. If the deliverable is part of a defcore set, the project will check if the
-   deprecated feature is part of the exposed capabilities. If it is, the
-   obsolescence date (see below) additionally needs to take into account
-   defcore capabilities deprecation schedule.
+#. If the deliverable is part of an Interop Working Group Guideline, the
+   project will check if the deprecated feature is part of the exposed
+   capabilities. If it is, the obsolescence date (see below) additionally
+   needs to take into account Interop WG capabilities deprecation schedule.
 
 #. Based on that data, an obsolescence date will be set. At the very minimum
    the feature (or API, or configuration option) should be marked deprecated