diff --git a/2023-Planning.md b/2023-Planning.md new file mode 100644 index 0000000..be62216 --- /dev/null +++ b/2023-Planning.md @@ -0,0 +1,35 @@ +# Planning for 2023 + +### OpenAPI Outreach Committee - Fri, Jan 13, 2023 + +Attending: Marsh G. , Agued Gama, Jesse, Amber Bennett, Chris Wood, Kevin Swiber, Neal Caidin, Stu Waldron + +## Strategy and Goals + +* Marsh: We are still working on what makes the community resonate +* What is a healthy community? Engagement? Numbers of new members? We need more involvement and people participating. AsyncAPI and GraphQL have done a good job, they are co-evolving with tooling. We took the spec out of Swagger, so we are a standard, which is different from software. +* 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 + +## 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. +* Marsh: We should be shining a spotlight - help draw attention to tracks in conferences. We have had good success doing that in the past. +* Is there a list of API events?? - None for 2023 - Current list is out of date, produced prior to Covid. +* API communities outreach + * Lorinda and team are looking to do some of those activities + * Marsh: We should connect with AsyncAPI (async nature connects well with OpenAPI), and GRPC should be transcoded to OpenAPI +* Chris: Pick a vertical! OpenBanking has real interest and is wedding to APIs + * Marsh: Challenges with gathering data, what do we want to learn? Need a repeatable process. +* Kevin: Invite tooling devs. They should have a say in building the spec. +* Amber: BetterCloud challenge is maintaining other community APIs, staying up to date +* Kevin: Very interested in hearing what Linux Foundation is doing with open standards +* Marsh: Yes, to case studies since incentives drive case studies + +Annual report +* How APIs are being used? Is a huge project, previously considered hiring a firm to do this, problem is how to you get the data, we don’t know tooling, can’t tell - We could do survey but it needs to be more than just a 100 responses +What is the adoption rate of each spec? +* Chris: massive undertaking in terms of gathering data from the community. Not specific of what they are trying to find on who uses the OpenAPI spec and how - have a basis for a database +* More notes [here](https://docs.google.com/document/d/19gLkynTLTJnd4bnHr-dCqLh544M2lAlL1VIIQJTEsw0/edit) + +![](img/outreach-planning-2023.png) diff --git a/README.md b/README.md index 29e5636..48ff9a6 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ ## πŸ“’ Welcome -The OpenAPI Marketing Group is an effort to further the reach and impact of the +The OpenAPI Outreach Committee is an effort to further the reach and impact of the [OpenAPI Specification](https://spec.openapis.org/oas/latest.html). - Led by passionate volunteers. πŸ™‹ @@ -14,9 +14,9 @@ This repository contains welcoming both transparency and contribution. Feel free to [start your own discussion](https://github.com/OAI/Marketing/discussions)! -## πŸ™Œ Join the OpenAPI Marketing Group +## πŸ™Œ Join the OpenAPI Outreach Committee -Feel free to indicate interest in joining the OpenAPI Marketing Group community +Feel free to indicate interest in joining the OpenAPI Outreach Committee community activities by [creating a new issue](https://github.com/OAI/Marketing/issues/new) in this repository with the `invitation-request` label. This will get you: diff --git a/img/outreach-planning-2023.png b/img/outreach-planning-2023.png new file mode 100644 index 0000000..84f8bce Binary files /dev/null and b/img/outreach-planning-2023.png differ diff --git a/img/temp.html b/img/temp.html new file mode 100644 index 0000000..8bd6648 --- /dev/null +++ b/img/temp.html @@ -0,0 +1 @@ +asdf