{"id":14636,"date":"2019-04-03T03:11:04","date_gmt":"2019-04-03T03:11:04","guid":{"rendered":"https:\/\/rsoftsolution.com\/blog\/chef-goes-100-open-source-2.html"},"modified":"2019-04-03T03:11:04","modified_gmt":"2019-04-03T03:11:04","slug":"chef-goes-100-open-source-2","status":"publish","type":"post","link":"https:\/\/www.rbsitsoftwaresolution.in\/blog\/chef-goes-100-open-source-2.html","title":{"rendered":"Chef goes 100% open source"},"content":{"rendered":"

Chef<\/a>, the popular automation service, today announced that it is open-sourcing all of its software under the Apache 2 license. Until now, Chef <\/a> used an open core model with a number of proprietary products that complemented its open-source tools. Most of these proprietary tools focused on enterprise users and their security and deployment needs. Now, all of these tools, which represent somewhere between a third and a half of Chef\u2019s total code base, are open source, too.<\/p>\n

\u201cWe\u2019re moving away from our open core model,\u201d Chef SVP of products and engineering Corey Scobie told me. \u201cWe\u2019re now moving to exclusively open-source software development.\u201d<\/p>\n

He added that this also includes open product development. Going forward, the company plans to share far more details about its roadmap, feature backlogs and other product development details. All of Chef\u2019s commercial offerings will also be built from the same open-source code that everybody now has access to.<\/p>\n

\"\"Scobie noted there are a number of reasons why the company is doing this. He believes, for example, that the best way to build software is to collaborate in public with those who are actually using it.<\/p>\n

\u201cWith that philosophy in mind, it was really easy to justify how we\u2019d take the remainder of the software that we produce and make it open source,\u201d Scobie said. \u201cWe believe that that\u2019s the best way to build software that works for people \u2014 real people in the real world.\u201d<\/p>\n

Another reason, Scobie said, is that it was becoming increasingly difficult for Chef to explain which parts of the software were open source and which were not. \u201cWe wanted to make that conversation easier, to be perfectly honest.\u201d<\/p>\n

Chef\u2019s decision comes during a bit of a tumultuous time in the open-source world. A number of companies like Redis, MongoDB and Elastic have recently moved to licenses that explicitly disallow the commercial use of their open-source products by large cloud vendors like AWS unless they also buy a commercial license.<\/p>\n

But here is Chef, open-sourcing everything. Chef co-founder and board member Adam Jacob doesn\u2019t think that\u2019s a problem. \u201cIn the open core model, you\u2019re saying that the value is in this proprietary sliver. The part you pay me for is this sliver of its value. And I think that\u2019s incorrect,\u201d he said. \u201cI think, in fact, the value was always in the totality of the product.\u201d<\/p>\n

Jacob also argues that those companies that are moving to these new, more restrictive licenses, are only hurting themselves. \u201cIt turns out that the product was what mattered in the first place,\u201d he said. \u201cThey continue to produce great enterprise software for their customers and their customers continue to be happy and continue to buy it, which is what they always would\u2019ve done.\u201d He also noted that he doesn\u2019t think AWS will ever be better at running Elasticsearch than Elastic or, for that matter, at running Chef better than Chef.<\/p>\n

It\u2019s worth noting that Chef also today announced the launch of its Enterprise Automation Stack, which brings together\u00a0under a unified umbrella <\/span>all of Chef\u2019s tools (Chef Automate, Infra, InSpec, Habitat and Workstation).<\/span><\/p>\n

\u201cChef is fully committed to enabling organizations to eliminate friction across the lifecycle of all of their applications, ensuring that, whether they build their solutions from our open-source code or license our commercial distribution, they can benefit from collaboration as code,\u201d said Chef CEO Barry Crist. \u201cChef 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.\u201d<\/p>\n

Article source: http:\/\/feedproxy.google.com\/~r\/techcrunchIt\/~3\/kqhYa1z3Ghw\/<\/p>","protected":false},"excerpt":{"rendered":"

Chef, the popular automation service, today announced that it is open-sourcing all of its software under the Apache 2 license. Until now, Chef used an open core model with a <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[19],"tags":[25],"class_list":["post-14636","post","type-post","status-publish","format-standard","hentry","category-enterprise-software","tag-enterprise"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t