{"id":26681,"date":"2014-10-11T06:45:21","date_gmt":"2014-10-11T10:45:21","guid":{"rendered":"http:\/\/www.opensource.im\/?p=26681"},"modified":"2014-10-11T06:45:21","modified_gmt":"2014-10-11T10:45:21","slug":"whats-driving-open-source-2-0","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/open-source-software\/whats-driving-open-source-2-0.php","title":{"rendered":"What&#8217;s Driving Open Source 2.0?"},"content":{"rendered":"<p><p>    We're hearing more from vendors about how new features,    functionality, rewrites and releases are being driven by    customers -- by their direct experience using the software and    competing in their various industries.  <\/p>\n<p>    We're also hearing from customers and users, including the    enterprise market, that increasingly they are involved and thus    empowered in open source software communities, where they are    collaborating on code and road maps and collectively requiring    flexibility and openness, including that code and improvements    be contributed upstream.  <\/p>\n<p>    These perspectives on the sell-side and now the buy-side seem    to indicate we have arrived at Open Source 2.0.  <\/p>\n<p>    This newer open source software trend is a natural progression    and evolution of the movement away from developer-centric    communities toward communities that have had a higher regard    and respect for the user -- particularly in the enterprise,    where getting more participants to a project can translate to    dollars.  <\/p>\n<p>    Open Source 2.0 is characterized by a higher level of    involvement and participation by users and customers, given the    wide range of commercial vendors providing support. Today's    successful open source communities also are characterized by a    higher level of collaboration among users and customers,    whereby they pool resources and team up for a number of    reasons: to avoid vendor lock-in; to negotiate better terms or    prices; or to require that contributions be routed upstream.  <\/p>\n<p>    In turn, these users and customers are empowered to further    drive and steer open source projects and communities, as well    as to share their knowledge and experience with others, further    expanding open source ecosystems.  <\/p>\n<p>    There has been an evolution of user and customer thinking and    behavior with respect to open source cloud software, for    instance, as noted in 451    Research's recent report on the OpenStack cloud computing    project and market.  <\/p>\n<p>    Previously, some large-scale users were directly involved in    collaboration in terms of dealing with and resolving OpenStack    issues, particularly for enterprises and at large scale, as    noted in 451 Research's 00000 on OpenStack in 2013.  <\/p>\n<p>    However, that customer community, like the OpenStack code, also    has been evolving and maturing -- to the point where OpenStack    customers now are banding together on requirements for multiple    vendors and service-level expectations, as 451 Research's    recent report found. This customer side of the    community will continue to play an important role in    OpenStack's ongoing evolution.  <\/p>\n<p>    Another area where open source software has evolved is DevOps, a reference to more agile,    rapid and efficient methodologies, technologies and processes    in managing IT infrastructure, application development and    deployments.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Follow this link:<br \/>\n<a target=\"_blank\" href=\"http:\/\/www.technewsworld.com\/story\/81169.html?rss=1\/RK=0\/RS=2PMKJAmJi1fD2.kXb6ycUsx3IKo-\" title=\"What's Driving Open Source 2.0?\">What's Driving Open Source 2.0?<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> We're hearing more from vendors about how new features, functionality, rewrites and releases are being driven by customers -- by their direct experience using the software and competing in their various industries. We're also hearing from customers and users, including the enterprise market, that increasingly they are involved and thus empowered in open source software communities, where they are collaborating on code and road maps and collectively requiring flexibility and openness, including that code and improvements be contributed upstream. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-26681","post","type-post","status-publish","format-standard","hentry","category-open-source-software"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/26681"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=26681"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/26681\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=26681"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=26681"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=26681"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}