Home Blog Page 2

Meet the new GM of CNCF – Priyanka Sharma

CNCF, a Linux Foundation project, recently appointed Priyanka Sharma as its new GM. As a long time expert of cloud native technologies Sharma brings unique vision and insights to the organization. On behalf of the Linux Foundation, Swapnil Bhartiya, founder and producer at TFiR talked to Sharma to better understand the vision she has for CNCF and what goals she has set for herself and the foundation.

Here is the transcript of our interview.

Swapnil Bhartiya: Hi, this is Swapnil Bhartiya. Today, we have with us Priyanka Sharma. Now she’s in the role of general manager of CNCF. Priyanka, first of all, welcome to the show in your new role.

Priyanka Sharma: Thank you so much for having me, Swapnil.

Swapnil Bhartiya: What exactly is the role of GM at CNCF, and how different is it from the role of executive director that Dan used to have there?

Priyanka Sharma: No difference at all, actually. I am stepping into the role Duncan had. Across the LF, various projects and some foundations have different titles for the leadership, and me being a GM is really giving a nod to trying to consolidate everything as one title, so that’s really where it comes from, it’s the same job.

Swapnil Bhartiya: If you look at CNCF now, it has played a very critical role in creating a home for cloud native technologies like Kubernetes, and now there are so many … I mean the landscape is so huge you cannot even see it, which also mean that a lot of consolidation within CNCF has to happen from the point of view of a lot of projects are overlapping, a lot of projects have gaps. What are your thoughts about that?

Priyanka Sharma: Yes. Absolutely. I actually think it’s a great thing. By charter, the CNCF does not intend to be a kingmaker. We are very different, I guess, from any other foundations in that we really focus on spreading the wave of cloud native for helping the ecosystem build better software quicker and more resiliently. For that, there are multiple tools people can use. They may use option A for telemetry versus option B for reasons that are specific to their system. And we don’t want to be getting into the middle of that. We want to support every solid, good project out there with a neutral IP space, open governance, best practices, support with marketing education, etc. It’s actually a good thing for the end users to have choice, and we enable that.

Swapnil Bhartiya: Right. If you look at CNCF, I think it’s like ’13, ’14, it’s been four or five years since the organization has been around, a lot of projects under the foundation have kind of matured. The ecosystem itself has matured. There are a lot of companies who are doing … and things are moving from testing to production. And there is a very healthy ecosystem there. What role is cloud CNCF playing today for the ecosystem, and how do you see the evolution of CNCF itself?

Priyanka Sharma: Great question. A few things. First off is yes, we’ve made great progress. The first wave of cloud native has gone exceptionally well. 2016, when I joined this ecosystem as a project contributor to open tracing, we were still talking about what are microservices, why you need to do cloud computing, very basic, right? And since then, a lot has changed, which is awesome. However, with new maturity, comes new complexity, and that’s why you see we are still accepting new projects, right, to support the entire development cycle.

In addition, there’s the crossing the chasm, as they say, for various technologies and projects. Kubernetes is definitely crossing the chasm right now, but we have not just 1 but 10 graduated projects, including Kubernetes. We are supporting all of those projects to also cross the chasm. We need to also make Kubernetes more widespread. If you notice, most KubeCons that happen, which are our flagship events, I think at least 25% of the audience each year is brand new first timers.

We actually were having conversation just a few hours back today about don’t underestimate the importance and need for consistent cloud native one on one nurturing. The job is far from done. We need to go deeper with developer engagement. We need to go deeper with end user engagement now that we have made some headway. The second wave of cloud native is just starting.

Swapnil Bhartiya: Excellent. Now when we look at second wave, so far the ride has become kind of easy breeze. But what are the challenges that you see that you want to tackle as you move into the second wave? Or what kind of challenges you’re setting for yourself, which are not the easy one, but you see there is a demand so that you have to do that?

Priyanka Sharma: I had various thoughts and ideas around this stuff. And when I was going to join the organization, I was going to take a complete few months to do a listening tour. Of course you know what they say about the best-laid plans of mice and men, the pandemic hit. The world scenario has completely changed. There’s been shelter-in-place orders various places. People are suffering many places with illness. There is the COVID illness. And then there’s other things that come up and you’re stuck at home for so long, so it’s not an easy time. It’s not a normal time. It’s not a usual time. And that reflects for the cloud native community as well. As an example, we’ve hosted the KubeCons, our flagship events in person with great fanfare, with lots of support, love and excitement from the community.

Now, we have to pivot completely and do it all online in a world where the online solutions are sort of catching up to be able to support large scale events like ours. So joining in, there are challenges that have been thrown my way by just the timing, right? In addition to the events which we’re working very hard on as a team, there is also just your community has different needs. There’s some people may want to be switching jobs or looking for jobs. That’s one element that we need to think about. Some people may need the support that they felt otherwise by going to meet ups, by being more in touch with people around them on cloud native. There are others whose businesses actually might be growing exponentially just because everything’s going online, just supporting them with the technology. There are various elements to this new, strange time that we find ourselves in. So that is a big challenge.

In addition, I would say Dan and Chris have built an amazing, massively impactful organization. For me, I intend to keep this momentum going, to keep building on what they have created. We all stand on the shoulders of giants here. I think the next big thing once we get through pandemic is to double down on the end user ecosystem. The end users have grown and become consistently more sophisticated and technical over the times in the last four years I’ve been involved. We need to support that and enable greater adoption, better insights, safe spaces to discuss and communicate with each other, so that’s coming.

And then finally, as I said, developer education and engagement has to go deeper and wider. That’s what I set for myself.

Swapnil Bhartiya: When you look at CNCF, what vision do you have? Because you yourself have been in the community, in the industry for so long, but you were also on the outside. You are not inside Linux Foundation. You have been working with private companies, so you have an outsider’s view. What unique vision did you bring to the CNCF? Because sometimes when we work within an organization for so long, we have our own myopic view. Can you talk about that?

Priyanka Sharma: You’re absolutely right, that I have worn multiple hats, seen CNCF through different lenses, and I can bring that perspective to this foundation. I’d say one thing that’s been a somewhat disturbing trend I notice was this othering of different parts of the community. It’s like CNCF staff versus end user versus project creator versus GB versus this. You can have so many different categories. But the reality is I really don’t think that’s the way the ecosystem truly functions well I don’t think there’s that much meat in that way of thinking. And we need to change and go back to what we’re good at, which is being builders and doers and being team cloud native, all of us together.

If we in fight, then we don’t stand strong and build upon our work, but rather just dissipate energy. And I’ve seen that trend happen in cloud native. I cannot speculate on the reasons for it, but I make a call to each and every one of you, just know we’re in it together. I have worn multiple hats in this industry. I have been a project contributor. I have been an educator, a marketer. I have been a developer advocate. I have been a governing board member. I have done many things. And now, I’m the GM. Let me tell you, we are all in it together no matter what hat we wear, and we need to make an extra effort to do that. And that is something I think will be a big change if we can achieve it.

Swapnil Bhartiya: You can have as much GitHub repository for tech issues. But what realistic efforts we can see from CNCF to kind of achieve the kind of vision you are bringing, because this is kind of different than a technological problem?

Priyanka Sharma: I hear that. I think that a lot of it starts with the leadership. I have been put in this position and my number one goal is to always keep my door open, these days virtually. I live by an open calendar. Anybody can book time with me, talk to me, tell me what you think, and reach out to me. And I mean it. I have serious blocks open. Of course, they’re starting to get booked up really quickly, which is nice because that means people are taking me up on this offer, that let’s engage. Let’s talk it out. Let’s see where we are disagreeing, and either agree to disagree, which is a totally fair thing to do, or come closer together in some form of consensus.

I think conversation is the first step. We all get so busy with the day-to-day work, that that goes away to the wayside. And when that happens, miscommunication just develops and deepens. So number one is open door policy. Let’s talk. Whenever there’s confusion, let’s do that.

The other is bringing greater transparency. It’s just a habit I have that I picked up at GitLab working under Sid, which is being all remote, it’s important to document everything. So most of my meetings, they will have a document where we write down agenda notes, etc. Sharing that with the people you talk to so everyone’s actually on the same page. We wrote this down. This is what we’re doing. Little things like that can I think go a really long way in making sure people are moving in lockstep together. All this is also, by the way, an ongoing effort that you cannot let up. You have to keep being transparent. You have to keep being open. This is not a onetime thing. People have to keep being transparent. People have to keep their door open. It’s an ongoing effort that I will not stop and let up on. I think it will make a difference.

I’m actually proud to report that I’m already seeing, having taken the time to talk to a lot of people, we really are on the same team. Everyone wants us to just build better software together, and I’m very confident that the cultural change is happening as we speak.

Swapnil Bhartiya: Awesome. Before we dive this last question, we are going through a crisis, a very serious crisis, and we don’t see any end in the sight right now. It has impacted all of us. For example, we were supposed to be in person at open source event, but everything is moving to online events. How does this impact the industry in general? Because a lot of these events, they do bring people together, where they not only hallway track, where people just touch base with colleagues, but a lot of … actually, a lot of partnerships are forged there. What impact do you see, and how do you see CNCF would respond to that or is already responding to that?

Priyanka Sharma: Absolutely. Events play a great role in the community and ecosystem, and that’s just evidenced by the awesomeness of KubeCons. Being at every KubeCon that I could be had open doors for me. Connected me to people who were happy to mentor, guide, talk to me. We cannot lose that, right? We all are waiting for things to change, right? The pandemic to go away one day for us to be able to meet in person. While we wait for that, here and the CNCF team, we are working to make KubeCon EU virtual in August as awesome of an experience as possible. There’s lots of ideas that we have. We sometimes have technology limitations in terms of the platforms that are available, and we’re trying to work through that.

My sense is that we’ll have a bunch of ideas in experiment at KubeCon EU in August, and by the time KubeCon North America, which was going to be Boston, but just today was announced is going to be virtual as well, by the time that rolls around, I think we’ll have a lot more cool engagement and innovation possible.

I did a small event a few weeks before joining CNCF, just for fun. I just wanted to see other community folks. And the reality is that it was cool because we were able to livestream, and we’d expected 200 people, but 2,000 showed up. No, actually, 7,000 at maximum views. It was crazy, crazy numbers. And that’s the equalizer that comes with online events. It’s nice to be able to reach more people. We have to figure out the engagement, have more fun games and trivia prizes, ways to connect a maintainer to someone who has a question, ways to connect a student to someone who will tell them how to contribute. These are the things we need to work on and it’s actively underway.

Swapnil Bhartiya: Awesome. Thank you, Priyanka, so much for taking time out and talking to me today, and I look forward to talk to you again. Thank you.

Priyanka Sharma: Same here. Thank you, Swapnil.


Student Linux club refurbishes computers to support distance learning (opensource.com)

Cam Citrowske on opensource.com writes:

It was March 17, 2020, and I was in my classroom at Aspen Academy. The clock was ticking. This was to be the last day of school before we, along with every other public school in Minnesota, would close due to the outbreak of the new coronavirus. I had students in my room during lunch, advisory periods, and my elective classes all doing the same thing—installing Linux onto old computers so we could give them to students who would use them for school at home during the shelter in place order. I was only going to have the kids’ help until dismissal time, but in the end, we had 17 computers ready to go. It was a start.

Read more at opensource.com

Solving technical debt with open source

Ibrahim Haddad and Cedric Bail at the Linux Foundation have published a new whitepaper on solving technical debt with open source:

Technical debt, a term used in software development, refers to the cost of maintaining source code that was caused by a deviation from the main branch where joint development happens. 

A broader interpretation of what constitutes technical debt is proprietary code by itself:

    • A single organization has developed it.
    • It is source code that the organization alone needs to carry and maintain.
    • In some cases, the organization depends on a partner’s ability to maintain the code and carry that said debt.

The following symptoms can identify technical debt:

    • Slower release cadence Time increases between the delivery of new features
    • Increased onboarding time for new developers Onboarding new developers become highly involved due to code complexity where only insider developers are familiar with the codebase. The second manifestation of this symptom is the difficulty in retaining developers or hiring new developers.
    • Increased security issues At least, experiencing more security issues than the main upstream branch.
    • Increased efforts to maintain the code base Maintenance tasks become more time consuming as the body of code to maintain becomes larger and more complex.
    • Misalignment with the upstream development cycle illustrated in the inability to keep pace, be aligned with the upstream development and release cycles.

Click here to read the abstract and download the new whitepaper

How open source development provides a roadmap for digital trust, security, safety, and virtual work

Mike Dolan writes on the Linux Foundation blog:

We’re seeing a shift to virtual events, remote work cultures, virtual “happy hours,” and other means of productively working together, virtually. Many of these practices will stick with us post-pandemic. Our organization is already exploring how to use virtual events to augment future physical events (yes, they will exist again). 

Virtual conferences may be a great path to offering more inclusive events where those of us unable to travel to an event physically can still find a way to participate at some level. We’re seeing the impact of virtual training and certifying professionals in freely available open source technologies — and it has a real impact on job prospects and employment. Virtual testing proctors have become an effective way to certify professionals. Similarly, virtual platforms can help facilitate mentorship and enable less experienced developers to find and connect with more skilled developers willing to lend a hand.

The coronavirus has opened the world’s eyes to the needs of systems and plans for pandemic situations. This year we will likely see technology communities and organizations adapt and develop the “playbook” for how the world does business in the face of a pandemic. But many of those practices will likely stay with us long after we defeat COVID-19. 

Read more at The Linux Foundation

New Training Course Teaches Kubernetes Application Management with Helm

The Linux Foundation, the nonprofit organization enabling mass innovation through open source, today announced the availability of a new training course, LFS244 – Managing Kubernetes Applications with Helm. LFS244 was developed in conjunction with the Cloud Native Computing Foundation® (CNCF®), which builds sustainable ecosystems for cloud native software, and hosts both the Kubernetes and Helm open source projects. The course is designed for system administrators, DevOps engineers, site reliability engineers, software engineers and others who wish to enhance their operational experience running containerized workloads on the Kubernetes platform.

New Kubernetes Security Specialist Certification to Help Professionals Demonstrate Expertise in Securing Container-Based Applications

The Linux Foundation, the nonprofit organization enabling mass innovation through open source, and Cloud Native Computing Foundation® (CNCF®), which builds sustainable ecosystems for cloud native software, today announced a new certification, the Certified Kubernetes Security Specialist (CKS) is in development. The certification is expected to be generally available before the KubeCon North America event this November.

The Linux Foundation’s First-Ever Virtual Open Source Summit (TechNewsWorld)

Jack M. Germain writes on Tech News World:

The success of The Linux Foundation’s first virtual summit may well have set the standard for new levels of open source participation.

Summit masters closed the virtual doors of the four-day joint gathering on July 2. The event hosted the Open Source Summit + Embedded Linux Conference North America 2020 and ended with more than 4,000 registrants from 109 countries.

The online platform InXpo enabled participants to be part of a real immersive technical gathering. They also can view on-demand content of sponsor resources and conference sessions for one year.

The InXpo platform enabled attendees to:

    • View 250+ informative educational sessions and tutorials, across 14 different technology tracks, and participate in live Q&A;
    • Join the ‘hallway track’ and collaborate via topic-based networking lounges in group chats, and connect with attendees in 1:1 chats;
    • Visit the 3D virtual sponsor showcase and booths to speak directly with company representatives, view demos, download resources, view job openings and share contact info.

The summit’s virtual format also provided attendees the chance to “gamify” their event experience by earning points and winning prizes for attending sessions, visiting sponsor booths, and answering trivia questions.

Read more at Tech News World

Device Drivers Training Helps Advance an Embedded Linux Career

In 2018, Anna-Lena Marx was preparing to begin the final thesis for her master’s degree. She was also working for a German company developing kernel drivers and fixing bugs in the Linux kernel and Android internal system.

Anna-Lena wanted to improve her Linux kernel development skills, so she applied for and was awarded a Linux Foundation Training (LiFT) Scholarship in the Kernel Guru category.

Open Source Communities and Trademarks: A Reprise

The Linux Foundation has published a new blog about the use of Trademarks in open source communities:

A trademark is a word, phrase or design that denotes a “brand” that distinguishes one source of product or solution from another. The USPTO describes the usage of trademarks “to identify and distinguish the goods/services of one seller or provider from those of others, and to indicate the source of the goods/services.” Under US trademark law you are not able to effectively separate ownership of a project mark from control of the underlying open source project. While some may create elaborate structures around this, at the end of the day an important principle to follow is that the project community should be in control of what happens to their brand, the trademark they collectively built up as their brand in parallel with building up the functionality of their code. 

For this reason, in communities that deem their brand important, we also file registrations for trademark protection to reserve the rights in the mark for the project, commonly in the United States, China, European Union, Japan, and other countries around the world. Registered marks will often have a ® symbol. This is different from a common law trademark right where you often see a ™ symbol with the mark. Having a registered trademark is often important because it enables us to better protect the community against misrepresentation, misuse, and confusion in the ecosystem between what is actually the community-built project, and what is not. This is often based on specific benefits that arise from the registration, which may vary from country to country.

Click to read more at the Linux Foundation