DevTalk: Extending Open Source Projects

•

0 recomendaciones•604 vistas

Collaborating with open source teams is a fact of life for many development shops these days, but it can be hard to take changes from an active upstream project and even harder to contribute. Even more difficult is contributing to projects when you have changes the wider community may not want. See how the GitSwarm team at Perforce has developed branching, build, and test automation systems to stay up-to-date while still sharing as many changes as possible with the community. -Learn about run-time extension and when to use it -See how to automate the testing and merging of community changes -Identify key traits of extensible projects Watch the entire presentation here: https://youtu.be/WoDkGqd-Eow

Tecnología

Geoff Nicol
Principal Architect
Perforce
John Palmer
Technical Sales Engineer
Perforce
Extending Open Source Projects

Extending Open Source Projects
Overview
 Background
 Our Approach
 Supporting Automation
 Required Community Traits
 Q&A

Why do we need to
worry about this?
Extending Open Source Projects

GitSwarm
How’d we find ourselves in this situation?
Extending Open Source Projects

Our Approach
Extending Open Source Projects

Approach
 Don’t touch their files!
 Unless you have to
 Runtime extension
Extending Open Source Projects

Don’t touch their files!
Extending Open Source Projects

InPlace Extension
Extending Open Source Projects

●
Extend
 They have Foo
 We extend to OurFoo
 Noone uses OurFoo
Extending Open Source Projects

Prepend
<Image was too Scary>
Extending Open Source Projects

Runtime Extension
Extending Open Source Projects

Other Extensions
 Gems
 Database Migrations
 Views
 CSS/Sass
 JS/CoffeeScript
 Tests/RSpec/Spinach
Extending Open Source Projects

Automation
Extending Open Source Projects

Importing from Community
Extending Open Source Projects

Test Automation
Extending Open Source Projects

Merge Automation
Extending Open Source Projects

Resolve Automation
Extending Open Source Projects

Community Traits
Extending Open Source Projects

Community Traits
 Extensible Language/Framework
 Small Methods
 Community Tests
 Active
 Receptive to Change
Extending Open Source Projects

Recap!
 Programatic Extension
 Automate!
 Verify Community/Project Suitability
Extending Open Source Projects

THANK YOU!
Geoff Nicol
gnicol@perforce.com
Extending Open Source Projects

Más contenido relacionado

Destacado

Want to be a Wikipedian?

ALIA Community Information Australia Networkers

Developing the SA Prison Library Service

ALIA Community Information Australia Networkers

Blattmann cbu unesco

Andrielle Marques

Alberobello

gutaschimidt2011

2011 November Legislature

Michigan Economic Development Corporation

Social Networking & Web 2.0

ALIA Community Information Australia Networkers

Content Curation

ALIA Community Information Australia Networkers

Destacado (7)

Want to be a Wikipedian?

Developing the SA Prison Library Service

Blattmann cbu unesco

Alberobello

2011 November Legislature

Social Networking & Web 2.0

Content Curation

Similar a DevTalk: Extending Open Source Projects

It’s no coincidence that all the interest around DevOps today comes at a time when open source technologies and processes are so dominant in cloud computing, data storage and analysis, and--increasingly--in networking. Innovations in Linux and other projects, including containers, configuration management, and continuous integration, are what make DevOps workflows and portable application deployments possible. But it’s also the result of open source culture, practices, and the tools supporting those practices that have made iterative development and collaboration such a powerful model for creating great software in communities. And now, they’re also providing a template for how to develop and operate applications internally within enterprises. In this session, we will discuss how open source tools and practices can be applied to create effective DevOps workflows and practices.

How open source is driving DevOps innovation: CloudOpen NA 2015

Gordon Haff

OpenOffice, Open Business

imacat .

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).

How and Why you can and should Participate in Open Source Projects (AMIS, Sof...

Lucas Jellema

Open Source

ajitchouhan

The OSGeo Foundation: Professionally Leveraging Open Source Geospatial

Arnulf Christl

OpenNTF Webinar 05/07/13: OpenNTF - The IBM Collaboration Solutions App Dev C...

Niklas Heidloff

R1-intro-to-go.pptx

Ababb2

Understanding DevOps in simpler way with Continuous Delivery

Swapnil Jain

Open source software for startups

victorneo

Driving development in PHP

Eduardo Gulias Davis

FINOS June 2018 Members Meeting - Plotting Your Journey in Open Source

FINOS

MongoDB World 2018: How an Idea Becomes a MongoDB Feature

MongoDB

Monktoberfest Fast Delivery

Adrian Cockcroft

Intro to open source - 101 presentation

Javier Perez

Atlassian has been building out the Teamwork platform, bringing cross-product experiences like the rich-text editor to all of our products. Extending the Teamwork platform presents a new opportunity for developers. In this talk, we'll share more on what the Teamwork platform is, where is it available, and explore how we’re thinking app developers might extend the platform. Learn more about the future vision of building cross-product apps, consider what new opportunities it might present for your team, and give early feedback for how you’d like to see it evolve.

An Exploration of Cross-product App Experiences

Atlassian

Most of us understand the benefits of using open source software (OSS) and libraries. Heck, even Microsoft embraces it, so why can’t you adopt it as well in your enterprise? Open source can be a blessing and a curse at the same time. We probably all remember incidents like the “heart bleed” vulnerability in a popular open source implementation of SSL. So, if open source becomes more and more prevalent, how can we cope with the challenges that lay at hand? We will be challenged with all sorts of questions in the enterprise: What are the license implications when I take a dependency on a library with a viral type of license? What version of open source libraries are we using and are they the choice of the generic public or did we select one we now need to maintain ourselves? Are there known vulnerabilities in the libraries we use, and if so, are we affected by that? In this session, we take a practical approach to using open source libraries in product development for the enterprise. We touch briefly on the license types and the ones to look out for. We show you how an artefact repository system can help you to answer a lot of the tough questions. Learn how to integrate a system that is very popular, called Nexus, in your continuous deployment strategy and ensure a frictionless experience for your developers. We show integration with NuGet and how to manage open source dependencies using proxy facilities so you can ensure only a curated set of libraries are used, and meet compliance requirements for your business.

Best practices for using open source software in the enterprise

Marcel de Vries

There are two parts to the “success” of an open source software project: Deployment growth: One publishes software to see it used. As the software is used, it reflects the dynamic nature of software, and is used in new ways to solve new problems. This leads to the second part of the success formula -- contributions. Contribution flow: A free or open source software project is at it’s simplest a discussion in software, and without contributions the conversation fades and fails. From a more complex community perspective, a FOSS project is about the economics of collaborative innovation and development. Without a continuous contribution flow, the dynamic aspect of a software project will become static and brittle and lose its relevancy. There are three on ramps to be built to drive the success of an open source project: Bringing new users to the project, enabling developers, and encouraging contributors. This talk looks at how these on ramps can be organized to drive growth and adoption, and to grow a successful and vibrant community around an open source project. The talk was delivered at SCaLE 14x: https://www.socallinuxexpo.org/scale/14x/presentations/patterns-and-practices-open-source-project-success

Scale14x Patterns and Practices for Open Source Project Success

Stephen Walli

Open Community, Open Strategy

Target Source

Open source

Yin-Ta Pan

Intro to Open source. Amit Bhayani

guest2a6108

Similar a DevTalk: Extending Open Source Projects (20)

How open source is driving DevOps innovation: CloudOpen NA 2015

OpenOffice, Open Business

How and Why you can and should Participate in Open Source Projects (AMIS, Sof...

Open Source

The OSGeo Foundation: Professionally Leveraging Open Source Geospatial

OpenNTF Webinar 05/07/13: OpenNTF - The IBM Collaboration Solutions App Dev C...

R1-intro-to-go.pptx

Understanding DevOps in simpler way with Continuous Delivery

Open source software for startups

Driving development in PHP

FINOS June 2018 Members Meeting - Plotting Your Journey in Open Source

MongoDB World 2018: How an Idea Becomes a MongoDB Feature

Monktoberfest Fast Delivery

Intro to open source - 101 presentation

An Exploration of Cross-product App Experiences

Best practices for using open source software in the enterprise

Scale14x Patterns and Practices for Open Source Project Success

Open Community, Open Strategy

Open source

Intro to Open source. Amit Bhayani

Más de Perforce

Different skills have different needs when it comes to planning. For a coder it may make perfect sense to plan work in two-week sprints, but for an artist, an asset may take longer than two weeks to complete. How do you allow different skills to plan the way that works best for them? Some studios may choose to open up for flexibility – do whatever you like! But that tends to cause issues with alignment and siloes of data, resulting in loss of vision. Lost vision in the sense that it is difficult to understand, but also — and maybe more importantly — the risk of losing the vision of what the game will be. With the right approach, however, you can avoid these obstacles. Join backlog expert Johan Karlsson to learn: -The balance of team autonomy and alignment. -How to use the product backlog to align the project vision. -How to use tools to support the flexibility you need. Looking for a planning and backlog tool? You can try Hansoft for free.

How to Organize Game Developers With Different Planning Needs

DevTalk: Extending Open Source Projects

Recomendados

Recomendados

Más contenido relacionado

Destacado

Destacado (7)

Similar a DevTalk: Extending Open Source Projects

Similar a DevTalk: Extending Open Source Projects (20)

Más de Perforce

Más de Perforce (20)

Último

Último (20)

DevTalk: Extending Open Source Projects