Git Without Branches - Simple, Smooth, Scalable
Download as ODP, PDF2 likes3,012 views
The document discusses how Git complexity can be reduced by eliminating branches in favor of forks and pull requests. It argues that branching leads to complex strategies and processes that don't scale well. By switching to a model where every change is a pull request to a single master branch, projects can be simplified, mistakes reduced, and collaboration improved. The author provides an example of switching to this approach with the ØMQ project, which saw growth from a few to over 70 contributors as a result of the simpler, kinder process.
1 of 15
Downloaded 16 times
Ad
Recommended
Revolutionary Open Source
Revolutionary Open Sourcepieterh This document discusses how to build successful open source communities through "social architecture". It argues that closed source is dead and the future belongs to open source. However, open source projects require communities to be sustainable. Social architecture is the art and science of growing online communities. Key aspects include using the right open source license to encourage contribution and remixing, starting small and growing slowly, making the project accessible and inviting contribution from diverse participants, and having living rules and oversight to prevent conflicts and capture from undermining the community. Done right, communities can do most of the work with simple, elegant solutions while being profitable through widespread sharing of profits.
Open Source Product Management
Open Source Product ManagementDanny Rosen An intro to Open Source Product Management or "A PM’s primer on leftist software development models."
This presentation outlines Product Management in open source and outlines enterprise open source product management techniques, best practices in the space, licensing models and other topics that may be of interest to people working in software.
From Head to Binary
From Head to BinaryDominik Salvet A simple image-based presentation on the topic of transforming an idea into a binary code. The last slide represents a handout for the presentation.
I gave this presentation at the Faculty of Informatics of Masaryk University in 2019 within the VB036 English II course. It was focused on speaking performance.
DevOps for Engineers
DevOps for EngineersAhmed AbouZaid The main goal of this session is to answer what DevOps is, why it started, and how it will help you. It sheds some light on DevOps in action.
This session was part of Talents Arena's virtual tech job fair 2020.
How contributing to Open-source made me a better DevOps
How contributing to Open-source made me a better DevOpsAhmed AbouZaid How participating in Open-source made me a better DevOps
And that actually started not just as a professional system engineer, but much earlier as a normal end-user also as a power user.
Switch or broker
Switch or brokerpieterh This document compares two models for reliable AMQP architectures: the reliable message broker model and the asynchronous message switch (AMS) model with reliability over AMS (R/AMS). The reliable broker model provides reliability but is complex, centralized, and not scalable to wide area networks. The AMS/R/AMS model uses simple, lightweight message switches with reliability implemented through persistence and request/response handling, allowing for better performance, scalability, and simplicity over both local and wide area networks. R/AMS is presented as a better approach for the future of AMQP.
Software Architecture using ZeroMQ - techmesh 2012
Software Architecture using ZeroMQ - techmesh 2012pieterh This document discusses software architecture using ØMQ. It argues that most existing code will become trash and that we do not know how to build code that can survive for decades. It suggests that software architecture should focus on building durable, large-scale systems and that future code needs to be interconnected like people. It emphasizes that protocols define the obligations between parties and that simplicity and removing problems are more important than adding features.
Social architecture-101
Social architecture-101pieterh The document discusses how human social instincts can be leveraged to create highly effective self-organizing groups. It provides patterns that have been observed to work across different domains, including simplicity, fluid structures, collaboration, engagement by choice, decentralization, transparency, and competition. The core architecture outlined involves defining a compelling mission, creating structures for collaboration, investing in seed projects, using problems to feed the structures, promoting active participants, and acting as a benevolent dictator. Examples mentioned include open source communities, radical management techniques, Wikipedia, and the early web.
Fosdem 2009
Fosdem 2009pieterh - The document discusses the need for simpler messaging standards and protocols as an alternative to complex and proprietary solutions.
- It introduces AMQP as an open protocol for messaging but notes it is still complex. It then presents RestMS as a simpler RESTful alternative to AMQP that works over plain HTTP.
- Examples are given of using RestMS through HTTP requests and responses to create feeds and send messages. Open source projects including Zyre, OpenAMQ, and X5 are discussed which implement RestMS.
CurveZMQ, ZMTP and other Dubious Characters
CurveZMQ, ZMTP and other Dubious Characterspieterh The document discusses secure messaging for internet applications using ZeroMQ. It proposes solutions like CurveZMQ and ZMTP 3.0 that provide encryption, authentication and extensibility at the protocol level. CurveZMQ defines a security handshake inspired by CurveCP that is transport neutral and compatible with SASL. ZMTP 3.0 introduces security mechanisms to ZMQ like CURVE for full encryption and authentication. The author advocates getting involved in the open RFC process to help evolve these standards.
ZeroMQ: Super Sockets - by J2 Labs
ZeroMQ: Super Sockets - by J2 LabsJames Dennis ZeroMQ is a library for message passing between processes using sockets. It provides patterns for common messaging needs like publish-subscribe, request-reply, and push-pull. ZeroMQ supports multiple protocols including TCP and inter-process communication. It aims to be more flexible than traditional messaging systems by allowing decentralized architectures. Examples of projects using ZeroMQ include Mongrel2, a high-performance web server, and Brubeck, a Python web framework.
Software Architecture over ZeroMQ
Software Architecture over ZeroMQpieterh The document contains a series of one-line statements by Pieter Hintjens about software architecture and distributed systems. Some of the key points made include that software needs to be designed to connect to other code and last for decades; distributed systems live or die by their communication protocols; and that ØMQ provides a framework for building distributed protocols and applications. The statements cover a range of topics from software design, distributed systems, security and ZeroMQ in particular.
RestMS Introduction
RestMS Introductionpieterh RestMS is a new protocol for web messaging that aims to provide a simple yet capable solution based on open standards. It takes the best aspects of AMQP, such as its generic routing model, and AtomPub, such as its RESTful access over HTTP, and combines them. RestMS allows publishers to send messages to feeds and subscribers to create pipes that join feeds to receive and process messages. It uses common REST/HTTP operations and aims to be easy to use while still providing high performance and interoperability.
Build reliable, traceable, distributed systems with ZeroMQ
Build reliable, traceable, distributed systems with ZeroMQRobin Xiao ZeroMQ is used to build a distributed system with reliable and traceable communication. It allows exposing code over RPC with minimal modification. Exceptions are properly propagated across services. The system is language agnostic and brokerless. Introspection allows viewing methods and signatures without opening code. Streaming APIs allow continuous updates without timeouts. Tracing helps profile nested calls and identify performance bottlenecks. Security is not implemented but could use SSL or authentication layers.
FOSDEM 2011 - 0MQ
FOSDEM 2011 - 0MQpieterh 1) The document discusses concurrency and the traditional model of sharing data between threads which leads to complexity, bugs, and diminishing returns.
2) It introduces the actor model from 1973 which uses message passing between isolated processes or "actors" to achieve concurrency without shared data.
3) ZeroMQ is presented as a modern implementation of the actor model, allowing applications to connect threads and processes across machines using messaging without locks or shared state.
Europycon2011: Implementing distributed application using ZeroMQ
Europycon2011: Implementing distributed application using ZeroMQfcrippa The document discusses the messaging patterns and sockets in ØMQ (ZeroMQ), an open-source library for building distributed applications. It describes the basic patterns like publisher-subscriber, request-reply, and load balancing. It explains that ØMQ sockets support asynchronous messaging, are cross-platform, and can be used from multiple programming languages. The document also touches on scalability, dynamic scaling, and built-in devices in ØMQ like proxies and brokers.
ZeroMQ Is The Answer
ZeroMQ Is The AnswerIan Barber Using Mikko Koppanen's PHP ZMQ extension we will look at how you can easily distribute work to background processes, provide flexible service brokering for your next service oriented architecture, and manage caches efficiently and easily with just PHP and the ZeroMQ libraries. Whether the problem is asynchronous communication, message distribution, process management or just about anything, ZeroMQ can help you build an architecture that is more resilient, more scalable and more flexible, without introducing unnecessary overhead or requiring a heavyweight queue manager node.
Overview of ZeroMQ
Overview of ZeroMQpieterh ØMQ was created to address the need for cheaper and more efficient connectivity between distributed systems as hardware capabilities increased. It is an intelligent socket library that provides various connection patterns for messaging between processes. ØMQ aims to be fast, small, multiplatform, and multilingual. It uses common patterns like request-reply and publish-subscribe to allow processes to communicate simply and efficiently over in-process, inter-process, and network connections. The ØMQ community continues to enhance and support the open source library.
Git intro fajar muslim
Git intro fajar muslimJesslyn Nathania The document discusses Git version control. It begins with an introduction and outline. Git is introduced as a free and open source distributed version control system designed to handle projects of all sizes efficiently. Reasons for needing Git include collaboration and maintaining a portfolio of work. The document indicates there will be examples and a demo of how Git works. It concludes by discussing creating a GitHub repository and basic Git commands like cloning, adding, committing, and pushing files. The presenter will demonstrate making a simple CV using HTML and CSS.
Git & Code review
Git & Code reviewCenk Gültekin This document discusses code reviews and Git. It provides information on what code reviews are, why they are important, and what reviewers typically look for. It then discusses Git, including what it is, common scenarios like rebasing and merging, and popular Git tools. Best practices for branching, branch management strategies, and the differences between rebasing and merging are also covered. Additional sources with more information on these topics are provided at the end.
Getting Started With Git and GitHub & Unfolding Opportunities in Open Source 
Getting Started With Git and GitHub & Unfolding Opportunities in Open Source Ashutosh Singh Looking to get started with Git and GitHub?
Did you always wonder what is Open Source and How you can contribute to it?
Do you need to collaborate with a team?
Do you want to work on an open source project?
Then this session is for you. We will start from the basics of Git and GitHub and dive into the world of Open Source and all the exciting opportunities it holds for you.
During this two-hour session, you will get a general overview of Git version control and GitHub from Mritunjay Kumar Sharma, a former GSoC Scholar @RTEMS and SiH'20 Winner.
We will be joined by Ekta Mishra, Co-Founder @ Code for Cause, SDE Intern @ Red Hat and an Outreachy Finalist who will discuss what Open Source is? how you can contribute to it? What different programs like GSoC, Outreachy, MLH Fellowship, etc.
Learning to use Git and GitHub is the first step towards getting familiar with Open Source and managing projects efficiently. This is the objective of the workshop for the 1st year members who are just beginning their journey to programming. Along with understanding what's what all we can do with Git, it's equally important to understand how to do it well.
No prior programming experience is necessary.
Git in the Enterprise: How to succeed at DevOps using Git and a monorepo 
Git in the Enterprise: How to succeed at DevOps using Git and a monorepo Perforce Join GitLab VP of Product Job van der Voort and Perforce VP of Community Matt Attaway to hear lessons learned from their customers on how to succeed with DevOps using Git and a monorepo.
In this webinar we'll discuss:
- Approaches for managing teams and projects using Git
- Techniques for handling issue tracking across dependent projects
- Methods for automating testing and deployment
- Strategies for bringing enterprise scale, cross-project visibility and security to teams using Git
Git in the Enterprise: How to succeed at DevOps using Git and a monorepo
Git in the Enterprise: How to succeed at DevOps using Git and a monorepoGina Bustos Join GitLab VP of Product Job van der Voort and Perforce VP of Community Matt Attaway to hear lessons learned from their customers on how to succeed with DevOps using Git and a monorepo.
In this webinar we'll discuss:
- Approaches for managing teams and projects using Git
- Techniques for handling issue tracking across dependent projects
- Methods for automating testing and deployment
- Strategies for bringing enterprise scale, cross-project visibility and security to teams using Git
Pull requests do's and don'ts
Pull requests do's and don'tsArie Bregman The document discusses best practices for submitting pull requests, including:
- Using meaningful commit messages that describe the purpose and changes of a commit, rather than meaningless messages.
- Limiting each pull request to one commit or a small number of related commits, rather than including multiple unrelated commits in a single request.
- Ensuring pull requests pass all continuous integration tests before requesting review, and addressing any failures or issues found by CI systems.
- Distinguishing commit messages, which describe changes, from code comments, which explain the code itself.
Modern source and_version_control_with_git
Modern source and_version_control_with_gitChristian Couder Evolution and benefits of modern version control with Git.
Importance of good use of version control for quality and agility, because of its big impact on code reviews and testing.
GIT AND GITHUB (1).pptx
GIT AND GITHUB (1).pptxGDSCCVRGUPoweredbyGo Git is a version control system that allows developers to work together and track changes to files over time. GitHub is a web-based platform that uses Git version control and allows collaboration on projects. The speakers demonstrated how to set up Git locally, create a GitHub account, initialize and push a repository, make commits, create branches, pull and push changes, fork repositories, and make pull requests to contribute code back to the original project. Open source development was discussed, including competitions that promote contributions to open source projects.
Software Engineering Primer
Software Engineering PrimerGeorg Buske Georg Buske provided an overview of essential software engineering topics for both small and large projects, including:
- Agile methodologies like Scrum, Kanban, and XP and how they can be applied to different sized projects.
- Software design principles like clean code, SOLID, DRY, KISS, and YAGNI and architectural styles like domain-driven design.
- The importance of documentation, standards, and guidelines for development processes, coding practices, and more within organizations.
- Additional topics on testing approaches like TDD, naming conventions, anti-patterns to avoid, and prioritizing simple, maintainable solutions.
Devops, Secops, Opsec, DevSec *ops *.* ?
Devops, Secops, Opsec, DevSec *ops *.* ?Kris Buytaert This document discusses the DevOps movement and related concepts. It provides background on how development and operations teams historically worked separately ("Devs vs Ops") and the problems that caused. DevOps aims to break down barriers between teams through practices like automation, continuous integration/delivery, infrastructure as code, and collaboration between teams from the beginning of a project. The document outlines problems DevOps aims to solve and gives examples of tools and approaches for bringing development and operations cultures together.
Let's talk FOSS!
Let's talk FOSS!AditiSaxena72 All of us, as part of the technical sphere, have sometime or the other heard about the term 'open-source'. Even if we haven't, we have been using since the first time we learned an algorithm or downloaded a software for free from the internet. But for most of you, this term may still be shrouded in mystery. So DSC IIT Goa and InfoSec IIT Goa are here for the rescue.
In this introductory event, we will celebrate the existence of this ever-expanding and most welcoming open-source community. A brief overview of the topics we'll cover is as below:
1. Introduction to open-source and why is it so valuable?
2. Basics of Git, GitHub and how to make a Pull Request.
3. Everything you need to know before making your first contribution.
4. Challenges faced and how to resolve them.
5. How open-source brings a security mindset.
6. Guide to safe usage and contribution to the community.
7. Famous annual open-source events and how to participate in them.
This event will fully equip you make the most dashing entry into this amazing community.
Ad
More Related Content
Viewers also liked (10)
Fosdem 2009
Fosdem 2009pieterh - The document discusses the need for simpler messaging standards and protocols as an alternative to complex and proprietary solutions.
- It introduces AMQP as an open protocol for messaging but notes it is still complex. It then presents RestMS as a simpler RESTful alternative to AMQP that works over plain HTTP.
- Examples are given of using RestMS through HTTP requests and responses to create feeds and send messages. Open source projects including Zyre, OpenAMQ, and X5 are discussed which implement RestMS.
CurveZMQ, ZMTP and other Dubious Characters
CurveZMQ, ZMTP and other Dubious Characterspieterh The document discusses secure messaging for internet applications using ZeroMQ. It proposes solutions like CurveZMQ and ZMTP 3.0 that provide encryption, authentication and extensibility at the protocol level. CurveZMQ defines a security handshake inspired by CurveCP that is transport neutral and compatible with SASL. ZMTP 3.0 introduces security mechanisms to ZMQ like CURVE for full encryption and authentication. The author advocates getting involved in the open RFC process to help evolve these standards.
ZeroMQ: Super Sockets - by J2 Labs
ZeroMQ: Super Sockets - by J2 LabsJames Dennis ZeroMQ is a library for message passing between processes using sockets. It provides patterns for common messaging needs like publish-subscribe, request-reply, and push-pull. ZeroMQ supports multiple protocols including TCP and inter-process communication. It aims to be more flexible than traditional messaging systems by allowing decentralized architectures. Examples of projects using ZeroMQ include Mongrel2, a high-performance web server, and Brubeck, a Python web framework.
Software Architecture over ZeroMQ
Software Architecture over ZeroMQpieterh The document contains a series of one-line statements by Pieter Hintjens about software architecture and distributed systems. Some of the key points made include that software needs to be designed to connect to other code and last for decades; distributed systems live or die by their communication protocols; and that ØMQ provides a framework for building distributed protocols and applications. The statements cover a range of topics from software design, distributed systems, security and ZeroMQ in particular.
RestMS Introduction
RestMS Introductionpieterh RestMS is a new protocol for web messaging that aims to provide a simple yet capable solution based on open standards. It takes the best aspects of AMQP, such as its generic routing model, and AtomPub, such as its RESTful access over HTTP, and combines them. RestMS allows publishers to send messages to feeds and subscribers to create pipes that join feeds to receive and process messages. It uses common REST/HTTP operations and aims to be easy to use while still providing high performance and interoperability.
Build reliable, traceable, distributed systems with ZeroMQ
Build reliable, traceable, distributed systems with ZeroMQRobin Xiao ZeroMQ is used to build a distributed system with reliable and traceable communication. It allows exposing code over RPC with minimal modification. Exceptions are properly propagated across services. The system is language agnostic and brokerless. Introspection allows viewing methods and signatures without opening code. Streaming APIs allow continuous updates without timeouts. Tracing helps profile nested calls and identify performance bottlenecks. Security is not implemented but could use SSL or authentication layers.
FOSDEM 2011 - 0MQ
FOSDEM 2011 - 0MQpieterh 1) The document discusses concurrency and the traditional model of sharing data between threads which leads to complexity, bugs, and diminishing returns.
2) It introduces the actor model from 1973 which uses message passing between isolated processes or "actors" to achieve concurrency without shared data.
3) ZeroMQ is presented as a modern implementation of the actor model, allowing applications to connect threads and processes across machines using messaging without locks or shared state.
Europycon2011: Implementing distributed application using ZeroMQ
Europycon2011: Implementing distributed application using ZeroMQfcrippa The document discusses the messaging patterns and sockets in ØMQ (ZeroMQ), an open-source library for building distributed applications. It describes the basic patterns like publisher-subscriber, request-reply, and load balancing. It explains that ØMQ sockets support asynchronous messaging, are cross-platform, and can be used from multiple programming languages. The document also touches on scalability, dynamic scaling, and built-in devices in ØMQ like proxies and brokers.
ZeroMQ Is The Answer
ZeroMQ Is The AnswerIan Barber Using Mikko Koppanen's PHP ZMQ extension we will look at how you can easily distribute work to background processes, provide flexible service brokering for your next service oriented architecture, and manage caches efficiently and easily with just PHP and the ZeroMQ libraries. Whether the problem is asynchronous communication, message distribution, process management or just about anything, ZeroMQ can help you build an architecture that is more resilient, more scalable and more flexible, without introducing unnecessary overhead or requiring a heavyweight queue manager node.
Overview of ZeroMQ
Overview of ZeroMQpieterh ØMQ was created to address the need for cheaper and more efficient connectivity between distributed systems as hardware capabilities increased. It is an intelligent socket library that provides various connection patterns for messaging between processes. ØMQ aims to be fast, small, multiplatform, and multilingual. It uses common patterns like request-reply and publish-subscribe to allow processes to communicate simply and efficiently over in-process, inter-process, and network connections. The ØMQ community continues to enhance and support the open source library.
Similar to Git Without Branches - Simple, Smooth, Scalable (20)
Git intro fajar muslim
Git intro fajar muslimJesslyn Nathania The document discusses Git version control. It begins with an introduction and outline. Git is introduced as a free and open source distributed version control system designed to handle projects of all sizes efficiently. Reasons for needing Git include collaboration and maintaining a portfolio of work. The document indicates there will be examples and a demo of how Git works. It concludes by discussing creating a GitHub repository and basic Git commands like cloning, adding, committing, and pushing files. The presenter will demonstrate making a simple CV using HTML and CSS.
Git & Code review
Git & Code reviewCenk Gültekin This document discusses code reviews and Git. It provides information on what code reviews are, why they are important, and what reviewers typically look for. It then discusses Git, including what it is, common scenarios like rebasing and merging, and popular Git tools. Best practices for branching, branch management strategies, and the differences between rebasing and merging are also covered. Additional sources with more information on these topics are provided at the end.
Getting Started With Git and GitHub & Unfolding Opportunities in Open Source
Getting Started With Git and GitHub & Unfolding Opportunities in Open Source Ashutosh Singh Looking to get started with Git and GitHub?
Did you always wonder what is Open Source and How you can contribute to it?
Do you need to collaborate with a team?
Do you want to work on an open source project?
Then this session is for you. We will start from the basics of Git and GitHub and dive into the world of Open Source and all the exciting opportunities it holds for you.
During this two-hour session, you will get a general overview of Git version control and GitHub from Mritunjay Kumar Sharma, a former GSoC Scholar @RTEMS and SiH'20 Winner.
We will be joined by Ekta Mishra, Co-Founder @ Code for Cause, SDE Intern @ Red Hat and an Outreachy Finalist who will discuss what Open Source is? how you can contribute to it? What different programs like GSoC, Outreachy, MLH Fellowship, etc.
Learning to use Git and GitHub is the first step towards getting familiar with Open Source and managing projects efficiently. This is the objective of the workshop for the 1st year members who are just beginning their journey to programming. Along with understanding what's what all we can do with Git, it's equally important to understand how to do it well.
No prior programming experience is necessary.
Git in the Enterprise: How to succeed at DevOps using Git and a monorepo
Git in the Enterprise: How to succeed at DevOps using Git and a monorepo Perforce Join GitLab VP of Product Job van der Voort and Perforce VP of Community Matt Attaway to hear lessons learned from their customers on how to succeed with DevOps using Git and a monorepo.
In this webinar we'll discuss:
- Approaches for managing teams and projects using Git
- Techniques for handling issue tracking across dependent projects
- Methods for automating testing and deployment
- Strategies for bringing enterprise scale, cross-project visibility and security to teams using Git
Git in the Enterprise: How to succeed at DevOps using Git and a monorepo
Git in the Enterprise: How to succeed at DevOps using Git and a monorepoGina Bustos Join GitLab VP of Product Job van der Voort and Perforce VP of Community Matt Attaway to hear lessons learned from their customers on how to succeed with DevOps using Git and a monorepo.
In this webinar we'll discuss:
- Approaches for managing teams and projects using Git
- Techniques for handling issue tracking across dependent projects
- Methods for automating testing and deployment
- Strategies for bringing enterprise scale, cross-project visibility and security to teams using Git
Pull requests do's and don'ts
Pull requests do's and don'tsArie Bregman The document discusses best practices for submitting pull requests, including:
- Using meaningful commit messages that describe the purpose and changes of a commit, rather than meaningless messages.
- Limiting each pull request to one commit or a small number of related commits, rather than including multiple unrelated commits in a single request.
- Ensuring pull requests pass all continuous integration tests before requesting review, and addressing any failures or issues found by CI systems.
- Distinguishing commit messages, which describe changes, from code comments, which explain the code itself.
Modern source and_version_control_with_git
Modern source and_version_control_with_gitChristian Couder Evolution and benefits of modern version control with Git.
Importance of good use of version control for quality and agility, because of its big impact on code reviews and testing.
GIT AND GITHUB (1).pptx
GIT AND GITHUB (1).pptxGDSCCVRGUPoweredbyGo Git is a version control system that allows developers to work together and track changes to files over time. GitHub is a web-based platform that uses Git version control and allows collaboration on projects. The speakers demonstrated how to set up Git locally, create a GitHub account, initialize and push a repository, make commits, create branches, pull and push changes, fork repositories, and make pull requests to contribute code back to the original project. Open source development was discussed, including competitions that promote contributions to open source projects.
Software Engineering Primer
Software Engineering PrimerGeorg Buske Georg Buske provided an overview of essential software engineering topics for both small and large projects, including:
- Agile methodologies like Scrum, Kanban, and XP and how they can be applied to different sized projects.
- Software design principles like clean code, SOLID, DRY, KISS, and YAGNI and architectural styles like domain-driven design.
- The importance of documentation, standards, and guidelines for development processes, coding practices, and more within organizations.
- Additional topics on testing approaches like TDD, naming conventions, anti-patterns to avoid, and prioritizing simple, maintainable solutions.
Devops, Secops, Opsec, DevSec *ops *.* ?
Devops, Secops, Opsec, DevSec *ops *.* ?Kris Buytaert This document discusses the DevOps movement and related concepts. It provides background on how development and operations teams historically worked separately ("Devs vs Ops") and the problems that caused. DevOps aims to break down barriers between teams through practices like automation, continuous integration/delivery, infrastructure as code, and collaboration between teams from the beginning of a project. The document outlines problems DevOps aims to solve and gives examples of tools and approaches for bringing development and operations cultures together.
Let's talk FOSS!
Let's talk FOSS!AditiSaxena72 All of us, as part of the technical sphere, have sometime or the other heard about the term 'open-source'. Even if we haven't, we have been using since the first time we learned an algorithm or downloaded a software for free from the internet. But for most of you, this term may still be shrouded in mystery. So DSC IIT Goa and InfoSec IIT Goa are here for the rescue.
In this introductory event, we will celebrate the existence of this ever-expanding and most welcoming open-source community. A brief overview of the topics we'll cover is as below:
1. Introduction to open-source and why is it so valuable?
2. Basics of Git, GitHub and how to make a Pull Request.
3. Everything you need to know before making your first contribution.
4. Challenges faced and how to resolve them.
5. How open-source brings a security mindset.
6. Guide to safe usage and contribution to the community.
7. Famous annual open-source events and how to participate in them.
This event will fully equip you make the most dashing entry into this amazing community.
Post-Agile Methodologies and all that Jazz
Post-Agile Methodologies and all that JazzStojan Peshov It's been 15 years since the Agile Manifesto was signed and several methodologies were raised ever since. There is almost no developer nowdays that haven't adopted at least one of the Agile principles and uses them in everyday work or even private life. Some has even done improvised versions which work according their needs.
The question that's been around these past years is if the Agile is old enough to become past and what's the next big thing, is it a time to call it Post-Agilit period and what that means. What has or needs to change in order to abandon the old and become the Post Agilit followers.
Lots of teams already claim themselves as Post-Agilit pioneers and some new ideas of methodologies have been introduced. I'll try to bring an overview of some of them and bring you some thoughts that might help answering the above questions.
Agile team workflow
Agile team workflowMahmoud Masih Tehrani managment team workflow with git work flow ci,cd & release strategy, smantic versioning , code review, lint & test
Git Branching – the battle of the ages
Git Branching – the battle of the agesJasmin Fluri Comparison of two common git workflows - trunk based and git-flow workflow.
Shared presentation by Jasmin Fluri and Gianni Ceresa.
Picking the right architecture and sticking to it
Picking the right architecture and sticking to itPetter Holmström The document provides guidance on choosing an architecture for a project, sticking to it, and evolving it over time. It emphasizes doing research upfront on project scope, requirements, and potential risks. The initial design should consider experimenting with new approaches but also prototyping risky features. Future changes should be considered but not overdesigned for. The architecture must be documented and explained to the team. Tests and code reviews help ensure the architecture is followed. While 90% of features can be implemented as designed, the architecture must be flexible to handle unexpected changes through open communication and potential compromises.
Nimble - iOS dependency management
Nimble - iOS dependency managementNimble We explore the multiple package managers available in iOS (2017) and we outline the pros and cons of each of them to decide which one we use moving forward.
Devops Devops Devops, at Froscon
Devops Devops Devops, at FrosconKris Buytaert Devops, Devops , Devops, from Dev and Ops to Devops presented at Froscon in Sankt-Augusting (Germany) on August 21st 2011
Git Things Done
Git Things DoneFITC Presented at Web Unleashed 2017
More info at www.fitc.ca/webu
Anne Thomas
Out of the Sandbox
Overview
Whether you are one developer or have a group of devs working on the same codebase, things can get a little crowded and messy. Git to the rescue! But are you using git and services like GitHub to their full potential? This talk will look at how you can best leverage git so that your merge conflicts are minimal and your projects get out the door on time. Anne will also be looking at real-life examples of git workflows so you can determine which one will work best for your situation.
Objective
To empower everyone to use git to keep their projects manageable, prevent mistakes and create a seamless development experience.
Target Audience
Teams/individuals who want to improve their git workflow
Five Things Audience Members Will Learn
Branch naming and how to set up a git-flow structure
Techniques for organizing multiple team members and branches
How to use projects, issues and tags to document your progress
Tools that make git easier to manage
How to integrate quality assurance into your process
Introduction to git and stash
Introduction to git and stashXpand IT Git is a distributed version control system created by Linus Torvalds in 2005 to manage work on the Linux kernel. Stash provides a graphical user interface for managing Git repositories in an enterprise setting. It offers features like security, integration with other tools like JIRA, and extensibility through APIs and add-ons. Stash is used by many large companies and open source projects to provide version control capabilities tailored for collaborative development in teams.
Ad
Git Without Branches - Simple, Smooth, Scalable
- 1. Git Without Branches - Simple, Smooth, Scalable Defusing the Git Complexity Bomb by Pieter Hintjens, CEO, iMatix Berlin Buzzwords 2013, 3 June, 2013
- 2. Git is easy... ... once you understand that a git branch is just a folded five- dimensional lepton space that has a detached history with no intervening cache.
- 3. Git makes me feel stupid ● (I love git... but) ● Inconsistent and arbitrary commands ● Too many concepts to learn ● Too many ways to make mistakes ● Too much space for opinion ● Every team has to invent a strategy
- 4. Git-flow is a popular strategy ● Has base branches (master, develop) ● Has feature branches ● Has release branches ● Has hotfix branches ● Has support branches ● Has its own git extensions ● Is this making life simpler?
- 5. Complexity ● Engineers just enjoy making stuff ● Complexity makes us feel stupid ● We make mistakes ● We lose confidence ● We fight over “unicorn policies” ● Outcome: projects that don't scale
- 6. The Git Complexity Bomb ● Branching is a poor solution for poor processes ● Complexity oriented design & trash oriented design ● The process becomes harder to fix ● You can't fix just part of this picture ● Defusing the bomb needs a holistic intervention
- 7. Simplicity Some quotes from my favorite author: ● “Simplicity beats functionality, every time” ● “If you can't understand it on a cold Monday morning before coffee, it's too complex!” ● “Design by removing problems, not adding features”
- 8. Simplicity Oriented Design ● Small patches to precise problems ● Fork + pull request for every single patch ● Contributor-maintainer ping-pong ● Accuracy over speed ● Community over code ● Bundled up as C4.1 protocol
- 9. In Practice ● Development repo has 1 branch = master ● Pull requests always applied to master ● Travis CI for builds & regression tests ● Stable releases are forked off ● Cherry pick fixes from master to stable
- 10. Branches vs. Forks ● How complex is the organization? ● What's the change latency? ● What is the learning curve for newcomers? ● How many ways can we screw up? ● How much upfront coordination do we need?
- 11. Branches vs. Forks ● Who owns what we make? ● Can our agreements survive arguments? ● How safe is my code from your errors? ● How visible is this project? ● How large can the project scale?
- 12. Does it work? ● We switched ØMQ in Dec 2011 after much talk ● Initial reactions: mixed and apprehensive ● After 18 months, ~70 contributors (from 2-3) ● Dev master is perfect most of the time ● Community is happy, and we use this widely ● Easy to learn, and smooth to drive
- 13. Conclusions ● Git branches are part of a “complexity bomb” that may be damaging your projects ● By switching to a better development process you eliminate the need for branches ● The result is a simpler, kinder Git that is much easier to learn, and safer to use ● And that gives you larger, more successful projects
- 14. If you want to try this ● Read C4.1 (rfc.zeromq.org/spec: 22) ● Look at a project that uses it ● Read my “ZeroMQ” book (O'Reilly), Chapter 6
- 15. Thanks! ● See you here tomorrow at 12pm for an explanation on how we're doing security for ZeroMQ ● Email me: [email protected] ● Twitter: @hintjens ● Blog: hintjens.com