Language Selection

English French German Italian Portuguese Spanish

Chef Liberated

Chef Goes All-In on Open Source

  • DevOps Chat: Chef Goes All-In on Open Source

    In front of next month’s ChefConf in Seattle, Chef has announced a major refinement to its business model. Affirming and clarifying its commitment to open source business models, Chef will now and in the future release all of its software as open source.

LWN and original from Chef

  • Chef becomes 100% free software

    Chef, the purveyor of a popular configuration-management system, has announced a move away from the open-core business model and the open-sourcing of all of its software.

  • Introducing the New Chef: 100% Open, Always

    Today, Chef is announcing meaningful changes to the way that we build and distribute our software. Chef has always believed in the power of open source. This philosophy is core to the way that we think about software innovation. There is no better way to build software than in the open in partnership with individuals and companies who use our stack in the real world. And for enterprises and other organizations facing complex challenges, Chef backs up our software by building and supporting distributions for our projects with the resources necessary for these organizations to succeed.

    Going forward, we are doubling down on our commitment to OSS development as we extend our support for the needs of enterprise-class transformation. Starting today, we will expand the scope of our open source licensing to include 100% of our software under the Apache 2.0 license (consistent with our existing Chef Infra, Chef InSpec, and Chef Habitat license terms) without any restrictions on the use, distribution or monetization of our source code as long as our trademark policy is respected. We welcome anyone to use and extend our software for any purpose in alignment with the four essential freedoms of Free Software.

Chef-paid 'analysi' comments

  • Chef’s Different Recipe

    Over the course of the past three plus years, the market has seen a growing number of commercial open source organizations – with encouragement from some investors – drifting away from traditional open source licensing and norms. While there have been significant differences in the precise mechanics of their respective approaches, the common thread between the likes of Confluent, Elastic, MongoDB, Redis Labs and TimeScale has been their willingness to violate open source norms long considered sacrosanct.

    Contrary to internet opinions, however, little if any of this was done with malicious intent, or absent due consideration for the grave implications of the various moves. In the majority of cases, the difficult decisions were made reluctantly, under duress. Whether that duress was real or more theoretical in nature is a matter of some debate, but there can be no doubt that the companies involved embarked on these courses because they felt they had to, not because they particularly wanted to.

    There have been many contributing factors to this drift away from open source, including the intrinsic problems of compelling payment for assets otherwise available for free, but by far the biggest driver has been the once cold war that recently escalated into a full scale hot war between cloud vendors and commercial open source providers. The relationships between these archetypes is fraught, and has evolved from relatively benign indifference on the part of open source providers to existential, unmanageable dread.

By Sean Michael Kerner

  • Chef Opens Up DevOps Platform With Enterprise Automation Stack

    Chef has been at the forefront of the DevOps movement with its namesake open-source Chef project. Not all of Chef's platforms, however, have been open-source, with some available under commercial proprietary licenses.

    On April 2, Chef announced a major shift in its company alignment, making all of its products available under the Apache 2.0 open-source license and revealing a new supported platform called the Enterprise Automation Stack. The move to being 100 percent open-source is an effort to provide more transparency and encourage broader collaboration. Rather than moving the projects to an independent, third-party open-source foundation and governance model, however, Chef will continue to lead and operate the projects.

    "When looking at foundations and the shape of open-source, a big issue is deciding who controls and builds the upstream asset. As soon as you put software into a foundation, the foundation controls the asset," Adam Jacob, co-founder and CTO of Chef, told eWEEK. "One of the things that we're doing is aligning our own commercial interests with our interest in being the upstream that provides the project."

Goodbye Open Core — Good Riddance to Bad Rubbish

  • Goodbye Open Core — Good Riddance to Bad Rubbish

    This morning, Chef Software announced that it will be releasing 100% of its software as Open Source, under the Apache License. Going forward, all of its product development will be done in the open, with the community, and released as Open Source Software. Chef is done with being Open Core, and is now a Free Software Product company. Good riddance to bad rubbish.
    As a Co-Founder of Chef, a board member, and a community member, I couldn’t be more thrilled. For me, it eliminates the longest-running source of friction and frustration from my time at Chef. On the one hand, we have a community that cares about the software, and about each other, where we develop the software in concert with our users and customers. On the other, we produced a proprietary software stack, which we use to make money. Deciding what’s in, and what’s out, or where to focus, was the hardest part of the job at Chef. I’m stoked nobody has to do it anymore. I’m stoked we can have the entire company participating in the open source community, rather than burning out a few dedicated heroes. I’m stoked we no longer have to justify the value of what we do in terms of what we hold back from collaborating with people on.
    As an insider, I got to witness first-hand the boldness and deep thought put in to this transition by the team at Chef. Our incredible CEO, Barry Crist; Corey Scobie, the SVP of Product and Technology; Brian Goldfarb, CMO; Katie Long, our VP of Legal; and so many others. Thank you.

Yet more coverage

Chef Goes All Open Source

  • Chef Goes All Open Source

    The Chef automation tool, a popular solution for DevOps IT management scenarios, has announced that it will be become a 100% open source platform. In the past, the basic Chef application was available in open source form, but the company also provided several enhancements and add-on tools with proprietary licenses. Rather than building proprietary tools around an open source core, Chef will now open source all of its software under an Apache 2.0 license.

    According to Chef CEO Barry Crist, “Over the years we have experimented with and learned from a variety of different open source, community, and commercial models, in search of the right balance. We believe that this change, and the way we have made it, best aligns the objectives of our communities with our own business objectives. Now we can focus all of our investment and energy on building the best possible products in the best possible way for our community without having to choose between what is “proprietary” and what is “in the commons.”

Configuration Management Tool Chef Announces to go 100% OSS

  • Configuration Management Tool Chef Announces to go 100% Open Source

    You are here: Home / News / Configuration Management Tool Chef Announces to go 100% Open Source
    Configuration Management Tool Chef Announces to go 100% Open Source
    Last updated April 5, 2019 By Ankush Das 2 Comments
    In case you did not know, among the most popular automation software services, Chef is one of the best out there.

    Recently, it announced some new changes to its business model and the software. While we know that everyone here believes in the power of open source – and Chef supports that idea too. So, now they have decided to go 100% open source.

    It will included all of their software under the Apache 2.0 license. You can use, modify, distribute and monetize their source code as long as you respect the trademark policy.

    In addition to this, they’ve also introduced a new service for enterprises, we’ll take a look at that as you read on.

"Chef Plates All Software as Open Source"

  • Chef Plates All Software as Open Source

    The IT automation and dev ops software vendors is embracing the open source model to clarify its product line and enhance its value proposition.

  • Chef says it’s going 100% open source, forks optional…

    Chef has lifted a page from Red Hat’s recipe book, and is making all of its software 100 per cent open source, under the Apache 2 license.

    But if you’re planning to use the automation and configuration specialist’s software in production, you’re still going to be expected to cough up for a subscription.

    Chef CEO Barry Crist said in a blog post today that the company “has always believed in the power of open source”.

  • Leading DevOps program Chef goes all in with open source [Ed: CBS repeats Microsoft talking points: "Some companies are wriggling out of open-source to maximize their profits." And proprietary software companies never do?]

    Some companies are wriggling out of open-source to maximize their profits.

  • “Chef” DevOps leading program goes all-in on open source

    Chef, one of the leading DevOps companies announced from here on out it would be developing all of its software as open source under the Apache 2.0 license and revealing a new supported platform called the Enterprise Automation Stack.

Some belated coverage

  • Chef open sources 100% under Apache 2.0 license

    “Chef Enterprise Automation Stack lets teams establish and maintain a consistent path to production for any application, in order to increase velocity and improve efficiency, so deployment and updates of mission-critical software become easier, move faster and work flawlessly.”

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Leftovers: GNOME/GTK, Android-x86, Fedora, LibreOffice and More

  • g_array_steal() and g_ptr_array_steal() in GLib 2.63.1

    Another set of new APIs in the upcoming GLib 2.63.1 release allow you to steal all the contents of a GArray, GPtrArray or GByteArray, and continue using the array container to add more contents to in future. This is work by Paolo Bonzini and Emmanuel Fleury, and will be available in the soon-to-be-released 2.63.1 release.

  • GNOME Shell Hackfest 2019

    This week, I have attended the GNOME Shell Hackfest 2019 held in Leidschendam, The Netherlands. It was a fantastic event, in a fantastic city! The list of attendees was composed of key members of the community, so we managed to get a lot done — a high amount of achievements for only three days of hackfest, in fact.

  • Android-x86: Run Android on your PC: Release Note 7.1-r3

    The Android-x86 project is glad to announce the release of 7.1-r3. This is the third stable release for Android-x86 7.1 (nougat-x86). The prebuilt images are available in the following site as usual: https://www.fosshub.com/Android-x86-old.html https://osdn.net/rel/android-x86/Release%207.1 Key Features The 7.1-r3 is mainly a bugfixes release of 7.1-r2. It based on Android 7.1.2 Nougat MR2 security updates (android-7.1.2_r39). Some newer features are also back-ported from 8.1 release. We encourage users of 7.1-r2 or older release upgrade to this release.

  • David Cantrell: rpminspect-0.8 released (and a new rpminspect-data-fedora)

    Work on the test suite continues with rpminspect and it is finding a lot of corner-case type runtime scenarios. Fixing those up in the code is nice. I welcome contributions to the test suite. You can look at the tests/test_*.py files to see what I'm doing and then work through one inspection and do the different types of checks. Look in the lib/inspect_NAME.c file and for all of the add_result() calls to figure out what tests should exist in the test suite. If this is confusing, feel free to reach out via email or another means and I can provide you with a list for an inspection.

  • Fedora Community Blog: FPgM report: 2019-42

    Here’s your report of what has happened in Fedora Program Management this week. Fedora 31 was declared No-Go. We are currently under the Final freeze. I have weekly office hours in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else.

  • New Feature in Libreoffice: Full-Sheet Previews

    The feature was developed on the cp-6.2 branch of LibreOffice code-base (which is basicly Collabora Office 6.2), and is already available in Collabora Office snaphots. And is being backported to LibreOffice master, so it will be also available in LibreOffice development builds and soon in the Collabora Office snapshots.

  • Rooting for ZFS | TechSNAP 414

    We dive into Ubuntu 19.10’s experimental ZFS installer and share our tips for making the most of ZFS on root. Plus why you may want to skip Nest Wifi, and our latest explorations of long range wireless protocols.

  • 2019-10-18 | Linux Headlines

    Researchers discover a kernel bug that can crash Linux devices, Fedora 31’s release date slips, Cedalo opens up its Streamsheets code, Google announces the Android NDK 21 beta, and Unix turns 50.

  • Google Launches A Refreshed Pixelbook Laptop At $649

    Say hello to a more affordable Chromebook that's lightweight and more fun to type on.

Proprietary Software, Games, Patent Traps/Tax and Openwashing

  • Adobe Announces Plan To Essentially Steal Money From Venezuelans Because It 'Has To' Due To US Sanctions

    Adobe has long had a history of questionable behavior, when it comes to the rights of its customers, and how the public is informed on all things Adobe. With the constant hammering on the concept that software it sells is licensed rather than purchased, not to mention with the move to more SaaS and cloud-based software, the company is, frankly, one of the pack leaders in consumers not actually owning what they bought.

  • Fantasy tactical RPG Wildermyth blends a mix of hand-painted 2D and 3D art & arrives on Steam soon

    With character art during the turn-based battles that look like paper cutouts in a 3D environment, Wildermyth certainly has a strange and lovely charm to it. Currently available on itch.io where users have been testing it for some time, Worldwalker Games have now announced that their character-driven tactical RPG will enter Early Access on Steam on November 13. In Wildermyth, your party will be tasked with defending the lands from various threats, switching between the turn-based combat and making decisions on the over-world map. It has choice-based comic-styled events, which can end up changing your heroes' appearance, personalities, relationships, and abilities.

  • Paragon Looks To Upstream Their Microsoft exFAT Driver For The Linux Kernel

    With the upcoming Linux 5.4 kernel release there is now an exFAT file-system driver based on an old Samsung code drop of their exFAT driver support for mobile devices. This comes after Microsoft made the exFAT specification public recently and gave their blessing for a native Linux driver for the file-system. The Linux developers acknowledge though the current exFAT code is "horrible" and a "pile of crap" but is within the staging area. So in Linux 5.4's staging is this preliminary read-write driver for exFAT that continues to be cleaned up and further improved upon. Meanwhile there is also another out-of-tree exFAT Linux driver based on Samsung's sdFAT code that is said to be in better shape than the mainline code. But now there's another option with Paragon Software wanting to upstream their own exFAT driver into the Linux kernel.

  • VMware’s Joe Beda: Enterprise Open Source Is Growing [Ed: “Enterprise Open Source” means proprietary software and openwashing for marketing purposes]

    One of the fathers of Kubernetes says enterprise customers see the most benefit from the community-driven approach because their users get the opportunity to influence the direction development takes.

Linux Devices/Open Hardware

  • Site.js and Pi

    Chatting about Pi, on a Pi, with a chat server running on Site.js on the same Pi.

  • This MicroATX Motherboard is Based on Phytium FT2000/4 Arm Desktop SoC @ 3.0 GHz
  • Rikomagic R6 Review – Part 1: Android Mini Projector’s Unboxing and First Boot

    Rikomagic R6 is a mini Android projector that looks like a vintage radio, or depending on your point of view a mini vintage television.

  • Brief on Behalf of Amicus Curiae Open Source Hardware Association in Curver Luxembourg, SARL v. Home Expressions Inc., No. 18-2214 (Fed. Cir.)

    Curver Luxembourg, SARL v. Home Expressions Inc. is a case of first impression for the Court of Appeals for the Federal Circuit. The question on appeal is whether a design patent’s scope is tied to the article of manufacture disclosed in the patent. In this amicus brief, the Open Source Hardware Association (“OSHWA”) explains the potential effects on open source hardware development, and design practice generally, of untethering design patent protection from the article of manufacture disclosed in the patent. A large percentage of open-source hardware combines both ornamental and functional elements, and industrial design routinely involves applying design concepts from disparate fields in novel ways. To engage in this practice, open-source hardware designers need to know the universe of available source material and its limits. Further, understanding the licensing requirements of open-source hardware begins with understanding how the elements that make up that hardware may or may not be protected by existing law. Accordingly, while many creators of open-source hardware do not seek patent protection for their own creations, an understandable scope of design patent protection is nonetheless essential to their ability to collaborate with other innovators and innovate lawfully. The brief argues that the District Court in the case—and every district court that has considered the issue—correctly anchored the patented design to the article of manufacture when construing the patent. The brief explains that anchoring the patented design to the disclosed article of manufacture is the best approach, for several reasons. Connecting the patented design to the disclosed article of manufacture calibrates the scope of design patent protection to the patentee’s contribution over the prior art. It avoids encumbering the novel and nonobvious application of prior designs to new articles of manufacture, a fundamental and inventive practice of industrial design. It aligns the scope of design patent protection with its purpose: encouraging the inventive application of a design to an article of manufacture. This balances protection for innovative designs with later innovators’ interest in developing future designs. Finally, anchoring the patented design to the disclosed article of manufacture helps fulfill design patent law’s notice function by clarifying the scope of protection.

Graphics: Gallium3D and AMDGPU

  • Gallium3D's Mesa State Tracker Sees "Mega Cleanup" For NIR In Mesa 19.3

    AMD developer Marek Olšák has landed a "mega cleanup" to the Gallium3D Mesa state tracker code around its NIR intermediate representation handling. As part of getting the NIR support in good enough shape for default usage by the RadeonSI driver, Marek has been working on a number of clean-ups involving the common Gallium / Mesa state tracker code for NIR.

  • AMDGPU DC Looks To Have PSR Squared Away - Power-Savings For Newer AMD Laptops

    It looks like as soon as Linux 5.5 is where the AMDGPU kernel driver could be ready with Panel Self Refresh (PSR) support for enabling this power-savings feature on newer AMD laptops. While Intel's Linux driver stack has been supporting Panel Self Refresh for years, the AMD support in their open-source Linux driver code has been a long time coming. We've seen them working towards the support since Raven Ridge and now it appears the groundwork has been laid and they are ready to flip it on within the Display Core "DC" code.