Update 2023-Planning.md

OAI · Jan 20, 2023 · 2fb1903 · 2fb1903
1 parent 820cbbe
commit 2fb1903
Showing 1 changed file with 14 additions and 0 deletions.
diff --git a/2023-Planning.md b/2023-Planning.md
@@ -11,6 +11,20 @@ Attending: Marsh G. , Agued Gama, Jesse, Amber Bennett, Chris Wood, Kevin Swiber
 * Kevin: difference between open source community and open standards. Open source software tends to have more iterations. A lot is done via email. Should we bring in more tools?
 * Stu: We are still struggling with finding relevance 
 
+## Additional thoughts from the January 20, 2023 meeting
+* Neal: thoughts on OAI challenges - perhaps can lead to goals?
+* Swagger vs OAS - is the terminology still obfuscating?
+   * Stu: Not sure if this is a goal, more of a challenge. As an organization, we’re not moving beyond OAS and talking about other APIS. SIGs do have latitude. What is doable within the constraints of the OAS?
+* Neal: First step is putting ideas on paper, being able to share and get feedback from the community
+* People carving out time of their busy day. Organizations not allocating time for them to work on OAI/OAS
+   * Stu: Goes with the value prop, they are making them a greater investment by contributing labor, should have a positive ROI for them
+* We haven't been as open as we need to, so conversations happening elsewhere
+   * Things have improved over the last year. We've opened up our Slack workspace and started a Discord channel. But these might need tending.
+* Tooling - dependency on ecosystem tooling inhibits adoption of latest spec version
+   * Stu: This is a value prop problem again. Value not understood by vendors that are making the tools
+* Value proposition of being an OAI member. Are we not articulating the value proposition well enough, or do we need to improve the value prop for membership?
+   * Stu: We should be looking at clarifying the value prop for upgrading to 3.1. Is there something we can do to make the path to adoption easier?
+
 ## Tactics and activities
 
 * Kevin: Idea for partnering with events - mutually beneficial - We could focus on things like an OpenAPI track versus sponsorship, which would be more useful and cost less money.