Category

Blog

OCI Announces 2018 TOB Election Results

By | Blog

By Chris Aniszczyk (@cra)

It’s 2018 and after shipping the v1.0 specifications last year, we’re nearing contributions from 300+ contributors across 70+ organizations. Today the community is hard at work on future versions of OCI, including discussions around a distribution API specification. For more details about releases and specifications in development, please visit  https://github.com/opencontainers.

Also, the OCI Technical Oversight Board (TOB) – comprised of independently elected individuals who provide oversight of the technical leadership and serve as a point of appeal – just elected the following five board members to each serve a two-year term, effective immediately:

  • Taylor Brown (Microsoft)
  • Stephen Day (Docker)
  • Phil Estes (IBM)
  • Jon Johnson (Google)
  • Mrunal Patel (Red Hat)

These newest TOB members join the following existing members, who are each in the middle of a two-year term:

  • Vincent Batts (Red Hat)
  • Michael Crosby (Docker)
  • Vishnu Kannan (Google)
  • Greg Kroah-Hartman (Linux Foundation)

The TOB also voted to elect Michael Crosby (Docker) as the new Chair. This new TOB lineup is responsible for adding, removing or reorganizing OCI Projects – to learn more, you can follow the TOB on GitHub here.

I’d also like to extend a big thank you to all of our outgoing TOB members – Chris Wright, Diogo Mónica, Jason Bouzane, John Gossman and former Chair, Brandon Philips – for their service and commitment. We look forward to your continued collaboration with and participation in OCI!

Next month, new TOB member Phil Estes of IBM will represent OCI on a panel at Container World on 2/28. Visit http://bit.ly/2Bsr5Gl to learn more about his involvement in this session!

As always, we welcome any/all contributions from the container community – as our success banks on the support and collaboration of many. If you’re interested in contributing to OCI, please join the OCI developer community. For those who are building products on OCI technology, we recommend joining as a member and participating in the future certification program.

Between our exciting new TOB, upcoming releases and a number of exciting community programs we have in the works, we’re on track to make 2018 our biggest year yet 👍🏼

OCI Member Spotlight: Kontena

By | Blog

The OCI community is comprised of a diverse set of member organizations that are committed to creating open industry standards around a container image format and runtime. This blog series highlights OCI members and their contributions to building an open, portable and vendor neutral specification.

Name: Miska Kaipiainen
Title: Founder & CEO
Company: Kontena, Inc.

Why did you join OCI?
We see OCI as the most important organization in the container ecosystem driving vendor neutrality, standardization and making this amazing technology accessible globally. Just like many other companies working with containers, we are strong believers in open source, open APIs and open ecosystems in general. We joined OCI to contribute to its mission which helps us and everyone else in this industry to be successful.

How is your organization involved in OCI?
We plan to take an active role in collaboratively on improving OCI specifications, tooling and look forward to being more engaged with other members.

What are the aspects of the runtime spec and/or image format spec that you are looking forward to most for your company?
We enjoy vendor neutrality and collaboration for developing container runtimes that are based on open standards.

How do you plan to use the runtime spec and/or image format spec?
We want to incorporate and support the runtime spec in our Kontena Platform open source project, via runC. Soon, we also plan to support the image spec in our own hosted image registry service.

How will these specifications help your business?
These specifications will provide our users with the confidence to get started with containers while having the promise of no vendor lock-in. In addition, these specifications have stabilized some of the core technology components we use.

How do you anticipate OCI changing the container technology landscape?
OCI has already shown its ability to create solid standards and specifications for an industry that’s moving at the speed of light. This community’s work has already produced amazing results through increased interoperability, recognition and adoption. However, there are still so many things we can accomplish with collaboration to help ensure open standards, interoperability and vendor neutrality.

What do you believe the benefits of using a runtime and image spec based on the OCI standard are for hosting providers? For small ISVs, application developers? For end users?
The benefit of using a runtime and image spec based on OCI is the ability to develop and package once, distribute, deploy and run anywhere. We predict that more vendors will be bringing out runtimes that do their own magic to benefit their specific end users. We’ve always been believers in this market not being a “one solution for all” type of situation, as there are a multitude of users, use cases and needs that no one solution can single handedly meet. Open APIs and standards will enable more vendors to build meaningful solutions that will then benefit the end user with more choice and less lock-in through easier interchangeability of components.

What advice would you give to someone considering joining OCI?
Get on-board and help shape the industry from the inside rather than staying out!

OCI Update: v1.0.1 Release and New Maintainer

By | Blog

The OCI community continues to be hard at work, having just issued the first update to OCI v.1.0, after five months of focusing on stability. OCI 1.0.1 contains updates to both the image format and runtime specifications.

We’re still growing and expanding, with even more collaboration since the launch of v 1.0. For example, we are now up to over 5,000 commits from 184 authors across 42 different organizations. Organizations like AWS, Docker, Cloud Foundry, CoreOS, Intel, Mesosphere, Oracle, Red Hat and Kubernetes have already taken advantage of the OCI v1.0 specifications, and with v1.0.1 now available, the industry is on the precipice of true portability and standardization. We had a strong showing on site at recent industry events, at both DockerCon Europe in Copenhagen and Open Source Summit Europe in Prague.

We are also happy to welcome Ma Shimiao as a new maintainer on the image-tools project. Ma joins Aleksa Sarai and Keyang Xie of the image format spec as the newest OCI maintainers, all of whom has been hard at work.  

Concurrently, we are gearing up for the next phase in ensuring broad adoption of common container image format and runtime specs as we prepare to launch an OCI certification/conformance program. This program will allow folks to be confident that their OCI solutions meet a high set of criteria that deliver interoperable solutions. We’ll be presenting a session on Container Runtime & Image Format Standards: What it Means to be ‘OCI-certified during CloudNatvieCon + KubeCon in Austin, Texas on Wednesday, December 6 at 11:10 am. If you’ll be on site, please stop by our booth and check the schedule for additional OCI-related sessions

OCI is always welcoming contributions from across the industry, so please join us! Follow us via @OCI_ORG, and if you’re interested in contributing to the technology, please join the OCI developer community which is open to everyone. If you’re building products on OCI technology, we recommend joining as a member and participating in the upcoming certification program.

 

OCI Member Spotlight: InfoSiftr

By | Blog

The OCI community is comprised of a diverse set of member companies that are committed to creating open industry standards around a container image format and runtime. This blog series highlights OCI members and their contributions to building an open, portable and vendor neutral specification.  

Name: Tianon Gravi
Title: SVP of Operations
Company: InfoSiftr

Why did you join OCI and how is your organization involved?
The Open Container Initiative (OCI) is a critical open source organization helping ensure compatibility and interoperability for the basic components of containers. We believe in the mission of the OCI and, as contributors and maintainers in the container ecosystem, will continue to lend expertise and effort to further the group’s goals. On an individual level, I have been involved since the foundation of OCI and am a member of the OCI’s Technical Developer Community (TDC), having worked on the container runtime specifications since the foundation of the OCI.

What are the aspects of the the runtime spec and/or image format spec that you are looking forward to most for your company?
By encouraging standardization and interoperability, the specs help enable differentiation further up the stack, where it benefits all users.  Additionally, companies can feel safer in adopting containers knowing that at a foundational level, they aren’t locked into any one vendor’s solution (which is all thanks to these low-level standards).

How do you plan to use the runtime spec and/or image format spec?
Any development work we do in the container space will adhere to OCI specifications, and encourage their use and furtherance within the ecosystem.

How will these specifications help your business?
The specifications will help all businesses with an interest in containers, whether they are contributing to the container ecosystem or just consuming container-based technology.  This flexibility helps us in our own day-to-day operations, but also helps our clients as they evaluate and commit to container-based solutions and deployments.

How do you anticipate OCI changing the container technology landscape?  
The OCI’s standards create a “baseline for competition.”  Now that we have an agreed upon foundation, companies can proceed to innovate and compete in more interesting ways.

What do you believe the benefits of using a runtime and image spec based on the OCI standard are for hosting providers?  For small ISVs, application developers? For end users?
If you’re doing anything in technology, it’s useful to adhere to standards. Much of the container ecosystem is still new and evolving, and we’re bound to see changes to technology stacks going forward. Adhering to the specifications set forth by the OCI means we all agree the underlying details of our tooling and products will be compatible and interoperable, whatever higher-level changes may come.

What advice would you give to someone considering joining OCI?
Contributing to the underlying specifications of the container ecosystem is sometimes difficult and involved work, but it can be very rewarding. Joining the OCI is a great way to start doing exactly that: https://www.opencontainers.org/join

 

 

OCI Welcomes New Project Maintainers

By | Blog

Following the recent release of OCI v1.0 (runtime-spec / image-spec) and a summer break, the work continues and the community is busy.

We had a great panel and strong showing on site at Open Source Summit North America last week in Los Angeles, entitled, “Open Container Initiative: What’s Next For Standards and Container Portability?”.

Furthermore, we’re partnering with Docker to support diversity and inclusivity at DockerCon Europe as one of the official DockerCon Europe Diversity Scholarship sponsors. We continue to work towards our certification program, due out in the near future.

Additionally, the community has just elected two new maintainers for the OCI image specification:

Both Aleksa and Keyang have been fantastic contributors to the OCI community. According to fellow maintainers, Aleksa has been invaluable with feedback, brainstorming and fixes/features all the way through the stack while Keyang has heavily contributed to improved overall quality and testing of the image specification.

As always, contributions from across the industry are welcome; our success depends on the support and collaboration of many. If you’re interested in contributing, please join the OCI developer community which is open to anyone. If you’re building products based on OCI technology, we recommend joining as a member and participating in the upcoming certification program.

OCI Member Spotlight: EasyStack

By | Blog

The OCI community is comprised of a diverse set of member companies that are committed to creating open industry standards around a container image format and runtime. This blog series highlights OCI members and their contributions to building an open, portable and vendor neutral specification.  

Name: Guohui Liu
Title: Co-founder and CTO
Company: EasyStack

Why did you join OCI?
Trends in cloud native computing are still on the rise. Businesses are evolving faster than ever before as applications require more agile and scalable infrastructure, and container technology is right at the center of it all. Unified standards are imperative for container technology to evolve and develop, with input and participation from the entire ecosystem. We believe the Open Container Initiative (OCI), with its runtime and image format specifications, plays a leading role in actualizing the ability to “package once, run anywhere” for applications.

Openness is a part of EasyStack’s DNA. We believe container technology will fill the gap between traditional IT and cloud native IT. We are among the first to release a converged infrastructure cloud platform featuring both containers and OpenStack cloud, and are looking forward to sharing our rich experiences with enterprise cloud native infrastructure offerings with the global OCI community.

How is your organization involved in OCI?
EasyStack is an active participant in the broader open source community, and we believe it is equally important to contribute to upstream open source projects to help address enterprise customer needs. Today — based on OpenStack, Kubernetes, Docker, Ceph and other open source technologies– EasyStack provides an open, secure, stable, reliable, and high-performance cloud computing capability for 200+ enterprise customers for their cloud infrastructure. As part of OCI, we are sharing our enterprise cloud and application model experience with the upstream community.  

What are the aspects of the runtime spec and/or image format spec that you are looking forward to most for your company?
The runtime spec and image format spec provide container standards, which is very important to both vendors and users. Trends in cloud native are encouraging more and more enterprise users to deploy containers, and many of them are already in production. This means reliability and consistent upgrades are extremely important. Additionally, API compatibility and scalability is imperative, especially in customized enterprise scenarios.

How do you plan to use the runtime spec and/or image format spec?
We leverage OCI v1.0 the runtime spec in our ESContainer Linux already, providing a reliable and stable container runtime. This allows us to focus on the development of true application-oriented orchestration, leveraging additional technologies such as Kubernetes.

How will these specifications help your business?
These specifications provide standardized and reliable image format and runtime specifications, allowing us to better and more efficiently develop ESContainer, shortening the development cycle. With these standards, the infrastructure provided by different vendors is of the same API so this avoids vendor lock-in, which helps our business to reduce risk (as well as costs, which in turn yields higher profits).  

What do you believe the benefits of using a runtime and image spec based on the OCI standard are for hosting providers?  For small ISVs, application developers? For end users?
OCI’s runtime and image format specs help all types of customers. The use of one standardized spec enables container applications to be deployed, run, and updated in a multi-cloud environment (e.g. public cloud, private cloud or community cloud) more quickly and efficiently. This is extremely helpful in today’s hybrid cloud environment and both the hosting providers and the end users will benefit from it.

ISVs and application developers now have standards to follow, which can help reduce the risk of going in the wrong direction while avoiding vendor lock-in as they build container applications.

What advice would you give to someone considering joining OCI?
If you and/or your organization’s vision align with current cloud native trends, just join OCI. Today, it is almost impossible for one company to really dominate one hot technology and at the same time keep it active and advanced. Open technologies have proven successful for rapid development, and OCI is a great example of this. New members to the OCI community can get started quickly with shared resources and support from across the community, in addition to having fun by contributing back.

Fostering Diversity and Inclusivity at DockerCon Europe

By | Blog

It’s incredibly important to the Open Container Initiative (OCI) community, as well as the larger container ecosystem, to build a community of inclusiveness that helps provide opportunities to underrepresented and disadvantaged groups around the world. We strongly believe the power of collaboration is heightened when many different perspectives are included, with massive benefits to the broader tech ecosystem.

To that end, we are pleased to help underrepresented members of the container community the opportunity to attend DockerCon Europe (October 16-19) in Copenhagen this year as one of the official DockerCon Europe Diversity Scholarship sponsors! Together with Docker, we’re helping to foster inclusivity by providing a financial scholarship – including conference pass, airfare, hotel accommodations, and a mentorship – to those who may not have the resources or support to attend on their own. Winners of the scholarship will also receive hands-on access to the resources, tools, and community support needed to further accelerate educational and career growth.  

Applications are due Tuesday, 5 September, 2017 at 5:00PM PST. More details on the program and how to apply are available here: https://blog.docker.com/2017/08/dockercon-europe-diversity-scholarship/

DockerCon is one of the container industry’s premiere events where practitioners come to learn from enthusiasts and experts. It’s all about learning, sharing, connecting, and innovating on the next generation distributed systems.

We plan on sharing a booth with our sister Linux Foundation collaborative project, the Cloud Native Computing Foundation (CNCF). Please stop by the booth to learn more about OCI, CNCF, the wider Linux Foundation container ecosystem, and how OCI integrates with the CNCF community and projects (Kubernetes, Prometheus, OpenTracing, Fluentd, Linkerd, gRPC, CoreDNS, containerd, rkt and CNI).

As always, we  encourage you to look for ways to get involved in OCI, either as an official member or as part of our open developer community.

OCI v1.0: Bringing Containers Closer to Standardization

By | Blog

By Chris Aniszczyk (@cra)

Over the past few years, there has been rapid growth in both interest and usage of containers. Almost all major technology vendors and cloud providers have announced container-based solutions, and there has been a proliferation of start-ups founded in this area as well. The promise of containers as a source of application portability requires the establishment of certain level of standards to ensure neutrality.

We launched the Open Container Initiative (OCI) with the goal of developing common, minimal, open standards and specifications around container technology without the fear of lock-in. I am proud to say that, after much hard work and passionate contributions from the community, we have reached our first critical milestone: the release of OCI v1.0!

The release brings a set of common, minimal, open standards and specs around container technology to a reality, containing both the image format specification (a specification for the container image format) and the runtime specification (a specification for managing the lifecycle of a container). The openness of the specifications yields a set of truly shared standards across the industry, that reduce interoperability issues and fuel innovation.

I am incredibly proud of the entire OCI community for the all the hard work that went into this release! Coupled with early pre-release deployments from organizations like, AWS, Docker, Cloud Foundry, CoreOS, Mesosphere, Oracle, Red Hat and Kubernetes, OCI v1.0 brings the industry closer to true portability and standardization. This work could not have been done without the real heroes, our project maintainers, who have toiled long and hard to bring these specifications to life:

Vincent Batts (Red Hat): “Pulling together contributors across a variety of companies and technologies can be tough, but it’s what we needed to do for the rapidly evolving and growing container ecosystem. The two years we’ve spent developing and refining the v1 release of the OCI specifications is just the first step towards much more collaboration around container life-cycles and distribution. It’s going to be exciting to see how the v1 specifications are used in the next iterations of tooling and technology from the ecosystem, and how they are used to enable collaboration. It’s been a real honor to work with so many smart and respected folks.”

Brendan Burns (Microsoft): “I’m incredibly excited to see OCI reach this important milestone. Open standards ensure the success of the revolution that containers are bringing to distributed cloud computing. Such standards also provide a critical building block on which higher level systems like Kubernetes can be built. I congratulate the OCI organization and the broader container community for reaching this important milestone.”

Michael Crosby (Docker): “I’m happy to see all the hard work that the community and maintainers put in over the past few years finally released.  From the early days of libcontainer to the OCI 1.0 release, many of the original maintainers, as well as a few new contributors to OCI, have stuck with the project over the years to get us where we are today.”

Stephen Day (Docker): “It’s great to see Docker’s image format become enshrined in the OCI image specification. The flexible components work well in meeting a wide variety of use cases for distributing container images in a secure manner. With the release of the 1.0 specification, it will be exciting to watch the industry grow around these strong primitives.”

Qiang Huang (Huawei): “I am very proud to participate in OCI to develop this long and exciting project. Thanks to those who contribute in the OCI individuals and companies, the release of OCI V1.0 is great payback of all the efforts. As the cornerstone of the entire container industry, the publication of the OCI standard is to bring positive and favorable changes to the community and ecosystem. I will continue participating in OCI to complement container standards, and look forward to seeing more innovations based on OCI.”

Mrunal Patel (Red Hat): “It’s been exciting to work with a talented group of contributors from across the industry on getting the OCI Runtime Specification to 1.0. Containers are becoming a mainstream technology, and standardization can help ensure that applications in a container will be portable across container runtimes. The runC implementation is already at the heart of most container orchestration systems, and we’re now seeing alternative implementations sprout up for specialized workloads enabled by the runtime specification. This is going to be key for container adoption going forward.”

Brandon Philips (CoreOS): “CoreOS started the conversation years ago on the container image and runtime specification, and today we are thrilled to have worked alongside the major leaders across the industry to create a stable OCI 1.0,” said Brandon Philips, chair of the OCI Technical Oversight Board and CTO of CoreOS. “With the OCI Runtime Spec, and more importantly, the OCI Image Format Spec, at 1.0 and now mature for broad use, users can expect the OCI to help stabilize a growing market of interoperable, pluggable tools, and should gain confidence that containers are here to stay. And we are actively working with the Kubernetes community to bring this v1.0 OCI release to a future release.”

Aleksa Sarai (SUSE): “It has been incredible working with the excellent engineering talent within the OCI development community, and I am excited to continue working with them to innovate on the base we have released thus far. I also cannot wait to see what the wider community builds on top of the OCI specifications, as well as what alternative implementations will be developed by others. Thanks to the interoperability of the OCI specifications, users are free to piece together different components to suit their needs without worry about vendor lock-in. The OCI was the missing piece in driving container adoption and innovation forward.”

Ma Shimiao (Fujitsu): “I’m so glad to see the v1.0 release of the OCI specifications after have been working together with the excellent contributors within the OCI community. I believe it’s an important step for container standardization. With rapid growth, it’s inevitable that container technology becomes fragmented. This causes such as portability, vendor lock-in problems. It will be exciting to watch OCI specifications to solve these problems and promote the development of container technology.”

Though we’ve just hit a huge milestone, there is still work to be done. Looking ahead, we’ll be launching a formal certification program later this year as active and ongoing work is underway to bring additional functionality and broader platform support.

If you would like to participate in the OCI, we are always welcoming contributions from across the industry, you can follow us via @OCI_ORG!  If you’re interested in contributing to the technology, please join the OCI developer community which is open to everyone. If you’re building products on OCI technology, we recommend joining as a member and participating in the upcoming certification program.

OCI Member Spotlight: CoreOS

By | Blog

The OCI community is comprised of a diverse set of member companies that are committed to creating open industry standards around a container image format and runtime. This blog series highlights OCI members and their contributions to building an open, portable and vendor neutral specification.

Name: Brandon Philips
Title: CTO
Company: CoreOS

The Open Container Initiative serves an important function in the container ecosystem. To us at CoreOS, we are committed to making sure the container ecosystem focuses on standards and security. As a founding member of the OCI, CoreOS is an ardent advocate of the OCI’s mission to establish open industry standards around container formats and runtimes. We are working alongside leaders of the industry to standardize how container images are built, verified, signed, and named. The OCI coalesced around these goals, formed by a strong technical community of industry maintainers dedicated to that mission and provides a platform from which to coordinate our efforts. Together, we have been working to deliver on the promise of “package once, run anywhere” containers. Users can expect increased innovation and interoperability between container registries, build tools, and runtimes.

As maintainers of the OCI image spec, industry leaders and I actively guide and contribute to its development. The OCI will play an important role in standardizing not only the runtime specification, but even more, the container image format specification, paving the way for portable containers that can be deployed on a variety of environments. Benefits include lowering confusion in the container space and reducing the avenues available to vendors to lock clients into an isolated ecosystem. We are committed as an organization to continue expanding, contributing to, and supporting standards; doing so is paramount to developing an open platform. These are key elements in our efforts to provide self-driving infrastructure to all via our CoreOS Tectonic product. As a company founded with open source values, CoreOS’s goals are closely aligned with organizations like the OCI that provide a framework for building an open, portable and vendor neutral specification.

Where we are today: Release candidates and ways to support the standard

Release candidates of the runtime and image format spec have continued to mature, and the container ecosystem has continued to grow. It now is possible to build container runtimes that support the standard. There is a bit of a chicken and egg with working in standards like the OCI; you need both sides of the standard (consumers and producers) for the interoperability to happen. With the support of AWS for example, we can create the ecosystem around it more quickly. This is a big milestone since most products will want to be interoperable with AWS.

The ability to have pluggable components ready to use is crucial for easy adoption. The container infrastructure industry is an emerging market, and new markets have an adjustment period before stabilizing. Before the creation of the OCI, we were seeing a proliferation of competing standards. This ran the risk of increasing confusion and discouraging participation. Our hope is that with the OCI, we can break down walls and prevent further isolation, leading to an influx of new tools and a burgeoning industry.

CoreOS will implement and adhere to the runtime and image format specifications and hopes to help bring compatibility to Kubernetes upstream. Having industry standards means having compatibility across the tools created with those standards. CoreOS is developing the tools needed to build a complete container infrastructure. Ensuring that our products can be used with other tools in the container ecosystem increases our exposure and expands our options with our enterprise solutions as well.

With supporting the standard, end users will know that OCI-compatible tools were built using industry-approved standards, making it easier to know what tools can be used together.

We are excited to see the OCI grow, and having a large and thriving community is the best way to garner interest, foster growth, and develop a strong network of contributors.

***
Brandon Philips, as cofounder and CTO at CoreOS, is building modern server infrastructure open source projects like Container Linux and enterprise products like CoreOS Tectonic and Quay. Prior to CoreOS, he worked at Rackspace hacking on cloud monitoring and was a Linux kernel developer at SUSE.

OCI Member Spotlight: Cycle.io

By | Blog

The OCI community is comprised of a diverse set of member companies that are committed to creating open industry standards around the container image format and runtime. This blog series highlights OCI members and their contributions to building an open, portable and vendor neutral specification.

Name: Jake Warner
Title: CEO / Founder
Company: Cycle.io

Why did you join OCI?
At the end of the day, it would have been much harder for us to get started as a company without the previous OCI members and contributors coming together and developing runC and the runtime-spec. As our company continues to grow, we look forward to joining and contributing to the movement started by the OCI.

How is your organization involved in OCI?
At the moment, we’re an implementer of runC and the runtime specification. Coincidentally, we had begun the development of Cycle only a matter of days before runC was donated to the OCI by Docker. As a CaaS and container orchestration platform, being part of the organization which is key to standardizing containers was a no-brainer for us.

What are the aspects of the the runtime spec and/or image format spec that you are looking forward to most for your company?
Once the image spec is finalized with a v1.0 release, we’ll begin to see even more container projects come to life. Given the nature of Cycle being a CaaS platform, being able to support a wide variety of container build tools is fantastic.

How do you plan to use the runtime spec and/or image format spec?
We truly lucked out with the timing of the initial spec and the start of Cycle’s development. Because of this, we’ve built our systems around the runtime spec from day one.

How will these specifications help your business?
In a world where new technologies are appearing every day, being able to fall back to standards keeps everything moving forward. Having a well designed spec helps ensure Cycle can continue to integrate with things that haven’t yet been built.

How do you anticipate OCI changing the container technology landscape?  
Really, it already has. Now days, even sitting in container chatrooms on Slack or IRC, developers from companies who would otherwise be competing are working together to ensure containers are a solution to everyone’s problem. Having an organization that helps ensure stability across ‘super hot’ technologies like containers can only be a good thing.

What do you believe the benefits of using a runtime and image spec based on the OCI standard are for hosting providers?  For small ISVs, application developers? For end users?
Given that Cycle provides bare-metal container hosting for our users, the runtime spec (and RunC) is invaluable to us. The ability to be complementary to other container build systems and integration tools is key to our success.

What advice would you give to someone considering joining OCI?
Do it. Even if you don’t have a ton of time to be involved in everything that takes place, you’re supporting an incredibly helpful organization and making an impact on what will be the future of application development/deployment. OCI members, code contributors, testers, and even those who really enjoy writing documentation, everyone has something to offer!