# OAI Update – new members, OpenAPI Spec 3.0 progress, and more!

Here comes a quick update on the ongoing activities within the OAI:

## New Members

There is an ongoing interest in joining the OAI and we are thrilled to welcome two new members to the group:

- [Apiary](https://apiary.io/): creators of API design and collaboration tools that recently announced support for Swagger / OpenAPI Spec.
- [Atlassian](https://www.atlassian.com/): the people behind JIRA, Confluence, HipChat, Bamboo, etc.

If your organisation is interested in joining the OAI to support the evolution and proliferation of the OpenAPI Specification then please have a look at [https://openapis.org/join](/content/join/index.html) for details on how to do so.

## Initial TDC Memberships and process finalized

The initial members of the Technical Developer Community driving the OpenAPI Specification have been decided on;

- Darrel Miller – [@darrel_miller](https://twitter.com/darrel_miller)
- Jason Harmon – [@jharmn](https://twitter.com/jharmn)
- Jeremy Whitlock – [@whitlockjc](https://twitter.com/whitlockjc)
- Marsh Gardiner – [@earth2marsh](https://twitter.com/earth2marsh)
- Ron Ratovsky – [@webron](https://twitter.com/webron)
- Tony Tam – [@fehguy](https://twitter.com/fehguy)

This list of contributors is maintained at [on GitHub](https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/CONTRIBUTORS.md) in line with the OAI charter.

The process for the evolution of the specification has been published by the TDC at [https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/DEVELOPMENT.md](https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/DEVELOPMENT.md)

## OpenAPI Spec 3.0 work progresses

Work on the next major iteration of the specification has started, and discussions on various features/improvements are in progress on corresponding issues at GitHub. If you’re interested in getting informed or involved here are a couple of links to point you in the right direction:

- The [OpenAPI.next branch on GitHub](https://github.com/OAI/OpenAPI-Specification/tree/OpenAPI.next)
- The [list of proposed issues for the next version](https://github.com/OAI/OpenAPI-Specification/issues?q=is%3Aissue+is%3Aopen+label%3A%22OpenAPI.Next+Proposal%22)

## OAI represented at events

The OAI will be represented by our members at two upcoming [OW2](http://www.ow2.org/) events in Europe:

- [Cloud Computing World Expo](http://www.ow2.org/bin/view/Events/Cloud_Computing_World_Expo_Paris), Paris, 23-24 March – Represented by Restlet
- [Cloud Expo Europe, London](http://www.cloudexpoeurope.com/), 12-13 April – Represented by 3Scale

The OAI is currently evaluating its possibilities to participate in upcoming API-related events around the globe; if you’re organising an event where you would like the OAI to be represented or if you’re interested in organising a local OAI/OpenAPISpec meetup that the OAI can sponsor – please don’t hesitate to [get in touch](/content/contact/index.html).

## Other ongoing activities

- We have assigned an internal workgroup to provide guidelines on usage of the OAI logo and mark – these will be published on our website.
- The OpenAPI Specification now has a twitter account at [https://twitter.com/openapispec](https://twitter.com/openapispec) – follow it to get notified of both OAI and OpenAPI-Spec related news.

That’s it for now – please don’t hesitate to get in touch with the [TDC on GitHub](https://github.com/OAI/OpenAPI-Specification) if you’re interested in participating in the technical discussions around the OpenAPI Specification – or with the OAI members via our [contact form](/content/contact/index.html) if you have general inquiries – we look forward to hearing from you.

/Ole Lensmar

[@olensmar](https://twitter.com/olensmar)