This document provides an overview of open source software. It defines open source as software that is freely available with its source code and allows others to use, modify, and share the software. It discusses the different types of open source licenses, including permissive, weak copyleft, and strong copyleft licenses. It also outlines different open source governance models like the walled garden, benevolent dictator for life, and meritocracy models. Finally, it provides tips for building open source communities through email lists, consensus driving, inclusive behavior, and having a friendly, sharing atmosphere.
The slides from my Apache Way talk at ApacheCon NA 2016. All about the Apache Way, lessons learned from the ASF about code, community and collaboration.
The document discusses open source software and the Apache Software Foundation. It notes that open source is crucial for business and that Drupal is part of its success. It provides background on Jim Jagielski and his role in Apache. It outlines reasons why open source matters for hackers, businesses, and users, including innovation, cost savings, and avoiding vendor lock-in. It acknowledges risks like a desire for control but argues communities are important to resist forks and share code through collaboration.
Inner Source: Enterprise Lessons from the Open Source Community.Jim Jagielski
Slides from my Inner Sourcing talk from ApacheCon NA 2016. Inner Sourcing is using the methods and techniques of successful open source projects inside Enterprise IT.
The document summarizes the key new features and enhancements in Apache HTTPD version 2.4, including improvements to configuration, new modules, cloud/proxy enhancements, and performance increases. Some highlights include finer-grained configuration and logging controls, new modules like mod_lua and mod_macro, enhanced proxy and load balancing capabilities, and continued performance optimizations. Benchmark results show Apache HTTPD competing well and sometimes outperforming Nginx in various concurrency and throughput tests.
This document provides an overview of open source software. It defines open source as software that is freely available with its source code and allows others to use, modify, and share the software. It discusses the different types of open source licenses, including permissive, weak copyleft, and strong copyleft licenses. It also outlines different open source governance models like the walled garden, benevolent dictator for life, and meritocracy models. Finally, it provides tips for building open source communities through email lists, consensus driving, inclusive behavior, and having a friendly, sharing atmosphere.
The slides from my Apache Way talk at ApacheCon NA 2016. All about the Apache Way, lessons learned from the ASF about code, community and collaboration.
The document discusses open source software and the Apache Software Foundation. It notes that open source is crucial for business and that Drupal is part of its success. It provides background on Jim Jagielski and his role in Apache. It outlines reasons why open source matters for hackers, businesses, and users, including innovation, cost savings, and avoiding vendor lock-in. It acknowledges risks like a desire for control but argues communities are important to resist forks and share code through collaboration.
Inner Source: Enterprise Lessons from the Open Source Community.Jim Jagielski
Slides from my Inner Sourcing talk from ApacheCon NA 2016. Inner Sourcing is using the methods and techniques of successful open source projects inside Enterprise IT.
The document summarizes the key new features and enhancements in Apache HTTPD version 2.4, including improvements to configuration, new modules, cloud/proxy enhancements, and performance increases. Some highlights include finer-grained configuration and logging controls, new modules like mod_lua and mod_macro, enhanced proxy and load balancing capabilities, and continued performance optimizations. Benchmark results show Apache HTTPD competing well and sometimes outperforming Nginx in various concurrency and throughput tests.
The document provides contact information for a presenter including their name, title, location of city and state, email address, phone number, and URL.
From the Linux Foundation Collaboration Summit 2016, my slides from the Why Community Matters presentation.
Why does community matter in open source and in open source foundations: because, frankly, there is nothing else.
This document discusses different information formats and their characteristics. It begins by defining what is meant by "format" in relation to information. It then outlines some common formats including news, magazines, academic journals, books, and reference sources. For each format, it describes qualities, when they are good sources to use, and when to look elsewhere. It also discusses how digital formats replicate physical formats online and the evolution of formats on the web.
This document provides an overview of advanced load balancing capabilities in Apache HTTP Server 2.2 using the mod_proxy module. Key points include:
- Mod_proxy allows Apache to function as a reverse proxy or load balancer for backend servers.
- New in 2.2 are improvements like large file support, graceful stop, mod_dbd integration, and better debugging.
- Load balancing is implemented through balancer providers that can be customized. Default providers balance by requests, traffic, or server busyness.
- Features like connection pooling, sticky sessions, failover clusters, and an embedded admin interface provide robust load balancing functionality.
The document discusses open source licensing, governance, and community. It notes that open source provides benefits to hackers/developers in having impact and satisfaction, to companies in saving costs and flexibility, and to users in access and security. Open source relies on licenses that allow use, modification, and sharing of content with credit given. Governance involves merit-based contributions and consensus-building through mailing lists. Successful communities avoid toxic members and focus on inclusion.
Apache httpd v2.4 is well-suited for cloud environments due to improvements that increase performance, flexibility, and dynamic configuration capabilities. It has been enhanced as a reverse proxy with load balancing and support for additional protocols. Benchmark tests show that for transaction speed, the prefork MPM performs best, though other MPMs are on par for concurrency. Apache remains a robust and customizable web server option.
Presented at the Open Repositories Conference, this presentation describes the Lessons Learned in the Open Source Movement that can be used outside of the traditional IT environment.
This document discusses open source projects and governance. It defines open source as software that is licensed under an OSI approved license and developed openly and collaboratively, usually via mailing lists. The document outlines the structure of the Apache Software Foundation, how it oversees open source projects through Project Management Committees (PMCs), and the principles of "The Apache Way" including meritocracy, consensus-based decision making, and collaborative development.
The document provides contact information for a presenter including their name, title, location of city and state, email address, phone number, and URL.
From the Linux Foundation Collaboration Summit 2016, my slides from the Why Community Matters presentation.
Why does community matter in open source and in open source foundations: because, frankly, there is nothing else.
This document discusses different information formats and their characteristics. It begins by defining what is meant by "format" in relation to information. It then outlines some common formats including news, magazines, academic journals, books, and reference sources. For each format, it describes qualities, when they are good sources to use, and when to look elsewhere. It also discusses how digital formats replicate physical formats online and the evolution of formats on the web.
This document provides an overview of advanced load balancing capabilities in Apache HTTP Server 2.2 using the mod_proxy module. Key points include:
- Mod_proxy allows Apache to function as a reverse proxy or load balancer for backend servers.
- New in 2.2 are improvements like large file support, graceful stop, mod_dbd integration, and better debugging.
- Load balancing is implemented through balancer providers that can be customized. Default providers balance by requests, traffic, or server busyness.
- Features like connection pooling, sticky sessions, failover clusters, and an embedded admin interface provide robust load balancing functionality.
The document discusses open source licensing, governance, and community. It notes that open source provides benefits to hackers/developers in having impact and satisfaction, to companies in saving costs and flexibility, and to users in access and security. Open source relies on licenses that allow use, modification, and sharing of content with credit given. Governance involves merit-based contributions and consensus-building through mailing lists. Successful communities avoid toxic members and focus on inclusion.
Apache httpd v2.4 is well-suited for cloud environments due to improvements that increase performance, flexibility, and dynamic configuration capabilities. It has been enhanced as a reverse proxy with load balancing and support for additional protocols. Benchmark tests show that for transaction speed, the prefork MPM performs best, though other MPMs are on par for concurrency. Apache remains a robust and customizable web server option.
Presented at the Open Repositories Conference, this presentation describes the Lessons Learned in the Open Source Movement that can be used outside of the traditional IT environment.
This document discusses open source projects and governance. It defines open source as software that is licensed under an OSI approved license and developed openly and collaboratively, usually via mailing lists. The document outlines the structure of the Apache Software Foundation, how it oversees open source projects through Project Management Committees (PMCs), and the principles of "The Apache Way" including meritocracy, consensus-based decision making, and collaborative development.