Paul Cormier, Red Hat EVP and president of products and technologies, discusses two new products announced today at the Red Hat Summit.
Chris Wright, chief technologist for Red Hat, sat down with theCUBE cohosts Dave Vellante and Stu Miniman to discuss new developments in the open source world and NVF in telcom networks.
As the person who helps define Red Hat’s strategic vision, Wright has seen conversations shift from cost of ownership to innovation. “Today, there is a shift to operationalize complex systems,” he says. “There has been a change in open source technology from commoditization to a place where real innovation is happening, and new services are introduced quickly.”
Last year Red Hat announced its first Women in Open Source Award, created to recognize the contributions that women are making in open source technologies and communities. I was honored to be on one of the committees that reviewed more than 100 nominations and narrowed the list down to 10 finalists divided into two categories: community and academic. Then the open source community voted, and I anxiously awaited the results. I wanted every woman on both lists to win, so I knew that no matter who ended up with most votes, I'd be happy.
As an open source contributor, I began as a newbie and grew into a decent contributor thanks to working on many great projects. Today, I am mentoring new contributors on how to make their first contributions to open source. So, I think I can answer this question more elaborately.
Open source organizations have projects that need contributions from everyone, from all skills and levels of expertise. There are many non-coding ways too contribute as well, like: reporting issues, writing documentation, helping with design, trying previous versions, checking quality and translation, outreach for a product, and organizing events. Doing so helps you learn more about the open source project as well as to network with the community while adding positive contributions.
I started as a package maintainer helping with initscrpits, systemd and other packages. Then I moved up the stack to work on containers which lead me to helping with defining Fedora Docker base image and getting a membership in Base WG and Env&Stacks WG to help with Docker integration. Currently, I am working on a composite multi-container application specification called Nulecule.
I’ve been with Mozilla, as a volunteer or employee, since 2000. I got involved when I read a Slashdot comment (!) from an existing Mozilla contributor called Matthew Thomas. It said that if Mozilla failed, then Microsoft would get control of the web. I thought that the web was too awesome, even then, to be controlled by a single company, so I decided to help Mozilla out. Sixteen years later, I’m still here. I’ve done many things in my time, but I currently work mainly on Public Policy, which I tend to summarise as "persuading governments not to make unhelpful laws about the Internet". My current focus is copyright reform in the EU; you can read our policy positions on the Mozilla Policy blog.
Whitehurst used the auto industry as an example where the old brands must change, or else face trouble ahead. Automakers have been focused for the last 100 years on how to make cars more cheaply, and management has been the same way, focused on how to control employees most effectively, Whitehurst said.
Linux Foundation instructor Mike Day is an expert in Linux hypervisors and led IBM's work on the Xen and KVM hypervisors as a Distinguished Engineer. But he came upon his calling almost by accident, having been “thrown into the project with colleagues who had worked on hypervisors for more than a decade,” he said.
“It was a real challenge for me but not too long after that I became viewed as an expert on the subject,” said Day, who now teaches KVM and Linux developer courses for Linux Foundation Training.
Open source licenses and the software programs that go along with them are critical to bringing great minds together to build great technology that spans boundaries while solving real world problems.
I believe open source licensing will continue to play a part in IoT, and I think it has to given the breadth of what IoT is all about. Today many IoT solutions are proprietary as different startups and companies investigate the technology. This is great for pushing the boundaries of what is possible, what will work, and what won't work. However, each of these proprietary solutions is created in silo of each other. They cannot communicate as there are limited standard protocols for this new generation of technology to adopt. This, by definition, ends up limiting the Internet of Things because it's now "Company A's Internet of Things that can talk to each other, but not to Company B's Internet of Things." This is commonly seen in household consumer products today. I have home lighting automation that can't speak to my home security automation that can't speak to my home TV automation.