Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task from marketing, create material or other artifacts to accelerate the adoption of 3.1 #33

Open
swaldron58 opened this issue Oct 29, 2021 · 1 comment

Comments

@swaldron58
Copy link
Contributor

In the marketing call on Oct 22nd, a request for the tech teams to create material to better communicate the benefits of 3.1. Marketing has to take the lead on messaging, but needs more consumable content targeted for various audiences.

@swaldron58
Copy link
Contributor Author

Initial ideas:

  • Publishable statement(s) of benefits of 3.1. Not just statements of updates where the reader needs to decipher what that means to them or their organization, but also where we can, outline commercial and/or productivity advantage.
    Arguably particular attention paid to tool vendors.
    Expecting this task to take one person about 8 to 10 hours spread over a week.
  • Publishable examples of targeted use cases such as support of Python or tool updates. The intent here is to demonstrate the efforts are reasonable in scope and cost. This will allow us to generate data for overall cost/benefit statements.
  • Publishable statement(s) of where 3.1 is already in use and the benefits gained. This would need to be updated on a regular basis. This may include notices of projected 3.1 implementations.

@webron webron transferred this issue from OAI/OpenAPI-Specification Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant