All of us, as part of the technical sphere, have sometime or the other heard about the term 'open-source'. Even if we haven't, we have been using since the first time we learned an algorithm or downloaded a software for free from the internet. But for most of you, this term may still be shrouded in mystery. So DSC IIT Goa and InfoSec IIT Goa are here for the rescue.
In this introductory event, we will celebrate the existence of this ever-expanding and most welcoming open-source community. A brief overview of the topics we'll cover is as below:
1. Introduction to open-source and why is it so valuable?
2. Basics of Git, GitHub and how to make a Pull Request.
3. Everything you need to know before making your first contribution.
4. Challenges faced and how to resolve them.
5. How open-source brings a security mindset.
6. Guide to safe usage and contribution to the community.
7. Famous annual open-source events and how to participate in them.
This event will fully equip you make the most dashing entry into this amazing community.
NUS-ISS Learning Day 2015 - Project Management - May the Agility be with YouNUS-ISS
The document outlines an unconference discussion on adopting agile practices. It introduces the unconference format and poses questions about experiences implementing agile. Common challenges are discussed, such as whether scrum eliminates the need for a project manager. The tensions between project management and software engineering aspects of agile are also examined. The discussion suggests both considering organizational readiness and marrying traditional project frameworks with scrum. Finally, it encourages an agile mindset and continuous improvement.
The spirit of Opensource - lets plan to contribute ! @JWC16Parth Lawate
Open Source Is A Powerful Concept And Used Correctly It Evolves A Powerful & Sustainable Ecosystem Around It. Open Source Can Be A Powerful Strategy That Drives Growth And Innovation. Join This Session To See How You Or Your Company Can Adopt This Powerful Tool That Not Only Increases Your Development Velocity But Also Drives You To Innovate And Make A Difference All While Running A Sustainable Business Around It !
Why Open Source Products Are Important by a Google Tech ManagerProduct School
This talk was geared towards a non-technical audience interested in the magic and wonder of open source. Danny Rosen went over what open source is, why it's important, what it means to have an open source product and why it's important to customers.
He also discussed what it's like to be involved in the open source community from the perspective of a user, a product manager and a developer, and the challenges and opportunities related to community management and community involvement.
It is easy contributing to open source - JCON 2020César Hernández
The problem developers new to open source have is joining the community, starting to contribute, and using common open source tools. In this session, attendees will learn how to contribute and become valuable a part of any open source community. Attendees will learn soft and hard skills based on two case studies: Eclipse MicroProfile and Apache TomEE projects. Attendees will learn to access the culture of open source projects, expected behavior and attitude toward new contributors; how to start small, take risks, ask lots of questions; and how to get started with common open source tools like Maven, Git, and JIRA. Students will leave this workshop the soft skills and the hard skills required to make meaningful contributions.
SIM RTP Meeting - So Who's Using Open Source Anyway?Alex Meadows
Open Source has been around for several decades now, but there is still a bit of mystery around what makes open source work and concern about using it in the enterprise. Open Source technologies are being widely used in many industries, including analytics, software development, social media, data center management, and more.
The discussion will be moderated by Julie Batchelor and panelists include:
* Todd Lewis, Open Source evangelist
* Jason Hibbets, Open Source Community Manager
* Jim Salter, Co-Owner and Chief Technology Officer at Openoid, LLC
* Alex Meadows, data scientist
In this episode, we will focus on open sourcing how we run Netflix's open source program. Netflix has been using and contributing to open source for several years. Over the years, Netflix has released over one hundred Netflix Open Source (aka NetflixOSS) libraries, servers, and technologies. Netflix engineers benefit by accepting contributions and gathering feedback with key collaborators around the world. Users of NetflixOSS from many industries benefit from our solutions including Big Data, Build and Delivery Tools, Runtime Services and Libraries, Data Persistence, Insight, Reliability and Performance, Security and User Interface. With such a large and mature open source program, Netflix has worked on approaches and tools that help manage and improve the NetflixOSS source offerings and communities. Netflix has taken a different approach to building support for open source as compared to other Internet scale companies. Come to this session to learn about the unique approaches Netflix has taken to both distribute and automate the responsibilities of building a world-class open source program.
The document discusses the history and philosophy of open source software. It begins by explaining that open source refers to the development methodology, not free software which is a social movement. The origins of open source date back to the 1960s when computer programmers shared source code. However, in the 1980s access to source code became restricted by vendors. This led to the rise of the free software movement and creation of the Free Software Foundation in 1985. In 1998, the Open Source Initiative was formed to promote open source principles to businesses. The document outlines the differences between the goals of OSI and FSF, and describes common open source licenses and development processes like forking.
(PROJEKTURA) lean and agile for corporation @Cotrugli MBARatko Mutavdzic
Great time and hopefully presentation on COTRUGLI MBA @Zagreb about Lean and Agile to packed crowd of MBA students. As you can imagine, number of questions later :)
The document discusses the history and operations of the Apache Software Foundation. It began in 1995 with 8 developers working on the Apache HTTP Server. It is now a large organization with over 2,500 committers across 70+ projects. The ASF operates under an open governance model called "The Apache Way" which emphasizes merit-based consensus decision making. It also discusses how the ASF scales its operations through project oversight, incubating new projects, and community education programs like mentoring.
AUGNYC Hosted the first event of 2018, with three talks.
1. Jira & Trello: When to use Each? - Trevor Longino, Unito.IO
2. A Lightning Talk on Giving a Lightning Talk - NYC AUG Leaders & You
3. Starting Small with Jira, but Planning for Growth - Craig Castle-Mead, Y&R
How Open Source Helps to Bring Back Product ObsessionSauce Labs
This document discusses how open source can help organizations bring back product obsession. It outlines Sauce Labs' approach to open source which includes establishing an Open Source Program Office (OSPO) to manage open source consumption and contributions. The OSPO aims to increase customer engagement, shape industry standards, and build Sauce Labs' reputation through open source. Guidelines are provided for how employees can participate in open source through code and non-code contributions. The benefits of open source for customers, engineering culture, and bringing product obsession are discussed.
This document provides guidance on building a project community. It discusses establishing categories of community involvement like users and contributors. It emphasizes designing for division of labor to facilitate contributions from many developers. It stresses the importance of being welcoming to community members and having a code of conduct. It also notes that a license may be needed if companies will use the code or full-time employees will work on the project.
Building software: the lessons from open sourceArnaud Porterie
This document summarizes Arnaud Porterie's presentation on lessons from open source for building software. Some key points include:
- Open source projects follow patterns of "wise crowds" like having a strong mission, free entry for contributors, transparency, and fair authority to scale effectively.
- These patterns can help improve closed source software development by fostering greater collective intelligence within companies.
- Applying concepts like inner source allows companies to benefit from open source practices internally by opening codebases and encouraging cross-team contributions under shared maintainers.
- A practical checklist is proposed for implementing inner source based on principles like giving all employees access to code, having documented missions and contribution processes, and enforcing consistent processes.
The Open Source Geospatial Foundation does much more than hold FOSS4G each year.
This talk will look into what makes OSGeo a software foundation. What software foundations have to offer members, software projects and developers.
This talk is structured around the “incubation” process by which new software projects join the OSGeo.
If you are new to open source take this is a great chance to see how OSGeo evaluates software projects and how these checks protect you!
For managers it is especially important to understand the risks associated with the use of open source. Understand what assurances OSGeo incubation offers, how to double check the results, and what factors are left for your own risk assessment.
If you are a developer considering getting involved in OSGeo this is great talk to learn what is involved, how much work it will be, and how you can start!
Come see what makes OSGeo more than a user group!
Its easy! contributing to open source - Devnexus 2020César Hernández
The problem developers new to open source have is joining the community, starting to contribute, and using common open source tools. In this session, attendees will learn how to contribute and become valuable a part of any open source community. Attendees will learn soft and hard skills based on two case studies: Eclipse MicroProfile and Apache TomEE projects. Attendees will learn to access the culture of open source projects, expected behavior and attitude toward new contributors; how to start small, take risks, ask lots of questions; and how to get started with common open source tools like Maven, Git, and JIRA. Students will leave this workshop the soft skills and the hard skills required to make meaningful contributions.
Take the advantage and connect upstream to downstreamRico Lin
The document discusses connecting upstream and downstream communities. It defines upstream as production and downstream as users and feedback. It proposes taking advantage of both communities by contributing fixes and features to upstream, integrating upstream changes, and providing feedback downstream. It addresses common questions and concerns about participation from different roles like products, managers, engineers, and students. It emphasizes the benefits of collaboration like improved skills, experiences, and preventing bad decisions.
Take the advantage and connect upstream to downstreamRico Lin
This document discusses strategies for connecting open source upstream projects with downstream products. It defines upstream as the development of the open source project and downstream as how the project is integrated into products. It then provides advice for different roles on how to engage with the open source community in a way that benefits both the community and their products.
k6 is an open source load testing tool that was acquired by Grafana in 2021. It allows teams to test reliability before problems impact users by simulating user traffic to applications and services. The k6-operator allows running distributed k6 tests on Kubernetes and integrates k6 into developer workflows. It provides many options for configuring and scaling tests through JavaScript scripts.
This document discusses extending kubectl functionality through plugins. It introduces kubectl plugins and Krew, a plugin manager for kubectl. It covers developing and publishing plugins, including writing plugins in any language, creating a krew manifest, and automating plugin updates through GitHub actions.
Enhancing Data Protection Workflows with Kanister And Argo WorkflowsLibbySchulze
This document discusses enhancing data protection workflows with Kanister and Argo Workflows. It begins with discussing the need for data protection of stateful workloads on Kubernetes and challenges with current approaches. It then provides an overview of Kanister, an open source tool for application-level data protection on Kubernetes. Kanister uses custom resources and functions to abstract away complex data protection workflows. It also works with Argo Workflows to scale parallel data operations. The document concludes with a demo of using Kanister's CSI functions to create and restore snapshots and scaling snapshots with Argo Workflows.
This document discusses 10 common fallacies in platform engineering. It begins by introducing the speaker and topic, which are 10 fallacies seen in platform engineering and how to mitigate them. Some of the fallacies discussed include prioritizing the wrong procedures, relying only on visualizations, trying to replace all tools at once, providing too much freedom without constraints, and trying to compete directly with large cloud providers. The goal of platform engineering is to standardize processes and reduce cognitive load on developers and operations teams.
This document introduces Fluvio, an open-source data streaming platform founded by the creators of Nginx's open-source service mesh. It provides a programmable platform for data in motion that can be used to build analytics pipelines, track user behavior and sensor data, and enable fraud detection. Fluvio offers better performance and lower costs compared to Kafka. The roadmap details ongoing development of Fluvio and its cloud offering from InfinyOn, including adding smart modules, connectors, and pipelines.
The document summarizes a CNCF webinar about Project Updates with LitmusChaos. The webinar agenda covers what's new in LitmusChaos 2.0, use cases from iFood and HaloDoc, and a demo of making an e-commerce application resilient. For iFood, the challenges of a growing online food delivery platform moving to microservices are described. For HaloDoc, the service reliability challenges of a hybrid cloud-native healthcare application are covered. LitmusChaos helps both companies by providing experiments, observability, and automation to test reliability.
This document discusses Sigstore, a new standard for signing, verifying, and protecting software. It provides three key pieces - Cosign for signing things, Fulcio for signing with short-lived certificates, and Rekor for verification and monitoring. Sigstore allows signing of software artifacts, documents like SBOMs and attestations, and git commits. Attestations provide signed statements about software, and Sigstore ensures their integrity. Sigstore supports achieving different levels in the SLSA framework for supply chain security. It also aligns with frameworks from NIST and CIS. Tools like Gitsign allow "keyless" signing of git commits to meet requirements for verified history and two-person review.
This document summarizes a presentation on avoiding configuration drift with Argo CD. It introduces configuration drift as differences between environments that are supposed to be similar, such as undocumented changes or "cowboy deployments". It then discusses how configuration drift can occur in Kubernetes and strategies like GitOps and Argo CD that use bidirectional synchronization between code repositories and clusters. This helps guarantee clusters always deploy the desired configuration from Git and can self-heal if manual changes are made. The presentation includes a live demo of these concepts using Rancher and Argo CD.
This document summarizes a virtual meetup on app modernization. It discusses that 79% of app modernization efforts fail, with the average cost being $1.5 million and time being 16 months. App modernization aims to improve scalability, engineering velocity, and remove technical debt. Common obstacles include complexity, technical debt, and lack of resources. Modernizing just the UI without the business logic is ineffective. The document recommends prioritizing modernizing the business logic first to achieve the most benefits, and provides guidance for successful modernization projects such as defining requirements, securing resources, training teams, and providing the right tools.
CNCF Live Webinar: Low Footprint Java Containers with GraalVMLibbySchulze
GraalVM Native Image can compile Java applications into native executables for improved performance and lower resource usage compared to the traditional Java Runtime. It works by ahead-of-time compiling Java applications into native images that have a smaller footprint when deployed in containers and start faster than traditionally interpreted Java applications. Native images generated by GraalVM Native Image were shown to use half the memory and achieve better throughput than the same application running on the Java Runtime when deployed to Oracle Kubernetes Engine.
This document summarizes a workshop about using EnRoute and Open Policy Agent (OPA) to enforce policies at the ingress level. It includes an overview of EnRoute and OPA, a system diagram, differences between EnRoute and other ingress controllers, how OPA can be used for attribute-based access control (ABAC). It then demonstrates configuring EnRoute with OPA integration, installing an example workload secured with JWT, enforcing JWT claims using an OPA policy, and verifying the policy is applied.
1. An air-gapped Kubernetes environment restricts internet access to increase security by preventing downloads of malicious data and attacks from outside entities.
2. Implementing an air-gapped Kubernetes cluster is more difficult than a standard one and requires additional effort for maintenance, but provides protections such as preventing data exfiltration by third parties.
3. Deploying components like the ELK stack in an air-gapped environment requires manually downloading, transferring, and installing charts and images due to the lack of access to external registries and repositories. Processes and permissions must be tightly controlled to maintain security.
CNCF_ A step to step guide to platforming your delivery setup.pdfLibbySchulze
1. This document provides a step-by-step guide to establishing an internal developer platform to help teams build applications more efficiently.
2. It recommends treating the platform as a product with a product owner, roadmap, and user interviews. Prioritize components based on how much developer and operations time they save.
3. Agree on core technologies like containers and Kubernetes as the minimum standard. Identify evangelistic teams to pilot the initial platform offerings.
CNCF Online - Data Protection Guardrails using Open Policy Agent (OPA).pdfLibbySchulze
The document discusses a presentation by Joey Lei and Anders Eknert on data protection guardrails using Open Policy Agent (OPA). It provides background on the speakers and an overview of OPA, including how it works, the Rego policy language, and OPA's open source community. It then discusses how data protection policies can be enforced as code using OPA to provide guardrails for infrastructure-as-code deployments and prevent misconfigurations that could compromise availability, integrity or confidentiality of data. Examples of policy checks for recovery objectives, retention, backup strategies and exfiltration protection are provided.
This document summarizes a presentation about securing Windows workloads in a hybrid Kubernetes cluster. It begins with an overview of Calico and describes what a hybrid cluster is. It then discusses running Windows containers and the need to choose container base images wisely. The presentation covers how to secure Windows workloads using Calico for networking and policy enforcement. It concludes with information about demo resources and links for further reading.
This document summarizes a presentation about securing Windows workloads in a hybrid Kubernetes cluster. It begins with an overview of Calico and describes what a hybrid cluster is. It then discusses running Windows containers and the need to choose container base images wisely. The presentation covers how Calico can be used to secure Windows workloads by providing networking and policy enforcement capabilities. It concludes with information about demo environments and resources for working with Windows and Kubernetes.
Advancements in Kubernetes Workload Identity for AzureLibbySchulze
This document summarizes Azure Workload Identity, a new solution for providing managed identities to Kubernetes workloads. It discusses the limitations of the existing AAD Pod Identity solution and introduces the motivations and architecture of Azure Workload Identity. Key points include that it eliminates identity assignment wait times, dependencies on Kubernetes custom resource definitions and the IMDS, and supports non-Azure Kubernetes clusters and non-Linux nodes. Integrations, the roadmap, and resources are also outlined.
This document discusses approaches to containerizing operating systems and development environments to automate software project setup and decrease onboarding time. It analyzes different layers involved in coding (project source, libraries, OS packages, OS, device) and whether their setup is declarative. Containerizing the OS and using tools like Docker, Nix, and containerized dev environments can automate previously manual setup steps and ensure consistency across environments. Fully automated solutions include using online IDE services while bringing your own browser and device.
This document discusses challenges around detecting software vulnerabilities in Kubernetes artifacts and proposes a solution called KubeClarity. It notes that effective vulnerability scanning requires an accurate software bill of materials (SBOM) but these are difficult to obtain for various reasons. KubeClarity aims to address these challenges by yielding SBOMs and detecting vulnerabilities across container images and code directories. It does this using multiple analyzers and scanners to scan at different stages, and groups results under applications to navigate dependencies. The high-level architecture includes runtime scanning in clusters and CI/CD pipelines using remote centralized scanners to provide faster and more complete vulnerability detection.
Have you ever built a sandcastle at the beach, only to see it crumble when the tide comes in? In the digital world, our information is like that sandcastle, constantly under threat from waves of cyberattacks. A cybersecurity course is like learning to build a fortress for your information!
This course will teach you how to protect yourself from sneaky online characters who might try to steal your passwords, photos, or even mess with your computer. You'll learn about things like:
* **Spotting online traps:** Phishing emails that look real but could steal your info, and websites that might be hiding malware (like tiny digital monsters).
* **Building strong defenses:** Creating powerful passwords and keeping your software up-to-date, like putting a big, strong lock on your digital door.
* **Fighting back (safely):** Learning how to identify and avoid threats, and what to do if something does go wrong.
By the end of this course, you'll be a cybersecurity champion, ready to defend your digital world and keep your information safe and sound!
Book dating , international dating phgrathomaskurtha9
International dating programhttps: please register here and start to meet new people todayhttps://www.digistore24.com/redir/384521/godtim/.
get started. https://www.digistore24.com/redir/384521/godtim/
4. INTRODUCTIONS
What is purpose of this webinar?
● To help end users navigate the community and project
● To encourage contributions
5. INTRODUCTIONS
What is the OpenTelemetry project?
● A collection of tools, APIs, and SDKs
● To help you analyze your software’s
performance and behavior
● Merging of OpenTracing and
OpenCensus in 2019
9. CURRENT & FUTURE STATE
What’s the current state of the project?
opentelemetry.io/status
10. CURRENT & FUTURE STATE
What’s the current state of the project?
Data Model GA (2020) GA (2021) GA (2022)
API Spec GA (2021) GA (2022) In progress
SDK Spec GA (2021) GA (2022) In progress
Protocol GA (2021) GA (2022) GA (2022)
Implementations 8 GA, 4 in progress 0 GA, 5 RC, 7 in
progress
0 GA, 0 RC,
Collector usable in
prod
Traces Metrics Logs
11. CURRENT & FUTURE STATE
What’s new and upcoming?
● Metrics RC and GA releases
● Profiles being added as a
new signal
● Logging GA targeted for 2023
● Instrumentation availability and quality
● Community demo application SIG
● End user discussion group
13. NAVIGATING THE PROJECT
What are some of the various OpenTelemetry concepts and components?
● API
● SDK
● Semantic conventions
● Specification
● Collector
● OTLP
14. NAVIGATING THE PROJECT
What are some of the various OpenTelemetry concepts and components?
● API
● SDK
● Semantic conventions
● Specification
● Collector
● OTLP
Provides a standard way to collect
instrumentation data
15. NAVIGATING THE PROJECT
What are some of the various OpenTelemetry concepts and components?
● API
● SDK
● Semantic conventions
● Specification
● Collector
● OTLP
Provides standard ways to configure what
we want to do with the instrumentation
data collected by the API
16. NAVIGATING THE PROJECT
What are some of the various OpenTelemetry concepts and components?
● API
● SDK
● Semantic conventions
● Specification
● Collector
● OTLP
Conventional attributes that
describe common software
operations
17. NAVIGATING THE PROJECT
What are some of the various OpenTelemetry concepts and components?
● API
● SDK
● Semantic conventions
● Specification
● Collector
● OTLP
Provides blueprints for all of the
above to bring standardization
across all languages
18. NAVIGATING THE PROJECT
What are some of the various OpenTelemetry concepts and components?
● API
● SDK
● Semantic conventions
● Specification
● Collector
● OTLP
A highly configurable system for
processing telemetry data
19. NAVIGATING THE PROJECT
What are some of the various OpenTelemetry concepts and components?
● API
● SDK
● Semantic conventions
● Specification
● Collector
● OTLP How each data signal should be
encoded and transferred over
OpenTelemetry’s exchange protocol
20. NAVIGATING THE PROJECT
What are the SIGs?
● Special Interest Groups
● Improve workflow, manage project efficiently
● Each SIG meets regularly, meeting notes and recordings are
available (check public calendar)
● Examples: Communications, Ruby, Collector
21. NAVIGATING THE PROJECT
What is the Governance Committee?
● Role: “to be a live, responsive body that can refactor and reform
as necessary to adapt to a changing project and community”
What is the Technical Committee?
● Role: “responsible for all technical development within the
OpenTelemetry project”
22. NAVIGATING THE PROJECT
What about documentation?
● opentelemetry.io/docs
● Communications SIG
● Some languages have more
comprehensive documentation than
others
● Standardization and improvements
under way
23. NAVIGATING THE PROJECT
Bonus: What are OTEPs?
● OpenTelemetry Enhancement
Proposal
● OTEP process for proposing changes to
the specification
● Cross-cutting changes that “introduce
new behaviour, change desired
behaviour, or otherwise modify
requirements”
24. GETTING INVOLVED
● How do I get help with using OpenTelemetry?
● What areas need help, and why should/how can I contribute?
25. GETTING INVOLVED
How do I get help with using OpenTelemetry?
● Slack
○ Vendor-specific or #otel-vendor
○ General
● Github
● End user discussion (incoming)
27. GETTING INVOLVED
What areas need help, and why should/how can I contribute?
● Honestly, everything
● But particularly:
○ Documentation
○ PHP
○ Instrumentation (defining semantic conventions and
maintaining contributed instrumentation)
29. GETTING INVOLVED
What areas need help, and why should/how can I contribute?
Implementers have one view of the universe, end
users have another. We need more end users to speak
up and have a voice in the project!
Ted Young, co-founder of OpenTelemetry and
Director of Developer Education, Lightstep
30. GETTING INVOLVED
What areas need help, and why should/how can I contribute?
Juraci Paixão Kröhling, OpenTelemetry maintainer and
Software Engineer, Grafana
31. GETTING INVOLVED
What areas need help, and why should/how can I contribute?
…the biggest advantage is that companies can help shape the
project's direction according to their needs, and I don't mean it in a
bad way at all: a lot of times, the project maintainers make
decisions based on what they think users would want. Sometimes,
we have data or requests from actual customers, but it's not the
same thing: having the opinions of a diverse user base is essential
for the project's success.
Juraci Paixão Kröhling, OpenTelemetry maintainer and
Software Engineer, Grafana
32. GETTING INVOLVED
What areas need help, and why should/how can I contribute?
But one thing I see companies doing wrong is just telling their folks
to contribute, without a strategy in mind. So, my advice is to focus
on the areas that matter to the company, with a plan and strategic
direction. If they can get measurable goals attached to the
company's own goal, so much the better: this way, their open
source contributions become relevant to the company!
Juraci Paixão Kröhling, OpenTelemetry maintainer and
Software Engineer, Grafana
33. GETTING INVOLVED
What areas need help, and why should/how can I contribute?
I love working in open source because its
global nature exposes me to a very diverse set
of people, ideas, and opinions that would
otherwise be difficult to tap into.
Daniel Dyla, OpenTelemetry maintainer & Governance
Committee Member, and Senior Open Source Architect,
Dynatrace
34. GETTING INVOLVED
What areas need help, and why should/how can I contribute?
I also especially love the community feeling in
OpenTelemetry where vendors and platforms
who would ordinarily be considered competitors
can work together to improve the state of the
ecosystem for everybody involved.
Daniel Dyla, OpenTelemetry maintainer & Governance
Committee Member, and Senior Open Source Architect,
Dynatrace
35. GETTING INVOLVED
What areas need help, and why should/how can I contribute?
…participating and contributing to OSS helps
you hone your skills. If you have not worked for
a remote-first company before, joining an OSS
project will help you gain real world experience.
Ariel Valentin, OpenTelemetry contributor & adopter, and
Software Engineer Observability, GitHub
36. GETTING INVOLVED
What areas need help, and why should/how can I contribute?
● What are you interested in?
● Code and non-code contributions welcome
● Join:
○ Mailing lists
○ The appropriate SIG
○ Community meetings
37. GETTING INVOLVED
What areas need help, and why should/how can I contribute?
● Share your experiences and feedback about using
OpenTelemetry with us!
39. RESOURCES
OpenTelemetry links
● Official site
● Community Github
● Google calendar
● CNCF Slack
Get or keep in touch with me!
● LinkedIn (reese-lee)
● @reesesbytes (Twitter)