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
InnerSource - Using open source best practices to help your companyEric Caron
Once a company has more than 1 department developing code, a problem inevitably arises: How do you share source code that's mutually used? There are many different thoughts on the matter, but one that's starting to gain a significant amount of attention is "InnerSource". PayPal defines InnerSource as:
"InnerSource takes the lessons learned from developing open source software and applies them to the way companies develop software internally. As developers have become accustomed to working on world class open source software, there is a strong desire to bring those practices back inside the firewall and apply them to software that companies may be reluctant to release. For companies building mostly closed source software, InnerSource can be a great tool to help break down silos, encourage internal collaboration, accelerate new engineer on-boarding, and identify opportunities to contribute software back to the open source world."
In this talk I cover how to get from where you are ("Hey, we've got some source code that multiple people find useful!"), where you're going ("Look, we're more popular than ReactJS"), and some hurdles along the way ("Oh shoot, it looks like there is already a library to convert FLAC to MP3s..."). I give real-world examples of doing it right, and leave with some takeaways that people can immediately implement at their own companies.
* What is different GitHub Flow and Git Flow?
* What is GitHub Actions?
* How to write the simple workflow?
* What's problem in GitHub Actions UI?
* What's problem with Secrets in GitHub Actions?
* How to write your first GitHub Actions and upload to the marketplace?
* What's a problem with environment variables in GitHub Actions?
Integrate CI/CD Pipelines with Jira Software CloudAtlassian
Key development information, such as source code repositories, build servers, feature flag providers, and deployment services from CI/CD providers (both Cloud and On-premise), are now available in Jira Software Cloud.
Join Oliver Burn, Senior Architect for Jira Software Cloud, and learn how to integrate a new CI/CD system or leverage one of the many existing integrations for popular CI/CD providers. Discover how Jira Software gives teams the information they need to make faster, better decisions through continuous visibility.
InnerSource - Using open source best practices to help your companyEric Caron
Once a company has more than 1 department developing code, a problem inevitably arises: How do you share source code that's mutually used? There are many different thoughts on the matter, but one that's starting to gain a significant amount of attention is "InnerSource". PayPal defines InnerSource as:
"InnerSource takes the lessons learned from developing open source software and applies them to the way companies develop software internally. As developers have become accustomed to working on world class open source software, there is a strong desire to bring those practices back inside the firewall and apply them to software that companies may be reluctant to release. For companies building mostly closed source software, InnerSource can be a great tool to help break down silos, encourage internal collaboration, accelerate new engineer on-boarding, and identify opportunities to contribute software back to the open source world."
In this talk I cover how to get from where you are ("Hey, we've got some source code that multiple people find useful!"), where you're going ("Look, we're more popular than ReactJS"), and some hurdles along the way ("Oh shoot, it looks like there is already a library to convert FLAC to MP3s..."). I give real-world examples of doing it right, and leave with some takeaways that people can immediately implement at their own companies.
* What is different GitHub Flow and Git Flow?
* What is GitHub Actions?
* How to write the simple workflow?
* What's problem in GitHub Actions UI?
* What's problem with Secrets in GitHub Actions?
* How to write your first GitHub Actions and upload to the marketplace?
* What's a problem with environment variables in GitHub Actions?
Integrate CI/CD Pipelines with Jira Software CloudAtlassian
Key development information, such as source code repositories, build servers, feature flag providers, and deployment services from CI/CD providers (both Cloud and On-premise), are now available in Jira Software Cloud.
Join Oliver Burn, Senior Architect for Jira Software Cloud, and learn how to integrate a new CI/CD system or leverage one of the many existing integrations for popular CI/CD providers. Discover how Jira Software gives teams the information they need to make faster, better decisions through continuous visibility.
From capabilities to services modelling for business-it alignment v.2Trond Hjorteland
Our industry seems to go through cycles of re-discovery of lost knowledge with every new generation of developers, which probably is not so odd considering the exponential growth of practitioners. Allegedly half of the programmers today are juniors, which means many of them have yet to encounter the challenges faced decades ago. For example, many run the risk of falling into the trap of modelling services around domain entities, risking ending up with a distributed monolith with its devastating coupling, fragility, and cognitive nightmare. Lucky for us, we have shoulders to stand on to get us out of the quagmire, or even better, prevent us from getting on that slippery slope in the first place.
Being conscious of fallacies like those of distributed computing and anti-patterns like functional decomposition and entity services are all well and good, and necessary heuristics to good service design, but we often crave more concrete guidance. There are many great techniques to consider, like context mapping, user story mapping, event storming, and value chain analysis, but in this talk I will focus on the lost art of business capability modelling. My thesis is that a technique that was relevant in the pre-computing era might be just as useful and relevant when we split our monoliths into a mesh of autonomous (micro)services. Maybe they even could help us identify subdomains, contexts, and organisational structure; in effect the construction of sociotechnical systems?
Github - Git Training Slides: FoundationsLee Hanxue
Slide deck with detailed step breakdown that explains how git works, together with simple examples that you can try out yourself. Slides originated from http://teach.github.com/articles/course-slides/
Author: https://twitter.com/matthewmccull
Git is a distributed revision control system that is widely used in the software development industry. The presentation was used in a lecture delivered in BITS-Pilani, India. The lecture served as a basic crash course on Git.
First, it sets off with a guide to install and configure git on various platforms.
Then, the basic working concepts of Git are explained.
This is followed by a detailed step-by-step guided demonstration of a sample workflow in Git.
Afterwards, Some auxillary commands that are frequently used are discussed briefly.
Finally, basic concepts of branching and merging are detailed.
The presentation ends with a few possible merge conflicts that occur in Git.
Speaker: Jerry Reghunadh, Architect, CAPIOT Software Pvt. Ltd.
Level: 200 (Intermediate)
Track: Microservices
One of the leading assisted e-commerce players in India approached CAPIOT to rebuild their ERP system from the ground up. Their existing PHP-MySQL setup, while rich in functionality and having served them well for under half a decade, would not scale to meet future demands due to the exponential grown they were experiencing.
We built the entire system using a microservices architecture. To develop APIs we used Node.js, Express, Swagger and Mongoose, and MongoDB was used as the active data store. During the development phase, we solved several problems ranging from cross-service calls, data consistency, service discovery, and security.
One of the issues that we faced is how to effectively design and make cross-service calls. Should we implement a cross-service call for every document that we require or should we duplicate and distribute the data, reducing cross-service calls? We found a balance between these two and engineered a solution that gave us good performance.
In addition, our current system has 36 independent services. We enabled services to auto-discover and make secure calls.
We used Swagger to define our APIs first and enforce request and response validations and Mongoose as our ODM for schema validation. We also heavily depend on pre-save hooks to validate data and post-save hooks to trigger changes in other systems. This API-driven approach vastly enabled our frontend and backend teams to scrum together on a single API spec without worrying about the repercussions of changing API schemas.
What You Will Learn:
- How we used Swagger and Mongoose to off-load validations and schema enforcements. We used Swagger to define our APIs first and enforce request and response validations and Mongoose as our ODM for schema validation. We also heavily depend on pre-save hooks to validate data and post-save hooks to trigger changes in other systems. This API-driven approach vastly enabled our frontend and backend teams to scrum together on a single API spec without worrying about the repercussions of changing API schemas.
- How microservices and cross-service calls work. One of the issues that we faced is how to effectively design and make cross-service calls. Should we implement a cross-service call for every document that we require or should we duplicate and distribute the data, reducing cross-service calls? We found a balance between these two and engineered a solution that gave us good performance.
- How we implemented microservice auto discovery: Our current system has 36 independent services, so we enabled services to auto-discover and make secure calls.
Github is a continuous Integration and Continous delivery platform that provides an excellent option for automating workflows to run specific tasks when some event like code push or a release is triggered on the repository. In this Session we will be exploring Github Actions and learning how to use them in our projects.
The monolith to cloud-native, microservices evolution has driven a shift from monitoring to observability. OpenTelemetry, a merger of the OpenTracing and OpenCensus projects, is enabling Observability 2.0. This talk gives an overview of the OpenTelemetry project and then outlines some production-proven architectures for improving the observability of your applications and systems.
GIT Details for people who:
* don't know what version control means
* don't know what distributed version control means
* Used to work on SVN (Subversion)
The talk "Kubernetes and Docker Forensics & Incident Response" will focus on the Digital Forensics and Incident Response (DFIR) investigation of containerized environments using Kubernetes and Docker. With the increasing adoption of containerization technologies, it is crucial for organizations to have a robust security strategy in place to handle security incidents.
This talk will cover the key concepts of containerization technologies such as Docker and Kubernetes, and their security implications. We will discuss the forensic techniques and methodologies that can be used to identify the root cause of security incidents in these environments, including container forensics, network traffic analysis, and memory forensics.
The talk will also provide insights into the challenges and limitations of conducting a DFIR investigation in a containerized environment, such as the ephemeral nature of containers and the need for specialized tooling.
Attendees will learn about the best practices for implementing logging and monitoring in Docker and Kubernetes environments, as well as the importance of having a well-defined incident response plan for containerized environments.
Overall, this talk will provide valuable insights into the DFIR investigation of containerized environments using Kubernetes and Docker, and how organizations can better prepare themselves to respond to security incidents in these environments.
With these slides we introduce the concept of source control and teach the core features to using Git, GitHub and BitBucket. You can find the accompanying video here. https://youtu.be/lZpNrCgGvuI
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.
Building Cloud Native Applications Using Spring Boot and Spring CloudGeekNightHyderabad
Nowadays enterprises as well as startups are looking to build their software applications leveraging Cloud Platforms so that they can greatly reduce their go to market time and infrastructure setup costs. However, Cloud Native Applications (NCA) should be designed with cloud computing architecture in mind which involves thinking about dynamic provisioning of resources, service downtimes, data redundancy etc. Spring Boot provides a robust platform for building microservices and Spring Cloud provides the capabilities to build Cloud Native Applications by abstracting the low level details. In this talk, we will learn how to develop Cloud Native Applications using Spring Boot and Spring Cloud frameworks.
From capabilities to services modelling for business-it alignment v.2Trond Hjorteland
Our industry seems to go through cycles of re-discovery of lost knowledge with every new generation of developers, which probably is not so odd considering the exponential growth of practitioners. Allegedly half of the programmers today are juniors, which means many of them have yet to encounter the challenges faced decades ago. For example, many run the risk of falling into the trap of modelling services around domain entities, risking ending up with a distributed monolith with its devastating coupling, fragility, and cognitive nightmare. Lucky for us, we have shoulders to stand on to get us out of the quagmire, or even better, prevent us from getting on that slippery slope in the first place.
Being conscious of fallacies like those of distributed computing and anti-patterns like functional decomposition and entity services are all well and good, and necessary heuristics to good service design, but we often crave more concrete guidance. There are many great techniques to consider, like context mapping, user story mapping, event storming, and value chain analysis, but in this talk I will focus on the lost art of business capability modelling. My thesis is that a technique that was relevant in the pre-computing era might be just as useful and relevant when we split our monoliths into a mesh of autonomous (micro)services. Maybe they even could help us identify subdomains, contexts, and organisational structure; in effect the construction of sociotechnical systems?
Github - Git Training Slides: FoundationsLee Hanxue
Slide deck with detailed step breakdown that explains how git works, together with simple examples that you can try out yourself. Slides originated from http://teach.github.com/articles/course-slides/
Author: https://twitter.com/matthewmccull
Git is a distributed revision control system that is widely used in the software development industry. The presentation was used in a lecture delivered in BITS-Pilani, India. The lecture served as a basic crash course on Git.
First, it sets off with a guide to install and configure git on various platforms.
Then, the basic working concepts of Git are explained.
This is followed by a detailed step-by-step guided demonstration of a sample workflow in Git.
Afterwards, Some auxillary commands that are frequently used are discussed briefly.
Finally, basic concepts of branching and merging are detailed.
The presentation ends with a few possible merge conflicts that occur in Git.
Speaker: Jerry Reghunadh, Architect, CAPIOT Software Pvt. Ltd.
Level: 200 (Intermediate)
Track: Microservices
One of the leading assisted e-commerce players in India approached CAPIOT to rebuild their ERP system from the ground up. Their existing PHP-MySQL setup, while rich in functionality and having served them well for under half a decade, would not scale to meet future demands due to the exponential grown they were experiencing.
We built the entire system using a microservices architecture. To develop APIs we used Node.js, Express, Swagger and Mongoose, and MongoDB was used as the active data store. During the development phase, we solved several problems ranging from cross-service calls, data consistency, service discovery, and security.
One of the issues that we faced is how to effectively design and make cross-service calls. Should we implement a cross-service call for every document that we require or should we duplicate and distribute the data, reducing cross-service calls? We found a balance between these two and engineered a solution that gave us good performance.
In addition, our current system has 36 independent services. We enabled services to auto-discover and make secure calls.
We used Swagger to define our APIs first and enforce request and response validations and Mongoose as our ODM for schema validation. We also heavily depend on pre-save hooks to validate data and post-save hooks to trigger changes in other systems. This API-driven approach vastly enabled our frontend and backend teams to scrum together on a single API spec without worrying about the repercussions of changing API schemas.
What You Will Learn:
- How we used Swagger and Mongoose to off-load validations and schema enforcements. We used Swagger to define our APIs first and enforce request and response validations and Mongoose as our ODM for schema validation. We also heavily depend on pre-save hooks to validate data and post-save hooks to trigger changes in other systems. This API-driven approach vastly enabled our frontend and backend teams to scrum together on a single API spec without worrying about the repercussions of changing API schemas.
- How microservices and cross-service calls work. One of the issues that we faced is how to effectively design and make cross-service calls. Should we implement a cross-service call for every document that we require or should we duplicate and distribute the data, reducing cross-service calls? We found a balance between these two and engineered a solution that gave us good performance.
- How we implemented microservice auto discovery: Our current system has 36 independent services, so we enabled services to auto-discover and make secure calls.
Github is a continuous Integration and Continous delivery platform that provides an excellent option for automating workflows to run specific tasks when some event like code push or a release is triggered on the repository. In this Session we will be exploring Github Actions and learning how to use them in our projects.
The monolith to cloud-native, microservices evolution has driven a shift from monitoring to observability. OpenTelemetry, a merger of the OpenTracing and OpenCensus projects, is enabling Observability 2.0. This talk gives an overview of the OpenTelemetry project and then outlines some production-proven architectures for improving the observability of your applications and systems.
GIT Details for people who:
* don't know what version control means
* don't know what distributed version control means
* Used to work on SVN (Subversion)
The talk "Kubernetes and Docker Forensics & Incident Response" will focus on the Digital Forensics and Incident Response (DFIR) investigation of containerized environments using Kubernetes and Docker. With the increasing adoption of containerization technologies, it is crucial for organizations to have a robust security strategy in place to handle security incidents.
This talk will cover the key concepts of containerization technologies such as Docker and Kubernetes, and their security implications. We will discuss the forensic techniques and methodologies that can be used to identify the root cause of security incidents in these environments, including container forensics, network traffic analysis, and memory forensics.
The talk will also provide insights into the challenges and limitations of conducting a DFIR investigation in a containerized environment, such as the ephemeral nature of containers and the need for specialized tooling.
Attendees will learn about the best practices for implementing logging and monitoring in Docker and Kubernetes environments, as well as the importance of having a well-defined incident response plan for containerized environments.
Overall, this talk will provide valuable insights into the DFIR investigation of containerized environments using Kubernetes and Docker, and how organizations can better prepare themselves to respond to security incidents in these environments.
With these slides we introduce the concept of source control and teach the core features to using Git, GitHub and BitBucket. You can find the accompanying video here. https://youtu.be/lZpNrCgGvuI
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.
Building Cloud Native Applications Using Spring Boot and Spring CloudGeekNightHyderabad
Nowadays enterprises as well as startups are looking to build their software applications leveraging Cloud Platforms so that they can greatly reduce their go to market time and infrastructure setup costs. However, Cloud Native Applications (NCA) should be designed with cloud computing architecture in mind which involves thinking about dynamic provisioning of resources, service downtimes, data redundancy etc. Spring Boot provides a robust platform for building microservices and Spring Cloud provides the capabilities to build Cloud Native Applications by abstracting the low level details. In this talk, we will learn how to develop Cloud Native Applications using Spring Boot and Spring Cloud frameworks.
Inner Source Webinar Series: Open Source Community Development MethodsBlack Duck by Synopsys
In this webinar series, Guy Martin from Red Hat and Andrew Aitken from Black Duck Consulting cover the inner source concept of using open source community-style development methods and best practices in internal IT development organizations.
Get Hip with JHipster: Spring Boot + AngularJS + Bootstrap - Angular Summit 2015Matt Raible
Presentation from Angular Summit talk in September 2015. http://angularsummit.com/conference/boston/2015/09/session?id=34190
Building a modern web (or mobile) application requires a lot of tools, frameworks and techniques. This session shows how JHipster unites popular frameworks like AngularJS, Spring Boot and Bootstrap. Using Yeoman, a scaffolding tool for modern webapps, JHipster will generate a project for you and allow you to use Java 7 or 8, SQL or NoSQL databases, Spring profiles, Maven or Gradle, Grunt or Gulp.js, WebSockets and BrowserSync. It also supports a number of different authentication mechanisms: classic session-based auth, OAuth 2.0, or token-based authentication. For cloud deployments, JHipster includes out-of-the-box support for Cloud Foundry, Heroku and Openshift.
[Srijan Wednesday Webinars] InnerSource: An Open Source Approach to Community...Srijan Technologies
Companies can struggle to get their internal operations working smoothly. Cooperation between departments is essential. A silo mentality can easily occur when different groups or departments within an organisation do not share knowledge or information. This influences performance negatively and can contribute to a failing corporate culture.
The proactive development of a user community and the use of open source collaborative strategies will greatly benefit any organisation. InnerSource takes the lessons learned from open source projects and applies them to the internal company community or culture. InnerSource can be a great tool to help break down silos, encourage collaboration and create a happier workplace.
Desarrollo de Microservicios con Spring Boot.Vítor Fernández
Presentación utilizada en el evento del VigoJUG en noviembre de 2017.
Veremos cómo implementar de forma sencilla una arquitectura de microservicios con el framework Spring Boot. Mediante ejemplos prácticos, con unas pocas líneas de código pondremos en funcionamiento un API REST, utilizando las herramientas que nos facilita el ecosistema Spring.
Ejempos de código en https://github.com/vfdiaz/talk-vigojug-2017-springboot
Más info:
http://www.vigojug.org/
http://vigotech.org/
Disrupt TYPO3: Thinking the Unthinkable. Challenge our thinking and create a ...Age of Peers
If you pay attention, you’ll notice that clichés are everywhere. Often, the more established and obvious the cliché, the greater the impact when it’s challenged. In this presentation, community manager, Ben van 't Ende explores ways to challenge our thinking and create a new mindset.
Cloud Native Microservices with Spring CloudConor Svensson
In this talk we are going to discuss some of the key components of Spring Cloud. This includes the Netflix OSS integrations for Spring Boot apps which include Service Discovery (Eureka), Circuit Breaker (Hystrix), Intelligent Routing (Zuul) and Client Side Load Balancing (Ribbon). We will also touch on the Spring Cloud centralised configuration server and deploy these apps to Cloud Foundry.
Microservice With Spring Boot and Spring CloudEberhard Wolff
Spring Boot and Spring Cloud are an ideal foundation for creating Microservices based on Java. This presentation explains basic concepts of these libraries.
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.
Jim Jagielski, Director, Apache Software Foundation and Sr. Distinguished Engineer Tech Fellows Program, Capital One, at the 2017 Open Source Strategy Forum
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.
Open Source Contribution Policies That Don't SuckTobie Langel
Open source contribution policies are long, boring, overlooked documents, that generally suck. They're designed to protect the company at all costs. But in the process, end up hurting engineering productivity, and morale. Sometimes they even unknowingly put corporate IP at risk.
But that's not inevitable.
It's possible to write open source contribution policies that make engineers lives easier, boost morale and productivity, reduce attrition, and attract new talent. And it's possible to do so while reducing the company's IP risk, not increasing it.
In this talk, we'll look at the general structure of contribution policies, examples in the wild, and tactics to make them suck less.
We'll also look at how to turn these policies into self-service software, preventing the tedious email back and forth between engineering and legal in most cases and making open source contribution a breeze.
Growing Developer Community One Pull Request At a TimeAlex Bulankou
Strong foundation and core principles, environment that promotes checks and balances, and human interactions with empathy, acknowledgement and inclusion.
Open source contribution policies, OW2online, June 2020OW2
Open source contribution policies are long, boring, overlooked documents, that generally suck. They're designed to protect the company at all costs. But in the process, end up hurting engineering productivity, and morale. Sometimes they even unknowingly put corporate IP at risk.
But that's not inevitable.
It's possible to write open source contribution policies that make engineers lives easier, boost morale and productivity, reduce attrition, and attract new talent. And it's possible to do so while reducing the company's IP risk, not increasing it.
In this talk, we'll look at the general structure of contribution policies, examples in the wild, and tactics to make them suck less.
We'll also look at how to turn these policies into self-service software, preventing the tedious email back and forth between engineering and legal in most cases and making open source contribution a breeze. Presentation by Tobbie Langel, UnLockOpen.
Open source contribution policies, OW2online, June 2020OW2
Open source contribution policies are long, boring, overlooked documents, that generally suck. They're designed to protect the company at all costs. But in the process, end up hurting engineering productivity, and morale. Sometimes they even unknowingly put corporate IP at risk.
But that's not inevitable.
It's possible to write open source contribution policies that make engineers lives easier, boost morale and productivity, reduce attrition, and attract new talent. And it's possible to do so while reducing the company's IP risk, not increasing it.
In this talk, we'll look at the general structure of contribution policies, examples in the wild, and tactics to make them suck less.
We'll also look at how to turn these policies into self-service software, preventing the tedious email back and forth between engineering and legal in most cases and making open source contribution a breeze. Presentation by Tobie Langel, founder of UnlockOpen.
Open Source Product Management with KEMP Tech's PMProduct School
In this talk Danny Rosen, Product Manager at KEMP Tech, talked to a non-technical audience about the magic and wonder of open source. He went over what open source is, why it's important, what it means to have an open source product and why it's important to customers.
To Open Source or Not to Open Source...Where is the ROI?Ted Haeger
This presentation is from Evans Data Corp's 2009 Developer Relations Conference.
It is about how to approach code sharing (Open Source) to enable a developer community.
(We do not confuse Open Source with Free Software. You shouldn't Either.)
A tale of two cities: Merging Yahoo and Aol’s open source programsAshley Wolf
Every company needs to address how they manage open source. Verizon Media is the merger of Yahoo and AOL, and those two companies ran their open source programs quite differently. The result of bringing them together was surprisingly good, but the process to get there offers many insights into how you can structure your open source program office to address the biggest problems you may face.
Ashley Wolf and Gil Yehuda explain how Verizon Media now addresses license compliance, community management, the publication process, and how to run a program office at scale. You’ll explore real-world examples of things that worked well and things that needed much repair—as well as details on how it was done—and get advice on how to apply these lessons to your businesses.
Neglecting your open source program leads to problems. Ashley and Gil highlight some big ones, like when the wrong people have access to your code, license issues get you in hot water, and employees make well-meaning but incorrect decisions about code publications. Sometimes it takes a revolution to force you to step back and get a better hold on your open source program. But you don’t have to wait for a merger to force the changes. Better to set the processes right starting today; Ashley and Gil show you how.
If you don’t have a formal open source program office, or if you have one that needs a boost with some new ideas about how to maximize your value to the company, join this talk.
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!
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
2. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
About Me
➡ Apache Software Foundation
➡ Co-founder, Director, Member and Developer
➡ Director
➡ Outercurve, MARSEC-XL, OSSI, OSI (ex)…
➡ Developer
➡ Mega FOSS projects
➡ O’Reilly Open Source Award: 2013
➡ European Commission: Luminary Award
➡ Sr. Director: Tech Fellows: Capital One
3. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Introduction
➡ What can corporate IT learn from leading open development
communities?
➡ Both principles and techniques offer value
➡ Understanding principles allows you to alter techniques
➡ Challenges must be overcome to realize success
4. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Principles
➡ Communication
➡ Transparency
➡ Collaboration
➡ Community
➡ Meritocracy
5. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Principles: Communication
➡ Is core and foundational
➡ Everything builds on this
➡ Open and asynchronous
➡ Doesn’t disenfranchise anyone
➡ Archivable
➡ Maintains history and allows ebb/flow
➡ Document tribal knowledge
➡ Communication ➾ Transparency
6. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Principles: Transparency
➡ Public and Open
➡ Inclusion
➡ Reuse
➡ You can only reuse what you can see
➡ Connections
➡ Quality/Security
➡ More eyeballs mean better quality
➡ Measurement
➡ Transparency enables measurement
➡ Transparency ➾ Collaboration
7. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Principles: Collaboration
➡ Common Vision
➡ Common Goal
➡ See connections
➡ Encourages contribution and improves leverage
➡ Encourages feedback and dialogue
➡ Collaboration ➾ Community
8. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Principles: Community
➡ Loyalty
➡ Community breeds loyalty
➡ Durability
➡ Communities can create durable assets, processes and culture
➡ Health
➡ Feedback and Dialogue
➡ Community ➾ Meritocracy
9. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Principles: Meritocracy
➡ Technical decisions made by technical experts
➡ Better informed decisions
➡ Role models
➡ Merit provides examples
➡ Earned authority
➡ “Natural” leadership
➡ Known path and “rewards”
➡ Meritocracy ➾ Communication
10. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Techniques
➡ Collaboration Infrastructure
➡ Systems supporting communication and coordination: repositories,
trackers, forums, build tools
➡ Open Standards
➡ Using open standards in systems design and standards-based tools
for development
➡ Meritocratic Governance
➡ Merit determines influence on decisions
➡ Community-based governance structures
11. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Techniques: Communication and
Transparency
➡ E-Mail lists
➡ Avoid F2F meetings
➡ Always bring meeting discussions back to list
➡ IRC/Slack/Hipchat as backups
➡ Communications
➡ Encourage larger audiences
➡ Not just “core” teams
➡ Encourage “lurkers”
➡ All development done on-list
12. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Techniques: Collaboration
➡ Repositories
➡ Enable discoverability
➡ All can read, limit write
➡ Trackers
➡ Coordinate collaborative work, transparency
➡ Build and Test tools
➡ Enable consistent, independent
➡ repeatable builds
➡ support process discipline, quality assurance, productivity,ramp-up
➡ Sharing / re-use
13. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Techniques: Community
➡ Tech-talks
➡ Mentoring
➡ Cross-team events
➡ Break down silos
14. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Techniques: Meritocracy
➡ Decisions
➡ Influence on decisions determined by merit
➡ Structures
➡ Governance structures supporting merit-based decision-making
➡ Examples: PMC managing roadmap / stds, shared components;
user/contributor/committer roles for common code as well as
strategy / standards content; review and approval of changes
to standards, roadmaps, shared assets; peer voting on
releases
15. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Techniques: Open Standards
➡ Faster ramp-up
➡ Standards provide common background
➡ Easier setup
➡ Easier to get started, get up to speed
➡ Interoperability
➡ Key to success in heterogeneous environments
16. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Challenges
➡ Resistance
➡ Choosing the right opportunities
➡ “Open everything” does not work
➡ Rewarding merit
➡ Business focus
➡ Accountability
➡ Control
17. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Resistance
➡ If it ain't broke...
➡ Communication can be annoying at first
➡ Need to learn new tools and processes
➡ Closed processes and decision-making are the norm
➡ Administrivia can get in the way
➡ can provide a convenient excuse to defer / delay
➡ Fear of loss of control and/or “ownership”
18. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Choosing the Right Opportunities
Good Bad Ugly
Open development of
shared assets
Open development in
specialized areas with
small teams
Building communities
that have nothing to
do with day jobs
Meritocracy principles
integrated into
performance
management
Meritocratic decision-
making process, but
decisions not binding
Merit earned and
acknowledged, but not
rewarded
Open development
infrastructure
introduced as part of
process improvement
Open development
process introduced
with no infrastructure
support
Open development
principles mandated
with no process or
infrastructure support
19. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Meritocracy / Rewards Mismatch
➡ Defining “merit” can be hard
➡ Reward system may not be based on merit
➡ Path to merit must be clear and open
➡ Merit needs to be rewarded to proliferate
➡ Merit needs to be rewarded to be respected
20. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Maintaining Accountability
➡ Community ownership does not guarantee owners are always
available and responsive
➡ Not always clear who owns decisions or when decisions have
been made
➡ Easy to blame lack of engagement / community support for bad
decisions or work products
➡ Control and support responsibilities need to be managed
explicitly
➡ Developers get the 3am call
21. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Maintaining Control
➡ Communities are harder to direct and focus than individuals
➡ Merit can be invaluable here
➡ Company value needs to drive community, not vice-versa
➡ Roadmap needs to be explicit and direct
➡ Timelines, feature sets, quality, packaging and deployment
objectives have to be explicit
➡ accepted as largely “external”
22. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Maintaining Business Focus
➡ Community interest must align with company interest
➡ Business leaders have to be welcome and engaged in
community
➡ Merit is not just technical and has to be linked to business
results
➡ Projects need to deliver value – “show value early, show value
often”
➡ Inner Sourcing should not be used as a means to invest in
projects that have weak or no business case
23. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Final Thoughts
➡ Community is not the same as team
➡ Contribution is work
➡ Community requires investment
➡ Transparency is not a threat
➡ Collaboration means compromise
➡ Driving results means driving consensus
24. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Thanks!
Twitter: @jimjag
Emails:
jim@jaguNET.com
jim@apache.org
jim.jagielski@capitalone.com
http://www.slideshare.net/jimjag/
Thx to Phil Steitz for inspiration and supplemental information
25. This work is licensed under a Creative Commons Attribution 3.0 Unported License.
Backup Slides