Cloud Native Platform Engineering Community – Ways to Contribute

Contribute: Community Participation

Mon, 01 Jan 0001 00:00:00 +0000

Finding Community

Please follow us on LinkedIn Cloud Native Platforms

Please consider joining the CNPE Community Slack workspace to find out more about how you can participate in the community. The CNPE Community is a place for platform engineering practitioners to share knowledge, collaborate on projects, and learn from each other. CNCF Slack #platform-engineering channel

Types of Community Participation

As a community we work on all kinds of practices, from the technical to the organizational or socio-technical. This work manifests in various contributor-friendly forms.

Research studies
Whitepapers and Research papers
Blog posts
Talks and presentations
Software product and project development
Community events and meetups
Facilitation and contribution to other technical projects and organizations.

For more information on how to submit community content, please see the Blog Post Getting started with contributing in WG Platforms

Types of Community Participants

Platform Engineering is a broad field that encompasses many different practitioner roles and responsibilities. The CNPE Community welcomes participation from all types of community members, including:

End Users
Platform Maintainers
Service Providers
Project Maintainers

Contributing

To get started, please open an issue on the CNPE Community repository using the Website Localization issue type.

This issue type will provide context on the scope of your work and provide guidance on the steps required to complete a localizations.

Contribute: Initiatives and Projects

Mon, 01 Jan 0001 00:00:00 +0000

Initiatives and Projects

As Platform Engineering practices evolve rapidly, the CNPE Community is committed to fostering collaboration and knowledge sharing. We have several active initiatives and projects that are ready for contribution and participation. These initiatives focus on various aspects of platform engineering, from product thinking to maturity assessments.

For information on initiatives, or to propose a new initiative, please see the Initiatives and Projects page.

Contributing

To get started, please open an issue on the CNPE Community repository using the Website Localization issue type.

This issue type will provide context on the scope of your work and provide guidance on the steps required to complete a localizations.

Contribute: Localizations

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

Part of what makes the CNCF so amazing is the diversity of people involved and supported by the community. One way we make this community more inclusive is by providing localizations for content where possible. Localizations of course require native speakers to create and maintain them and this post is about how you can do that within the CNPE Community content.

The Platform Engineering artifacts and website are initially developed in English, but we welcome contributions to prepare them for other languages. This is a great way to help make the content accessible to a wider audience and to contribute to the community.

Guidelines

While each localization is unique, we encourage you to familiarlize yourself with past localization PRs and the Kubernetes SIG-Docs localization documentation for general guidelines and lessons learned.

The SIG-Docs team has a much broader remit than this Community requires, so be aware that the workflow including slack channels, opening PRs, and website owner reviews will be done via the same process as all other Community postings, just with the added requirement of a native language speaker review.

It is worth reiterating what the SIG-Docs team has stated:

Localizing all the Kubernetes documentation is an enormous task. It’s okay to start small and expand over time.

Whether you start with a single white paper, or want to expand on an existing language to include more blog posts or content, every little bit will make a difference and is appreciated!

Contributing

To get started, please open an issue on the CNPE Community GitHub repository using the Website Localization issue type.

This issue type will provide context on the scope of your work and provide guidance on the steps required to complete a localizations.

Contribute: Platform Maturity Model examples

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

Platform engineering is still an emerging space. The Maturity Model was written and reviewed by over 50 individuals from different countries, business domains, company sizes and experiences. That being said, it is still a reflection of the group who wrote it.

This contribution type is an opportunity to expand that number even more. To add real life examples to the model giving richer details to the current levels.

Guidelines

This contribution type is not asking for a change in the model structure or wording. Therefore any suggestions that would change the content, wording, or even formatting of the model and the descriptions of the aspects should be submitted through the more generic contribution format.

What this is doing is enabling and encouraging end users (companies who do not profit from the implementation or sale of cloud native tooling solutions) to share their experiences in relation to the maturity model.

The intention of these contributions is to make these examples more grounded in concrete examples, ideally supplemented by context (e.g. company size, business domain, etc) and more reading (e.g. links to company blogs).

Contributing

To get started, review the current model are scroll down to the Model Detail section. In this section there is a page per aspect, and each level provides Example Scenario section (e.g. Investment Provisional level).

We are asking for community members to please open a Pull Request (PR) adding your example to the current model version. PRs should be limited to just examples, as other changes such as vocabulary, content, or even formatting of the wider maturity model can be submitted as a separate issue.

The original examples are meant to help readers feel connected to the model aspects and levels. To see themselves in the model, and ideally to see examples of what they could experience if they were to invest in moving to another level within the model. These examples were curated by the group but are not attributed to any one company or exact scenario.

You proposed examples should be succinct summery of the way this specific aspect and level presented in your context. We recommend that you use a fairly neutral voice even when presenting challenges or successes. This maintains the tone that there is not “good” or “bad” maturity, but instead the “right” or “wrong” maturity for you, at this time. In addition, we encourage people to include their company name specifically if allowed, or some small context on the company for comparison (e.g. “a large multi-national bank” provides insight into size, regulation, and domain).

The current examples are mostly between 200-500 characters which may feel challenging at first. Reviewers can help you refine your words so don’t stress too much but also be aware this will be the goal before merging. One way you can manage this is to link out to a separate blog which provides more details if that helps to narrow the focus of your example for this white paper.

Asking for help

If you have any questions about this contribution type, your specific context, the technicalities of opening a PR, or really anything else, please join the CNCF Slack and reach out to #platform-engineering.