The document discusses the Apache Software Foundation (ASF) and open source software development. It provides an overview of the ASF, including that it is a non-profit organization founded in 1999 to support open source projects. It describes the ASF's structure and governance model, including that projects use a meritocratic and consensus-based process. It also outlines some of the core tenets of "The Apache Way", such as meritocracy, transparency, and community-driven development.
All Things Open 2017: Open Source LicensingJim Jagielski
The document discusses open source licensing and provides an overview of key concepts:
- It introduces Jim Jagielski and his background in open source software development.
- Licensing determines how software can be used, modified, and shared. Choosing the right license is important to avoid legal risks.
- Common open source licenses include permissive licenses like MIT, weak copyleft licenses like LGPL, and strong copyleft licenses like GPL. The license chosen depends on goals like commercial use or community development.
The document discusses The Apache Way, which are the governance principles and guiding tenets for how Apache Project Management Committees (PMCs) operate. It focuses on why understanding the origins and reasons behind The Apache Way is important. The Apache Way was developed to optimize for volunteer contributors, focus on community over code, and encourage long-term sustainable open source projects and software. Some key aspects of The Apache Way discussed are meritocracy, peer-based communities, consensus decision making, transparency, and collaborative development.
The History of The Apache Software FoundationJim Jagielski
- The Apache Software Foundation (ASF) was incorporated in 1999 to provide legal, financial and organizational support for open source software projects.
- It started with two projects - the Apache web server and Apache conferences - and has grown to over 150 projects with over 400 members.
- The ASF is a non-profit organization run by volunteers and provides infrastructure for collaborative, community-based development of open source software.
This document contains slides from a presentation given by Jim Jagielski at APACHECON North America on September 9-12, 2019. The presentation provides an overview and review of key features of Apache HTTP Server version 2.4, including improvements to configuration, new modules, enhancements for cloud/proxy usage, and performance increases. It highlights capabilities like mod_macro for virtual hosts, expression-based configuration with <IfDefine>, and health checking of backend servers. The presentation aims to dispel myths about Apache being outdated and argues it remains highly relevant due to its flexibility and performance.
The document provides an overview of the Apache Software Foundation (ASF) in 2011. It discusses that the ASF started with 21 members and 2 projects and has now grown to 390 members and over 95 top-level projects. It summarizes some of the accomplishments in 2011, including establishing several new top-level projects and approving the 2011-2012 budget. The document also discusses how the ASF has adapted over time to increased scale while maintaining its community-focused principles.
What's New and Newer in Apache httpd-24Jim Jagielski
Jim Jagielski presents an overview of new features and enhancements in Apache HTTP Server version 2.4, including configuration and runtime improvements, new modules and capabilities, cloud and proxy enhancements, performance increases, and support for HTTP/2. Key highlights include finer-grained configuration controls, new modules like mod_lua and mod_macro, improved proxy and load balancing functionality, better performance through optimizations and new MPMs like Event, and initial HTTP/2 support.
This document provides an overview of open source software and recommendations for companies adopting open source. It discusses how open source can accelerate projects and attract talent. It profiles companies like Adobe, Netflix, Oracle, Samsung, and Microsoft that contribute to open source despite not being commonly associated with it. The document outlines how to launch an open source project, including using an open source license, README, contribution guidelines, and code of conduct. It also discusses roles in open source projects and various open source business models. The recommendations encourage companies to publish independent components on GitHub, take releases from GitHub, and create developer websites to engage with the open source community.
All Things Open 2017: Open Source LicensingJim Jagielski
The document discusses open source licensing and provides an overview of key concepts:
- It introduces Jim Jagielski and his background in open source software development.
- Licensing determines how software can be used, modified, and shared. Choosing the right license is important to avoid legal risks.
- Common open source licenses include permissive licenses like MIT, weak copyleft licenses like LGPL, and strong copyleft licenses like GPL. The license chosen depends on goals like commercial use or community development.
The document discusses The Apache Way, which are the governance principles and guiding tenets for how Apache Project Management Committees (PMCs) operate. It focuses on why understanding the origins and reasons behind The Apache Way is important. The Apache Way was developed to optimize for volunteer contributors, focus on community over code, and encourage long-term sustainable open source projects and software. Some key aspects of The Apache Way discussed are meritocracy, peer-based communities, consensus decision making, transparency, and collaborative development.
The History of The Apache Software FoundationJim Jagielski
- The Apache Software Foundation (ASF) was incorporated in 1999 to provide legal, financial and organizational support for open source software projects.
- It started with two projects - the Apache web server and Apache conferences - and has grown to over 150 projects with over 400 members.
- The ASF is a non-profit organization run by volunteers and provides infrastructure for collaborative, community-based development of open source software.
This document contains slides from a presentation given by Jim Jagielski at APACHECON North America on September 9-12, 2019. The presentation provides an overview and review of key features of Apache HTTP Server version 2.4, including improvements to configuration, new modules, enhancements for cloud/proxy usage, and performance increases. It highlights capabilities like mod_macro for virtual hosts, expression-based configuration with <IfDefine>, and health checking of backend servers. The presentation aims to dispel myths about Apache being outdated and argues it remains highly relevant due to its flexibility and performance.
The document provides an overview of the Apache Software Foundation (ASF) in 2011. It discusses that the ASF started with 21 members and 2 projects and has now grown to 390 members and over 95 top-level projects. It summarizes some of the accomplishments in 2011, including establishing several new top-level projects and approving the 2011-2012 budget. The document also discusses how the ASF has adapted over time to increased scale while maintaining its community-focused principles.
What's New and Newer in Apache httpd-24Jim Jagielski
Jim Jagielski presents an overview of new features and enhancements in Apache HTTP Server version 2.4, including configuration and runtime improvements, new modules and capabilities, cloud and proxy enhancements, performance increases, and support for HTTP/2. Key highlights include finer-grained configuration controls, new modules like mod_lua and mod_macro, improved proxy and load balancing functionality, better performance through optimizations and new MPMs like Event, and initial HTTP/2 support.
This document provides an overview of open source software and recommendations for companies adopting open source. It discusses how open source can accelerate projects and attract talent. It profiles companies like Adobe, Netflix, Oracle, Samsung, and Microsoft that contribute to open source despite not being commonly associated with it. The document outlines how to launch an open source project, including using an open source license, README, contribution guidelines, and code of conduct. It also discusses roles in open source projects and various open source business models. The recommendations encourage companies to publish independent components on GitHub, take releases from GitHub, and create developer websites to engage with the open source community.
The document discusses Jim Jagielski's presentation on InnerSource and the Apache Way at the InnerSource Commons Summit. It provides an overview of what InnerSource is, why companies adopt it, and the basic principles of the Apache Way, including meritocracy, peer-based collaboration, consensus decision making, and individual participation. It also outlines the principles of InnerSource, such as culture, communication, transparency, collaboration, and community.
The topics of Free Software/Open Source licensing and governance can be complex and confusing. This presentation provides for an easy and clear description of the hows and whys of both. Presented at the All Things Open 2016 Conference in Raleigh, NC
All Things Open 2017: Foundations of Inner SourceJim Jagielski
The document discusses the principles of InnerSource, which is applying open source development principles within enterprises. It outlines the principles of InnerSource as culture, communication, transparency, collaboration, community, and meritocracy. It describes the Apache Way, which focuses on meritocracy, transparency, and community. The Apache Way originated from focusing on volunteer contributors and community.
Jim Jagielski gave a presentation about open source licenses. He is the co-founder and director of the Apache Software Foundation and has worked on many open source projects. He explained that licenses determine how software can be used, modified, and shared. The main types of open source licenses are permissive, weak copyleft, and strong copyleft licenses. Jagielski emphasized that the license chosen should align with the project's goals and that changing licenses later can be difficult.
InnerSource is applying open source principles to internal enterprise development by running projects as if they were open source. The document discusses why InnerSource through increased collaboration, transparency, and community can help drive innovation, reduce costs, and attract talent. It outlines principles like culture, communication, transparency, collaboration, community, and meritocracy that are important for successful InnerSourcing based on lessons from open source projects like Apache.
Jim Jagielski, Capital One/Apache Software Foundation: Innersourcing 101.
INNERSOURCING 101
Initially, the success of the Open Source movement was corporate acceptance, embracement, and then dependence on Open Source software. Recently, Enterprise IT, and especially Fintech, have deepened their alliance with Open Source by leveraging not only the software, but the actual software development methodologies practiced by successful Open Source projects. These “lessons learned” form the basis of Inner Source. In this session, Jim, one of the core architects of “The Apache Way”, which is one of the prime guidelines for much of Inner Source, will explain the history of open source development and why it excels at creating healthy project communities and driving innovation. With that as a foundation, Jim will describe and explain the principles and techniques of Inner Source being used in IT today.
InnerSource 101 for FinTech and FinServJim Jagielski
An overview of the topic, benefits, techniques and challenges of implementing an InnerSource policy in the FinTech/FinServ arena. From my talk at the Open Source Strategy Summit 2017 in NYC.
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.
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.
InnerSource: Enterprise Lessons from Open SourceJim Jagielski
Jim Jagielski discusses the concept of "Inner Sourcing", which involves applying principles and techniques from open source software development within corporate IT organizations. Some key principles discussed include transparency, collaboration, community, and meritocracy. Techniques for implementing Inner Sourcing include using tools that enable communication, collaboration and open development. Challenges that must be overcome include resistance to change, properly rewarding merit, maintaining business focus and accountability. Overall, Inner Sourcing aims to improve efficiency, speed, costs and talent through more open and collaborative development practices.
The Hop project entered Apache Software Foundation as an Incubator project in 2020, and Julian Hyde, one of their mentors, gave this presentation to educate the initial committers on the Apache Way and what to expect during the Incubation process.
The talk was given by Julian Hyde on October 1st, 2020, with the original title "Apache Incubation - What's it all about?"
The Open Source Geospatial Foundation does much more than hold FOSS4G each year.
This talk will look into what makes OSGeo a software foundation. What software foundations have to offer members, software projects and developers.
This talk is structured around the “incubation” process by which new software projects join the OSGeo.
If you are new to open source take this is a great chance to see how OSGeo evaluates software projects and how these checks protect you!
For managers it is especially important to understand the risks associated with the use of open source. Understand what assurances OSGeo incubation offers, how to double check the results, and what factors are left for your own risk assessment.
If you are a developer considering getting involved in OSGeo this is great talk to learn what is involved, how much work it will be, and how you can start!
Come see what makes OSGeo more than a user group!
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 distribute the software. It discusses the main open source licenses like permissive, weak copyleft, and strong copyleft licenses. It also covers the different types of open source community governance models like walled gardens, benevolent dictators, and meritocracies. Finally, it provides tips for building open source communities through email lists, consensus, positivity, and sharing.
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 Apache Way: A Proven Way Toward SuccessEvans Ye
With innumerous successful Apache projects that dominate the big data world, the working model of Apache communities clearly deserved a study. In this talk, I'll walk you through how Apache communities and the Apache Software Foundation work generally. The whole thing behinds it is so called "The Apache Way".
For audience whose an engineer, I'll share with you why you should be part of the Apache family, how to do it, and what you can get from it. Moreover, I'll cover this with some actionable tips, and closing up with some career advices. For those being managers or at CXO level, I'll talk about some aspects on building engineering culture which can alternately pace your team and business toward success.
The document discusses Open Source Program Offices (OSPOs), which are centers of excellence within organizations responsible for the strategic engagement with open source. The key responsibilities of an OSPO include maintaining license compliance, defining the open source strategy, communicating it, overseeing execution, facilitating open source use, engaging with communities, and fostering an open source culture. Having an OSPO becomes more important as organizations depend more on open source. An OSPO provides benefits like better management of security risks and helps organizations of all sizes. Challenges include culture, processes, tools, and budget. Success is defined by each organization.
The document discusses Jim Jagielski's presentation on InnerSource and the Apache Way at the InnerSource Commons Summit. It provides an overview of what InnerSource is, why companies adopt it, and the basic principles of the Apache Way, including meritocracy, peer-based collaboration, consensus decision making, and individual participation. It also outlines the principles of InnerSource, such as culture, communication, transparency, collaboration, and community.
The topics of Free Software/Open Source licensing and governance can be complex and confusing. This presentation provides for an easy and clear description of the hows and whys of both. Presented at the All Things Open 2016 Conference in Raleigh, NC
All Things Open 2017: Foundations of Inner SourceJim Jagielski
The document discusses the principles of InnerSource, which is applying open source development principles within enterprises. It outlines the principles of InnerSource as culture, communication, transparency, collaboration, community, and meritocracy. It describes the Apache Way, which focuses on meritocracy, transparency, and community. The Apache Way originated from focusing on volunteer contributors and community.
Jim Jagielski gave a presentation about open source licenses. He is the co-founder and director of the Apache Software Foundation and has worked on many open source projects. He explained that licenses determine how software can be used, modified, and shared. The main types of open source licenses are permissive, weak copyleft, and strong copyleft licenses. Jagielski emphasized that the license chosen should align with the project's goals and that changing licenses later can be difficult.
InnerSource is applying open source principles to internal enterprise development by running projects as if they were open source. The document discusses why InnerSource through increased collaboration, transparency, and community can help drive innovation, reduce costs, and attract talent. It outlines principles like culture, communication, transparency, collaboration, community, and meritocracy that are important for successful InnerSourcing based on lessons from open source projects like Apache.
Jim Jagielski, Capital One/Apache Software Foundation: Innersourcing 101.
INNERSOURCING 101
Initially, the success of the Open Source movement was corporate acceptance, embracement, and then dependence on Open Source software. Recently, Enterprise IT, and especially Fintech, have deepened their alliance with Open Source by leveraging not only the software, but the actual software development methodologies practiced by successful Open Source projects. These “lessons learned” form the basis of Inner Source. In this session, Jim, one of the core architects of “The Apache Way”, which is one of the prime guidelines for much of Inner Source, will explain the history of open source development and why it excels at creating healthy project communities and driving innovation. With that as a foundation, Jim will describe and explain the principles and techniques of Inner Source being used in IT today.
InnerSource 101 for FinTech and FinServJim Jagielski
An overview of the topic, benefits, techniques and challenges of implementing an InnerSource policy in the FinTech/FinServ arena. From my talk at the Open Source Strategy Summit 2017 in NYC.
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.
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.
InnerSource: Enterprise Lessons from Open SourceJim Jagielski
Jim Jagielski discusses the concept of "Inner Sourcing", which involves applying principles and techniques from open source software development within corporate IT organizations. Some key principles discussed include transparency, collaboration, community, and meritocracy. Techniques for implementing Inner Sourcing include using tools that enable communication, collaboration and open development. Challenges that must be overcome include resistance to change, properly rewarding merit, maintaining business focus and accountability. Overall, Inner Sourcing aims to improve efficiency, speed, costs and talent through more open and collaborative development practices.
The Hop project entered Apache Software Foundation as an Incubator project in 2020, and Julian Hyde, one of their mentors, gave this presentation to educate the initial committers on the Apache Way and what to expect during the Incubation process.
The talk was given by Julian Hyde on October 1st, 2020, with the original title "Apache Incubation - What's it all about?"
The Open Source Geospatial Foundation does much more than hold FOSS4G each year.
This talk will look into what makes OSGeo a software foundation. What software foundations have to offer members, software projects and developers.
This talk is structured around the “incubation” process by which new software projects join the OSGeo.
If you are new to open source take this is a great chance to see how OSGeo evaluates software projects and how these checks protect you!
For managers it is especially important to understand the risks associated with the use of open source. Understand what assurances OSGeo incubation offers, how to double check the results, and what factors are left for your own risk assessment.
If you are a developer considering getting involved in OSGeo this is great talk to learn what is involved, how much work it will be, and how you can start!
Come see what makes OSGeo more than a user group!
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 distribute the software. It discusses the main open source licenses like permissive, weak copyleft, and strong copyleft licenses. It also covers the different types of open source community governance models like walled gardens, benevolent dictators, and meritocracies. Finally, it provides tips for building open source communities through email lists, consensus, positivity, and sharing.
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 Apache Way: A Proven Way Toward SuccessEvans Ye
With innumerous successful Apache projects that dominate the big data world, the working model of Apache communities clearly deserved a study. In this talk, I'll walk you through how Apache communities and the Apache Software Foundation work generally. The whole thing behinds it is so called "The Apache Way".
For audience whose an engineer, I'll share with you why you should be part of the Apache family, how to do it, and what you can get from it. Moreover, I'll cover this with some actionable tips, and closing up with some career advices. For those being managers or at CXO level, I'll talk about some aspects on building engineering culture which can alternately pace your team and business toward success.
Similar to All Things Open 2017: The Apache Software Foundation 101 (20)
The document discusses Open Source Program Offices (OSPOs), which are centers of excellence within organizations responsible for the strategic engagement with open source. The key responsibilities of an OSPO include maintaining license compliance, defining the open source strategy, communicating it, overseeing execution, facilitating open source use, engaging with communities, and fostering an open source culture. Having an OSPO becomes more important as organizations depend more on open source. An OSPO provides benefits like better management of security risks and helps organizations of all sizes. Challenges include culture, processes, tools, and budget. Success is defined by each organization.
The document discusses Apache httpd v2.4 and its use as a reverse proxy. Key points include: Apache httpd v2.4 has improvements that make it suitable for cloud environments and dynamic configurations; it supports load balancing, clustering, caching, and offloading SSL to improve performance and high availability when used as a reverse proxy; directives like ProxyPass and ProxyPassReverse are used to configure proxying and load balancing using modules like mod_proxy and mod_proxy_balancer.
Jim Jagielski discusses the Apache HTTPD v2.4 reverse proxy capabilities. Key points include:
1) Apache HTTPD v2.4 includes improvements that make it suitable for cloud environments and high performance as a reverse proxy, including support for asynchronous I/O and additional load balancing mechanisms.
2) As a reverse proxy, Apache HTTPD can provide security, load balancing, caching, and high availability for backend servers located behind the proxy.
3) Apache HTTPD v2.4's reverse proxy functionality includes support for additional protocols, load balancing algorithms, dynamic configuration, and HTTP/2.
ApacheCon 2017: What's new in httpd 2.4Jim Jagielski
What new is Apache httpd 2.4, both in upgrading from httpd 2.2 and well as new features in this latest version. Performance, HTTP/2, reverse proxy and cache!
Apache httpd 2.4 Reverse Proxy: The Hidden GemJim Jagielski
The document discusses the reverse proxy capabilities of Apache HTTP Server (httpd) version 2.4. It notes that httpd is commonly used as a front-end reverse proxy and that its proxy capabilities have improved in version 2.4, including support for load balancing, connection pooling, and dynamic configuration. The document provides examples of configuring reverse proxying, load balancing clusters, and other advanced proxy features in httpd.
The document reports on the growth of the Apache Foundation from November 2015 to November 2016, including a growth in project committees and projects under management. It discusses why the ASF continues to grow, noting that it is defined by the people who do the work on the projects rather than central governance. The ASF operates through consensus rather than having leaders, and works for the public good. It encourages contributions of resources like people rather than cash to support projects.
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.
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.
Slides from my Inner Source 101 presentation at Great Wide Open 2016. Using the lessons learned from Open Source to enhance Enterprise IT via inner-sourcing
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.
Honeypots Unveiled: Proactive Defense Tactics for Cyber Security, Phoenix Sum...APNIC
Adli Wahid, Senior Internet Security Specialist at APNIC, delivered a presentation titled 'Honeypots Unveiled: Proactive Defense Tactics for Cyber Security' at the Phoenix Summit held in Dhaka, Bangladesh from 23 to 24 May 2024.
Securing BGP: Operational Strategies and Best Practices for Network Defenders...APNIC
Md. Zobair Khan,
Network Analyst and Technical Trainer at APNIC, presented 'Securing BGP: Operational Strategies and Best Practices for Network Defenders' at the Phoenix Summit held in Dhaka, Bangladesh from 23 to 24 May 2024.
HijackLoader Evolution: Interactive Process HollowingDonato Onofri
CrowdStrike researchers have identified a HijackLoader (aka IDAT Loader) sample that employs sophisticated evasion techniques to enhance the complexity of the threat. HijackLoader, an increasingly popular tool among adversaries for deploying additional payloads and tooling, continues to evolve as its developers experiment and enhance its capabilities.
In their analysis of a recent HijackLoader sample, CrowdStrike researchers discovered new techniques designed to increase the defense evasion capabilities of the loader. The malware developer used a standard process hollowing technique coupled with an additional trigger that was activated by the parent process writing to a pipe. This new approach, called "Interactive Process Hollowing", has the potential to make defense evasion stealthier.
All Things Open 2017: The Apache Software Foundation 101
1. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
APACHE: 101
Jim Jagielski || @jimjag
CODE, COMMUNITY AND OPEN SOURCE
2. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
AGENDA
• Introduction
• Overview of the ASF
• The What and Why of “Open Source”
• The Lessons Learned by the ASF - The Apache Way
3. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
ABOUT ME
• Apache Software Foundation
• Co-founder, Director, Vice Chairman, Member and Developer
• Director
• Outercurve, MARSEC-XL, OSSI, OSI (ex)…
• Developer
• Much FOSS projects
• Sr. Director: Tech Fellows: Capital One
4. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
THE ASF
• ASF == The Apache Software Foundation
• Before the ASF there was “The Apache Group”
• The ASF was incorporated in 1999
5. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
THE ASF
• Non-profit corporation founded in 1999
• 501( c )3 public charity
• Volunteer organization (The ASF doesn’t pay anyone to
work on Apache projects)
• Virtual world-wide organization - Membership of Individuals
• Exists to provide the organizational, legal, and financial
support for various OSS projects - let the developers
develop
6. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
STRUCTURE OF THE ASF -
LEGAL
• Member-based corporation - individuals only
• Members nominate and elect new members
• Members elect a board - 9 seats
• Semi-annual meetings via IRC
• Each PMC has a Chair - eyes and ears of the board
(oversight only)
7. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
ASF “ORG CHART”
Development Administrative
Users
Patchers/Buggers
Contributors
Committers
PMC Members
Members
Officers
Board
~400
9
~160
~4500
~2000
Technical Oversight Organizational Oversight
PMCs
(TLPs)
~150
Elects
ReportsAppoints
Creates
&
Updates
8. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
ISSUES WITH DUAL
STACKS
• Despite clear differentiation, sometimes there are leaks
• eg: PMC chair seen as “lead” developer
• Sometimes officers are assumed to have too much power if
they venture into development issues
• “hats”
9. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
THE ASF’S MISSION
• Provide open source software to the public free of charge
• Provide a foundation for open, collaborative software
development projects by supplying hardware,
communication, and business infrastructure
• Create an independent legal entity to which companies and
individuals can donate resources and be assured that those
resources will be used for the public benefit
10. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
THE ASF’S MISSION
•Provide a means for individual volunteers to be sheltered from
legal suits directed at the Foundation’s projects
•Protect the ‘Apache’ brand, as applied to its software products,
from being abused by other organizations
•Provide legal and technical infrastructure for open source
software development and to perform appropriate oversight of
such software
11. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
VISION STATEMENT
• The Apache Software Foundation provides support for the
Apache community of open-source software projects. The
Apache projects are characterized by a collaborative,
consensus based development process, an open and
pragmatic software license, and a desire to create high
quality software that leads the way in its field. We consider
ourselves not simply a group of projects sharing a server,
but rather a community of developers and users.
12. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
VISION STATEMENT,
TAKE 2
• Community created code
• Our code should be exceptional
13. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
WHY OPEN SOURCE?
• Access to the source code
• Avoid vendor lock-in (or worse!)
• Much better software
• Better security record (more eyes)
• Much more nimble development - frequent releases
• Direct user input
14. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
THE DRAW OF OPEN
SOURCE
• Having a real impact in the development and direction of IT
• Personal satisfaction: I wrote that!
• Sense of membership in a community
• Sense of accomplishment - very quick turnaround times
• Developers and engineers love to tinker - huge opportunity
to do so
15. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
OPEN SOURCE FUD
• No quality or quality control
• Prevents or slows development
• Have to “give it away for free”
• No real innovation
16. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
THE APACHE WAY
• Although the term is deprecated, “The Apache Way”
relates to how the ASF (and its projects) work and operate
• Basically, the least common denominators on how PMCs
operate
17. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
WHY FOCUS ON ASF ?
http://webmink.com/essays/#OBR
http://www.zdnet.com/blog/open-source/
oracle-gives-openoffice-to-apache/9035
18. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
CORE TENETS
• Meritocracy
• Transparency
• open
• public
• Community
• healthy
• active
19. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
BASIC MEMES
• Meritocracy
• Peer-based
• Consensus decision making
• Collaborative development
• Responsible oversight
• Individual Participation
20. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
MERITOCRACY
• “Govern by Merit”
• Merit is based on what you do
• Merit never expires
• Those with more merit, get more responsibility
• Provides incentive to Do More
• It’s NOT a dirty word
• aka “do-acracy”
21. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
PEER-BASED
• Developers represent themselves - individuals
• Mutual trust and respect
• All votes hold the same weight (no BDFL)
• Community created code
• Healthy communities create healthy code
• Poisonous communities don’t
• Feel as part of a community
22. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
WHY COMMUNITY -> CODE
• Since we are all volunteers, people’s time and interests
change
• A healthy community is “warm and inviting” and encourages
a continued influx of developers
• Poisonous people/communities turn people off, and the
project will die
• Diversity ensures survival
• End result - better code, long-term code
23. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
CONSENSUS DECISION
MAKING
• Key is the idea of voting
• +1 - yes
• +0 - no real comment
• -1 - veto
• Sometimes you’ll also see stuff like -0, -0.5, etc...
24. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
VOTING
• The main intent is to gauge developer acceptance
• Vetos must be justifiable and have sound technical merit
• If valid, Vetos cannot be overruled
• Vetos are very rare
25. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
COLLABORATIVE
DEVELOPMENT
• Code is developed by the community
• Voting ensures at least 3 active developers
• Development done online and on-list
• If it didn’t happen on-list, it didn’t happen
26. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
COLLABORATIVE
DEVELOPMENT
• Mailing lists are the preferred method
• Archived
• Asynchronous
• Available to anyone - public list
27. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
COLLABORATIVE
DEVELOPMENT
• Other methods are OK, if not primary
• Wikis
• IRC
• F2F
• Always bring back to the list
28. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
THE APACHE INCUBATOR
• Entry point for all new projects and codebases
• Indoctrinates the Apache Way to the podling
• Ensures and tracks IP
29. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
CONTRIBUTOR LICENSE
AGREEMENT
• aka: iCLA (for individual)
• Required of all committers
• Guarantees:
• The person has the authority to commit the code
• That the ASF can relicense the code
• Does NOT assign copyright
30. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
DEVELOPMENT
• The ASF never pays for development of projects
• Some contributors are corporate sponsored, some aren’t
but as far as the ASF is concerned it makes no difference!
• Diversity == Independence
• git-like mega merges are counter-productive
• Code is one form of contributing, not the only form.
31. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
THE ASF IS VITAL
• Foundations (independent) are critical for widespread
adoption of s/w
• ASF: totally vendor neutral - Sponsors don’t control/
manage/direct the foundation nor projects
• “There are other ways of doing things, what we’ve been
doing has simply be proven to be one of the best.”
32. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
CURRENT STATUS
33. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
CURRENT STATUS
34. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
CURRENT STATUS
35. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
CURRENT STATUS
36. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag
@jimjag
THAT’S IT
• Support the ASF!
• Any questions?
• @jimjag
• www.slideshare.net/jimjag
• www.linkedin.com/in/jimjag/