- 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.
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.
All Things Open 2017: The Apache Software Foundation 101Jim Jagielski
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.
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.
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!
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.
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 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.
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.
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.
All Things Open 2017: The Apache Software Foundation 101Jim Jagielski
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.
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.
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!
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.
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 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.
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. 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.
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.
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 and introduction to Apache Usergrid, an open source backend as a service (BaaS) platform. It discusses why developers should use Usergrid to avoid building their own servers, and focuses instead on building their apps. Usergrid provides a complete BaaS with a REST API, management portal, and client SDKs. It offers core services like data storage, user management, authentication and more. The document also provides an overview of the Usergrid REST API and explores building a sample check-in application using the Usergrid JavaScript SDK.
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.
JMS, WebSocket, and the Internet of Things - Controlling Physical Devices on ...Peter Moskovits
JMS is widely used behind enterprise firewalls to build loosely coupled distributed systems. This session discusses how JMS can be extended and applied to an always connected Web and mobile environment to provide interactivity and collaboration by controlling physical objects, such as model cars, remotely. You’ll learn how you can connect an HTML5 client running on the Web browser of a smartphone and Java running on a Raspberry Pi, a credit-card-size computer, in real time, using open industry-standard Web technologies. The presentation features several live demonstrations of the concepts discussed throughout the session.
Presentation given by David Witherspoon and Prashant Khanal on Sep 25, 2013 at JavaOne in San Francisco.
An introduction to Google's PRPL pattern that can be used to implement Progressive Web Applications. Delivered at MWLUG 2017 in Alexandria, VA by Keith Strickland.
The document is a presentation about infrastructure automation for the cloud. It discusses how infrastructure is changing with the rise of cloud computing and how this necessitates new approaches like treating infrastructure as code. It advocates for techniques like configuration management, version controlling all components, building from source code, enabling one step deployments, continuous monitoring, and integrating development and operations teams through a DevOps culture and shared processes. The overall goal is to enable agile infrastructure that allows for business agility and a faster time to market.
HTML5 WebSocket for the Real-Time Weband the Internet of ThingsPeter Moskovits
Abstract: In his talk Peter gives a brief introduction to WebSocket and discusses how real-time Web communications technologies can be applied to an always connected Web and mobile world. Then, he walks you through how to provide interactivity and collaboration by controlling physical objects remotely. The presentation features several live demonstrations of the concepts discussed throughout the session.
The document discusses ways to speed up WordPress sites to improve user experience and reduce environmental impact. It recommends optimizing sites by reducing HTTP requests, compressing files, leveraging caching, minimizing files, optimizing images, and using CSS sprites. Implementing these techniques can significantly improve site performance and speed.
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.
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
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 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?"
But we're already open source! Why would I want to bring my code to Apache?gagravarr
From ApacheCon Europe 2015 in Budapest
So, your business has already opened sourced some of its code? Great! Or you're thinking about it? That's fine! But now, someone's asking you about giving it to these Apache people? What's up with that, and why isn't just being open source enough?
In this talk, we'll look at several real world examples of where companies have chosen to contribute their existing open source code to the Apache Software Foundation. We'll see the advantages they got from it, the problems they faced along the way, why they did it, and how it helped their business. We'll also look briefly at where it may not be the right fit.
Wondering about how to take your business's open source involvement to the next level, and if contributing to projects at the Apache Software Foundation will deliver RoI, then this is the talk for you!
How and Why you can and should Participate in Open Source Projects (AMIS, Sof...Lucas Jellema
For a long time I have been reluctant to actively contribute to an open source project. I thought it would be rather complicated and demanding – and that I didn't have the knowledge or skills for it or at the very least that they (the project team) weren't waiting for me.
In December 2021, I decided to have a serious input into the Dapr.io project – and now finally to determine how it works and whether it is really that complicated. In this session I want to tell you about my experiences. How Fork, Clone, Branch, Push (and PR) is the rhythm of contributing to an open source project and how you do that (these are all Git actions against GitHub repositories). How to learn how such a project functions and how to connect to it; which tools are needed, which communication channels are used. I tell how the standards of the project – largely automatically enforced – help me to become a better software engineer, with an eye for readability and testability of the code.
How the review process is quite exciting once you have offered your contribution. And how the final "merge to master" of my contribution and then the actual release (Dapr 1.6 contains my first contribution) are nice milestones.
I hope to motivate participants in this session to also take the step yourself and contribute to an open source project in the form of issues or samples, documentation or code. It's valuable to the community and the specific project and I think it's definitely a valuable experience for the "contributer". I looked up to it and now that I've done it gives me confidence – and it tastes like more (I could still use some help with the work on Dapr.io, by the way).
OSMC 2018 | Integrating Check_MK agent into Thruk – Windows monitoring made e...NETWAYS
Did you ever get a headache configuring Windows monitoring using NSClient++? We did, too! While using the Check_MK Windows agent we were impressed by the plethora of checks that had already been implemented there. With the goal in our minds to create a fast and easy-to-use Windows monitoring solution, we set out to integrate the Check_MK agent into Thruk and tap into it’s capabilities. Combining them even allows for fully automatic service discovery!
LTI Advantage: The Next Big Thing in LMS IntegrationCharles Severance
LTI Advantage is the next major integration standard for learning management systems (LMS). It uses new technologies like JSON Web Tokens (JWTs) and public/private key infrastructure (PKI) to securely launch tools and access user data and grading services. The presentation provides an overview of the LTI Advantage specification and code samples for implementing launches, user authorization, and accessing LMS services using libraries available in Java. While adoption of LTI Advantage promises tighter integration between LMSs and external tools, there are also transition challenges as vendors continue to evolve their systems.
We all love open source software and open culture, and of course we all want to contribute to and leverage the power of open source in our work. However when it comes to working in a startup, openness is often sacrificed to give way to work efficiency and business logic. In this talk I will talk about some of my experience(and failures) to be open source, and how our company is trying to be open by default without too much efficiency overhead.
https://hkoscon.org/2020/topics/open-default-trying-run-startup-open-source-culture-mind
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.
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.
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 and introduction to Apache Usergrid, an open source backend as a service (BaaS) platform. It discusses why developers should use Usergrid to avoid building their own servers, and focuses instead on building their apps. Usergrid provides a complete BaaS with a REST API, management portal, and client SDKs. It offers core services like data storage, user management, authentication and more. The document also provides an overview of the Usergrid REST API and explores building a sample check-in application using the Usergrid JavaScript SDK.
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.
JMS, WebSocket, and the Internet of Things - Controlling Physical Devices on ...Peter Moskovits
JMS is widely used behind enterprise firewalls to build loosely coupled distributed systems. This session discusses how JMS can be extended and applied to an always connected Web and mobile environment to provide interactivity and collaboration by controlling physical objects, such as model cars, remotely. You’ll learn how you can connect an HTML5 client running on the Web browser of a smartphone and Java running on a Raspberry Pi, a credit-card-size computer, in real time, using open industry-standard Web technologies. The presentation features several live demonstrations of the concepts discussed throughout the session.
Presentation given by David Witherspoon and Prashant Khanal on Sep 25, 2013 at JavaOne in San Francisco.
An introduction to Google's PRPL pattern that can be used to implement Progressive Web Applications. Delivered at MWLUG 2017 in Alexandria, VA by Keith Strickland.
The document is a presentation about infrastructure automation for the cloud. It discusses how infrastructure is changing with the rise of cloud computing and how this necessitates new approaches like treating infrastructure as code. It advocates for techniques like configuration management, version controlling all components, building from source code, enabling one step deployments, continuous monitoring, and integrating development and operations teams through a DevOps culture and shared processes. The overall goal is to enable agile infrastructure that allows for business agility and a faster time to market.
HTML5 WebSocket for the Real-Time Weband the Internet of ThingsPeter Moskovits
Abstract: In his talk Peter gives a brief introduction to WebSocket and discusses how real-time Web communications technologies can be applied to an always connected Web and mobile world. Then, he walks you through how to provide interactivity and collaboration by controlling physical objects remotely. The presentation features several live demonstrations of the concepts discussed throughout the session.
The document discusses ways to speed up WordPress sites to improve user experience and reduce environmental impact. It recommends optimizing sites by reducing HTTP requests, compressing files, leveraging caching, minimizing files, optimizing images, and using CSS sprites. Implementing these techniques can significantly improve site performance and speed.
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.
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
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 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?"
But we're already open source! Why would I want to bring my code to Apache?gagravarr
From ApacheCon Europe 2015 in Budapest
So, your business has already opened sourced some of its code? Great! Or you're thinking about it? That's fine! But now, someone's asking you about giving it to these Apache people? What's up with that, and why isn't just being open source enough?
In this talk, we'll look at several real world examples of where companies have chosen to contribute their existing open source code to the Apache Software Foundation. We'll see the advantages they got from it, the problems they faced along the way, why they did it, and how it helped their business. We'll also look briefly at where it may not be the right fit.
Wondering about how to take your business's open source involvement to the next level, and if contributing to projects at the Apache Software Foundation will deliver RoI, then this is the talk for you!
How and Why you can and should Participate in Open Source Projects (AMIS, Sof...Lucas Jellema
For a long time I have been reluctant to actively contribute to an open source project. I thought it would be rather complicated and demanding – and that I didn't have the knowledge or skills for it or at the very least that they (the project team) weren't waiting for me.
In December 2021, I decided to have a serious input into the Dapr.io project – and now finally to determine how it works and whether it is really that complicated. In this session I want to tell you about my experiences. How Fork, Clone, Branch, Push (and PR) is the rhythm of contributing to an open source project and how you do that (these are all Git actions against GitHub repositories). How to learn how such a project functions and how to connect to it; which tools are needed, which communication channels are used. I tell how the standards of the project – largely automatically enforced – help me to become a better software engineer, with an eye for readability and testability of the code.
How the review process is quite exciting once you have offered your contribution. And how the final "merge to master" of my contribution and then the actual release (Dapr 1.6 contains my first contribution) are nice milestones.
I hope to motivate participants in this session to also take the step yourself and contribute to an open source project in the form of issues or samples, documentation or code. It's valuable to the community and the specific project and I think it's definitely a valuable experience for the "contributer". I looked up to it and now that I've done it gives me confidence – and it tastes like more (I could still use some help with the work on Dapr.io, by the way).
OSMC 2018 | Integrating Check_MK agent into Thruk – Windows monitoring made e...NETWAYS
Did you ever get a headache configuring Windows monitoring using NSClient++? We did, too! While using the Check_MK Windows agent we were impressed by the plethora of checks that had already been implemented there. With the goal in our minds to create a fast and easy-to-use Windows monitoring solution, we set out to integrate the Check_MK agent into Thruk and tap into it’s capabilities. Combining them even allows for fully automatic service discovery!
LTI Advantage: The Next Big Thing in LMS IntegrationCharles Severance
LTI Advantage is the next major integration standard for learning management systems (LMS). It uses new technologies like JSON Web Tokens (JWTs) and public/private key infrastructure (PKI) to securely launch tools and access user data and grading services. The presentation provides an overview of the LTI Advantage specification and code samples for implementing launches, user authorization, and accessing LMS services using libraries available in Java. While adoption of LTI Advantage promises tighter integration between LMSs and external tools, there are also transition challenges as vendors continue to evolve their systems.
We all love open source software and open culture, and of course we all want to contribute to and leverage the power of open source in our work. However when it comes to working in a startup, openness is often sacrificed to give way to work efficiency and business logic. In this talk I will talk about some of my experience(and failures) to be open source, and how our company is trying to be open by default without too much efficiency overhead.
https://hkoscon.org/2020/topics/open-default-trying-run-startup-open-source-culture-mind
Lucene and Solr are open-source search engines developed by the Apache Software Foundation (ASF). Lucene was created in 1999 and donated to ASF in 2001. Solr was created in 2004 and donated to ASF in 2006. Both projects have large user communities and are maintained through a collaborative process within ASF. ASF provides organizational support for many open-source projects through a meritocratic process.
Open Source at the Apache Software Foundation wgstoddard
This document provides an overview of the Apache Software Foundation and the development process used by Apache projects known as "The Apache Way". It discusses how the Apache Foundation was formed from the original Apache Group in response to IBM's decision to use and contribute to the Apache HTTP Server. It describes the founding principles of being developer-focused and not-for-profit. Statistics are given on growth in members, projects and traffic to Apache sites. The consensus-based development process aims to reduce barriers to participation while improving quality through open and transparent decision making.
Presentation for the recent developerWorks Open broadcast where OAI Board member Jeff Borek (@jeffborek) moderates a discussion with fellow OAI members Capital One's Dennis Brennan (@dennis_brennan), Apigee's Marsh Gardiner (@earth2marsh) and Tony Tam (@fehguy) of SmartBear Software along with Raymond Feng (@cyberfeng) of StrongLoop.
The document summarizes Ulrich Krause's presentation on the latest developments from OpenNTF. The presentation covered:
- An overview of OpenNTF, its 800+ open source projects and 200k annual downloads.
- Current OpenNTF initiatives like CollaborationToday, XPages.info, contests and webinars.
- Specific projects like Bootstrap4XPages, org.openntf.domino, Tika for XPages, and Unplugged XPages mobile controls.
- The OpenNTF intellectual property policy and ways for developers to get involved.
Come to this session to get an update about everything related to OpenNTF, the open source community for IBM Collaboration Solutions.
See the contest winning XPages projects live and learn about the new open source projects for IBM Connections.
The session will also cover the IBM Social Business Toolkit SDK which allows XPages, Java and JavaScript developers to easily access IBM Connections and IBM SmartCloud for Social Business from custom applications. Attend this session to see demos of the latest functionality and new samples of the toolkit.
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.
Programming the Real World: Javascript for Makerspchristensen
Hardware is becoming easier to design and manufacture, approaching the ease of software. This presentation:
- takes you on a tour of the changes in hardware
- a crash course in building circuits
- teaches the basics of using and programming Arduino
- introduces Javascript libraries for controlling hardware and robots
- how to get involved with hardware projects
If you'd like me to present this or similar content at your event, please contact me: peter at pchristensen dot com
My keynote at the CloudStack Collaboration Conference 2012 event. Overview of The Apache Way, the Lesson's Learned at the Apache Software Foundation on building code and community.
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.
Similar to The History of The Apache Software Foundation (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.
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.
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.
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.
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
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.
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.
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.
1. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
HISTORY OF THE ASF(A PERSONAL AND FACTUAL RECOLLECTION)
Jim Jagielski || @jimjag
NON PROFITS / FOUNDATIONS
2. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
ABOUT ME
• Apache Software Foundation
• Co-founder, Member, Emeritus Director, President, EVP, Chairman, Vice
Chairman, Secretary and VP
• Director (emeritus)
• Outercurve, MARSEC-XL, OSSI, OSI …
• Developer
• Much FOSS projects
• OSPO Lead, Uber
3. 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
4. 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
5. 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)
6. 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
7. 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”
8. 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
9. 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
10. 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.
11. 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
12. 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
13. 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.
14. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• There was no ASF
• There was just The Apache Group
• Apache === The Web Server Project
1995-1999
15. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• Right before incorporation1999
16. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• The ASF is born
• Started off w/ 2 projects:
• Web Server
• Conferences
• Quickly add additional projects
• Jakarta - Sun stuff/Java servlet
• XML - IBM stuff
• Members === Web Server PMC (21
people)
• ALv1.1
• CLA
1999
17. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• First ASF ApacheCon
• Added Apache TCL
• Perl Apache
• PHP (what??)
• APR
• initial work on ALv2
• Jakarta goes its own way…
2000-2001
18. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• Jakarta comes to a head and…
• … The Incubator is formed
• ASF joins JCP
• More projects enter the fold
• “The Apache Way” becomes more
and more well known
2002
19. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• ALv1.2 DOA
• What to do with PHP?
• Growth of “umbrella PMCs”
• HTTPD, Ant, Xerces-J win awards
2003
20. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• ALv2
• CLA, CVS and the Great Signing
• iCLA, and cCLA created
• Adios to Avalon - the ASF’s 2nd
painful lesson (https://lists.apache.org/thread.html/
7dbd83ec175e3462eb390f77b9c094efc6796f5453b59c01ef7e1abb%401101864
403%40%3Ccommunity.apache.org%3E)
• PHP “leaves”
• JBoss claims infringement on
Geronimo, ends up, they infringed
instead
2004
21. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• Umbrella projects lose favor - Jakarta
sub-projects start to leave the nest
• starts w/ Lucene
• Tomcat becomes TLP
• VP Legal Affairs
2005
22. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• The Great Jakarta Migration (to TLP)
• Security Team re-booted (board
cmmt)
• PRC re-booted (board cmmt)
• Apache Labs
• We hire a sys-admin!
• We start the ASF Sponsorship
program
• CVS shutdown - svn now default
2006
23. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• Website getting quite stale
• Loads of new projects
• CMO office dissolved (semi-DOA)
• Legal Affairs becomes full-fledged
cmmt
• Big changeover within board - 1st
time all Directors are “2nd
generation” (except for me)
2007
24. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• Major site refresh
• The Attic is born
• The Infrastructure cmmt (ad-hoc)
gets official VP
• Almost 1 project a month established
(on average)
• ASF wins JCP PMO Member of the
Year for the 3rd time (irony ahead)
2008
25. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• 10 Year anniversary
• VP W3C
• We take budgeting more seriously
• ~$400k/yr
• ComDev created
• PRC divides into 4 cmmts
2009
26. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• The ASF / Java relationship sours:
• IBM drops Harmony for OpenJDK
• Oracle’s FOU TCK restrictions
(continuation of Sun’s policy)
• ASF leaves JCP EC
• ~20 new TLPs
• From Lucene
• From Incubator
• Attic gains another 4 projects
• 1 millionth commit!
• Git starts being used
2010
27. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• Web site refresh
• Apache Harmony is terminated
• Jakarta terminated
• We hire our 1st (and only) executive
assistant.
• ASF subpoenaed in Oracle vs Google
2011
28. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• VP JCP finally dissolved
• Officers “executing operations”
moved to be under President
• Brand / Fundraising / M&P /
Conferences / TAC / Infra
• Budget ~ $750k/yr
• Apache HTTPD 2.4 released
2012
29. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• Infra grows
• 139 projects (or so)
• 386 members
• 25th ApacheCon event held
2013
30. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• Budget almost $1.2M
• Hired “Virtual” for financial
management
• We hit the 2 millionth code commit
mark
• Better GitHub integration
2014
31. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• We pass 500 members
• We pass 200 projects
• Lots of TLP related activity
• Chair changes
• Establish *
• Terminate *
2015
32. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• NEW LOGOS!
• Infra Administrator now officer
• 175 Projects
• 56 podlings
• Growth of 3rd “generation” of
ASFers
2016
33. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• 5 year plan discussion
• Formal Annual Reports
• 860 iCLAs on file
• 27 cCLAs
• 18 software grants
• What is “operations”?
2017
34. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• Hit 200M lines of code
• Board publishes ASF Vision
Statement
• Passes audit w/ flying colors
• I decide not to run for BOD
2018
35. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• The return of Jakarta (Eclipse
Foundation)
• The return of Xalan (from the Attic)
• VP Security
• 2nd major BOD changeout
• 2 Directors and the EVP resign;
replacements installed
2019
36. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
• Bye bye Apache Labs
• “Trillions and Trillions Served”
released
• 2021 budget expected to be ~$1.7M
• Refocus on core value prop and
project health with eye towards the
future - return to basics
2020 -
37. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
CURRENT STATUS
38. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
DIRECTORS
39. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
APACHE MESHES
40. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
TLPS
41. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
PODLINGS
42. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
RETIRED
43. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
ALL PROJECTS
44. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
ALL PROJECTS
45. This work is licensed under a Creative Commons Attribution 3.0 Unported License. - Jim Jagielski - @jimjag @jimjag
COMMITTERS
46. 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/