Merken

Pull Requests: Not Just For Code Anymore

Zitierlink des Filmsegments
Embed Code

Automatisierte Medienanalyse

Beta
Erkannte Entitäten
Sprachtranskript
well that's started a couple people come later again welcome takes a commitment talk this is Paul requests not just for Cody anymore my name is tim criteria probably figured out by now that I'm not in fact American from Portland Oregon he may have heard of our trail I think it's kind of famous solicitors in the US maybe not here Oregon trail period anyone this is a little bit again in Portland I worked for a year like
we do application performance management and staff for analytics lots of data about how applications the working with web applications mobile application that sort of thing specifically I am a manager for the new relic rpm team the Ruby agent so if you're Ruby developer and you wanna talk performance and having to do that I also have some new stickers you're welcome to come about the talking yet 1 whether or not you want have a conversation that took a disastrous there that's fine and it's very trendy these days to put your Twitter handle slides on a mission to very suddenly so you won't have to worry too much about it but I treat going to conferences as a very cost inefficient weighted by Twitter followers so that you can follow me and we can justify the cost that so this talk starts off with that story and I hope this story translates to the culture here it certainly is a common story in American companies you're sitting at your desk Monday morning have your coffee opening imperial because it's Monday at you 8 9 A. M. but already you have you know waiting for you and you get a message like this hello everyone effective immediately all extends reports will printed and have physical paper receipts attachment file thank you can imagine and you're thinking to yourself this is another change to a processor doesn't make a whole lot of sense seems to have a lot of inefficiency wire moving paper around there's no explanation there's no discussion so you think OK what and about 30 minutes later you get another you know to respond to the 50 people who replied to my earlier messages the reason I receipts is to verify that the expense total that this is important to make sure financial statements are correct OK fine no problem 3rd lady another e-mail some people have asked of the consensus scanned the receipt and submit the report electronically we don't have any way of doing that it probably wouldn't pass on so please print them and this is where you start introducing the head to the deaths that those factors this is very common this happens for also all the time for all sorts of reasons companies organizations even open source projects messages like this come from accounting from your office manager Assistant from your CTO from the project maintainer whatever it's common but I think it's really really bad for a couple reasons it's a bad kind of surprised you don't know some of this this is coming this is a like 0 this is great news now this is more inefficiency more work there's no explanation there's no reason it seems to be indicative of a good example of this is like a company dress code it's very very common at least in the US here to for companies to declare a company-wide dress code instead of just talking privately to the 1 person who needs to change how they dress in the office so for everyone else it's just unnecessary noise there's no ownership of transparency there's no insight as to why actions are being taken what alternatives were considering that sort of thing so I think there's a couple reasons why this happens and
and a lot of research on how small groups operate you're probably familiar with Robin Dunbar Dunbar's number word of paper in 1992 while at University College London and describe the limits in the average primate group size caused by the size of the neo cortex in the brain so he
came up with this number will be when they come to understand is that humans can associate closely with more than Dunbar's number of 150 people what an organization or company or even an open source project gets more than 150 members the death of your social relationships will drop this is when you start feeling like I will this is a big group now I don't even know who any of these people are in groups over the size limit this sort of bureaucratic top-down process will grow and and have more the reason is that of a gas said earlier direct follow-up is hard the rules are easy it's much harder to have an uncomfortable conversation with someone then it is to send out an e-mail to everyone and not have to deal with problems directly but really I think the reason why this happens is because you allow it to happen so it will about how to make that happen this is what I think of when I think of company or organization or open-source culture and culture I think is really important actually budgets of ODP shall formally Opscode so that organizational culture that makes productive systems not 10 x developers bad culture ruins good people so again bad culture ruins good people and I think culture is really important and divided into 2 on separate categories there's explicit culture and implicit culture explicit culture are things that are written down things that everyone can understand cause it's written down it's clear if well documented axles is way more important implicit an implicit culture is things just happen you don't know what is going to happen you just it just shows up 1 of the most important things I hope you take away from this talk is that X explicit culture is absolutely more powerful than implicit culture this was a culture gives you clear expectations if things are written down in clear people know what consequences their actions might have good or bad was a culture gives you faster onboarding implicit culture takes a really long time to learn often you what discover and detail of the culture and tell you make a mistake or you do the thing that you were supposed to do with X was a culture you can learn ahead of time what you should and should be doing and avoid the mistakes I also think explicit culture gives you much greater accountability if you share with the standards are and document and you can allow everyone to hold each other accountable to the standards this is really really impossible with an implicit culture if nothing is written down there's no standard you can have any sort of accountability I also think with explicit culture you have an opportunity to show your work you can document thought process history that explains the way things are there's a difference between here's what we do and why verses it's always been this way no 1 knows why justice for tackling about how to build explicit culture another code I love the biggest way you can't because we can build this explicit culture your your company organization project reinforce the value of non productive activities that enhance culture stop treating these activities as non-productive because they are very very very productive it may not be writing code but it's really important you come up with these artifacts when you're talking about explicit culture this can be the corporate stuff mission statements corporate values things like that these may or may not actually be reflected in the day-to-day operations of the company but it can also be a lot more interesting than that I think you can do
things like valves new Handbook for employers have you seen this is a one page to this yet it's a very interesting and entertaining read even if you don't work and it's a really really powerful recruiting tool this has gotten out to the public and people read this and say well I wanna work for this company another example Netflix's culture slide that this was widely circulated a few years ago this step was kind of aspirational open they were quite where they said they wanted to be but it but it made a clear message of who they wanted to be internally and externally
hopefully you may now explicit culture really important let's talk a little bit about how to build it hopefully you don't know that like this with the committee full of dozens of people meeting every week or every 2 weeks to do things I think this is really terrible please don't do this it's very very cumbersome it's very slow it consumes a massive amount of time and you're probably going to get the wrong people in the room you probably won't have people with the proper authority to decide what the culture should be so everyone waste their time producing a bunch of stuff that followed now a lot of companies use wikis for the sort of thing you might have an internal wiki we you can write things that we is OK it's not good it's not that I think there's 2 big problems with which 1 is that it requires boldness for editors when you make an edit to weak usually live right away which means you have to be pretty confident the year and it is correct this sort of culture stuff it's not always easy to get right the 1st time it's better to have more discussions it's really hard how productive and will contain discussion on we now of course you know from the topic that the title of this talk where this is going we figured this out a long time ago in open source if you keep your processes and culture documentation in markdown files or HTML or something like that in get everybody you can leverage some really really helpful features using poor quest for request to some really pretty great things actually you have a nice system for notifications people can watch the repo for notifications on every pull request that they really care about company culture or they can just subscribe to individual things that they can don't care about everything you can also tag people who you know what a given put on the page you know that Bob really cares about this topic tagging and so you can see the process happening yeah integrated support for tracking a conversation including automatically hiding out notes on out of the content this is incredibly helpful for discussing process documentation because anything that's changed gets hidden right away the discussion of something you've already passed book Don you can also use built-in labels feature for workflow management of shoulder example of that later and assign URIs to people using science field to make it clear who owns a proposed change was actually responsible for reviewing this and unchanging this really gets
awesome if you get pages because then you can turn your mark files into an actual static website they can be browsed easily by anybody whether or not they understand again works using get of enterprise you can even do this behind a firewall protected content this has a really a great number of advantages over publishing the content in the CMS or by pushing static files themselves not any service to manage you don't have to wait for someone to come around and applied code and there's no CMS
to keep up-to-date with security patches thinking about spammers so this isn't just a theoretical idea for me were using this exact model internally and you for several really really important pieces of our explicit company culture
1st off there's what we call our processes pp these are attempts to comprehensively document what it means to work in engineering and the full technical details of every single job is in you not like not yet anyway but we have information on the overall development processes details like expense reports and hiring taking time and even a collection of random knows that we think are important details of our company culture like the fact that you're not allowed to you before this was around you would learn that ruled by breaking it someone would could tell you had don't do that now we have a written down here people can read it right away and understand the processes pages have been such a success we've already started we also started using different pages and pull request to manage overall architecture of the company the software architecture we've adopted a system of numbered architecture notes very similar to RFC process which eventually this is work really really well we have dozens of architecture notes this is just a few only the stages and and and and we've also started using markdown files and pull request to track the specks of how all 7 of our language agents we have like we have agents that in Ruby in PHP and Java and that that all of those how close a bar server monitoring agent we we we specified how they should behave how they form and data how they interpret configuration values and so on this report doesn't have that pages because we know only software engineers are looking at the people who actually working on the but we do make extensive use of labels as you can see here to track which genes have approved the specs so we know when they're ready to merge teams are responsible for coming in and putting a label on the PR when they read and approved it and the content changes they can take a little off again until they had a chance to review so our
company validated nodes fears and data on how it's going since July 2014 about 13 4 months 214 pull requests in our processes rebuilt from 48 different people the most common we had a single PR was 40 which is not that architecture has only been around for 5 months at 137 pull requests from 32 contributors we had 129 comments on a single if you're wondering what 129 comments looks like it looks like this that and this is even higher than the ones that run out of the content if you're wondering what we were talking about is to discuss the list of approved programming languages for new projects not not surprisingly people have a lot of feelings about this topic so I wanna wrap a rope with the formal presentation I have a lot of time for questions that I know people might have some uninhabited taken I wanna share some of the things we learned by doing this the company maybe you can take this process back to your company organization or project and implement it to the
1st thing we learned is that it can be really hard for non-technical people we are familiar with this this is the Gibbs Random man page generator just the use of a bunch of words that sound sort of like the documentation so you can use this command to gain a non-specified downstream changes over the fastest Portinari set on stage stashes obviously now costly if you familiar with you can recognize this is nonsense emission of sense but if you're not familiar with it just looks an awful lot like the the real documentation it's very very complicated that the 2nd
lesson we learned is that developers loved by chance this is a common term here you know function in book so it's a it's from a British scholar of public administration you noticed that a committee was formed to approve plans for nuclear power plant and they spend the majority of their time discussing the materials for this application rather than discussing how the plant should actually designed because it's so that everyone can understand how to build should but nuclear power plants are actually kind of hard and a complicated and are discussed the other thing we learned is they can generate a lot of e-mail spam so you should be prepared with people to do filtering rules I I I talk a little about all the subscription options and managing that and being thoughtful of peoples set up to go goes a long way to get by and on this process I also think it's really really important to encourage action when you 1st implant this process people are going to comment on the very get excited they're going to get all this this is request I care about model common what's better than the comment is a instead of saying I think it should be about have somebody come and say what's your actual idea right inevitable request so we can talk about the this takes a lot of like careful practice and an encouragement to be able to say it's OK openable request will talk about rather than just making suggestions or even pointing out that pursuant point 96 6 with merge rights comes merge responsibility Pr sitting open for weeks on end will kill any enthusiasm people have around this work very quickly it's natural to want your leadership to be the 1 who were injured emerging things they need to make time to actually do it and things just sit for days and days and days people will lose interest really really fast I also think it's important to make clear that it's not a democracy but open source is needed that's OK we noticed quickly that this process much like most open source projects moves best when it's not a democracy build share motivation input and trust from people and build consensus but at the end of the day the majority opinion doesn't always win and that's OK that I think the bonsai tree is a really good metaphor for how that should work you have 1 or maybe 2 or 3 4 caretakers whose job it is to let things grow organically but once in a while there's a bit of careful delicate trimming to be done redirecting and unproductive conversation making concrete decisions on areas where there is a consensus and that sort of thing it's also important I think today to deal with entropy in a processes things get old and out of date really really really quickly you should designate 1 or more people as entropy fighters and empower them and give them the job of going through and updating a removing things that out of date on a regular basis to keep things fresh otherwise it just sits there gets old and 2008 so where are
the only ones who have figured out this process the following in the United States government which is well known for being a wretched hive bureaucracy is on this this is that the Torah project the Federal Information Technology Acquisition Reform Act which was passed by Congress is essentially guidance for the US federal government of how IT project should be run can you imagine a more a concrete example of bureaucracy and that sort of thing but as it turns out the table requests a US representative from Virginia opened up all request a congressman openable request against Israel and has a more it was a huge for request but it did have some interesting ramifications I think this is also something is really really really cool I hope it spread throughout the rest of how the government of the war it doesn't work so let's go back to the
story at the very beginning of my talk and see how it could have done a bit differently and we get this whole request model place are county
manager open pull request against our processes already this is a little bit better we have a y attached to this from the 1st moment to help explain the change were concerned the previous process will pass on its so now requiring paper received to be submitted along with paper expense reports there is an immediate opportunity for comment someone asks if we can use I'd ask ready to support add support for existing electronic system for receipt images accounting managers able to respond in line to say a scanned copy receives fine they update the pool contents of the was with new newcomer again emerged this is idea to work all the time as we have
today I'm happy to take any questions of anyone has some I allotted time so feel free yes it is not a democracy the without democracy worker it was I think you know the democracy of the employees of a company my want something to be a certain way but the leadership might say you know that's not actually direction that we have we wanna go this way and I you know it's it's a little bit much to perhaps a mark procedures that when but just because 40 people want to be with this way and 38 wanted to be that way doesn't mean it has to be this way there's still decision it's very much similar to open source although in open source you can for going to things like that yeah all all the manager that generic work so for the purposes of by stores for a while of the winter time but if is not idea each the answer really is reacting very simple just markdown file 2 text files that have the continent marked is very easy syntax to learn anyone who's non-technical can understand very quickly Hadamard things that make lists links that sort of thing we use HTML 4 things that need but this is 1 of the things we know and so this is my little sample you can see it so well trained so this is the this is I actually wrote this out for the purpose of the minimum it can be that simple that market doesn't have to be very complicated for pages that need it we use HTML we need big table that sort of thing but market actually really really great that rdf yet so that will also it gives you all the at all so you know the all of you
yeah we haven't we haven't had any actually distorted documents everything gets translated in the variational are marked on that would be a nice diffs amounts the questions that the hand over here that all right the right of the all of the and on yet but yeah that's a great point I'll repeat for the for the recording and dealing with colleagues who purposefully hide their work in progress until it's done so that the the PNA gallery doesn't waiting constantly we had that issue a couple times people people get in these early in 1 at work on things but we've also found that sometimes the 1st draft is authored by a small group of 3 or 4 people who come together for an afternoon and write something put it together that way you get at least some of the initial round of Guinea gallery out of the way it's a little bit I wish there was a better way to do attribution for multiple authors so that they we get credit for their work someone has to be the person who made the comment fortunately but we knew that a couple times for things that are very complicated bringing grouped together just for a short amount of time to come up with the 1st draft put it up and then go from there I think that anything that's an OK way to do that this this process scaled down I think so the age of suspects that example measure it affects the number of developers who really way in that is around and so on so I I can't say that I've seen it work 1st from less than 10 but i think for a group that's what we've been able to work is it really well we used to do with the prospects but he got very very confusing very quickly because it was difficult to keep the old revisions tag them in the of course wiki has a full history but which is the exact version that was implemented by the state and this time using the RFC numbering system we're able to say OK were implementing expect 18 and maybe spec 18 gets replaced later with spectrally 5 or you know what 18 was and you have that linking simply this version was on 18 in this region around 25 and I think that's I think that's important I think it can skeletal because the reason why not this just like a lot of you I think that when was thing would it work for things like you I decide that I'm not sure about I think you'll be difficult without finding a format that you could use that's easily comprehensible and I guess you could put PSD is but an entire opening binaries and yet it's the not it's not very good so I give you I think if he did some work and you thought about how you doing here you as I mean it is just because I then computing for a long time and I remember the good old days of is but I love last year do you realize it last year for a little bit until you get down the road a little bit maybe even pretend that way and do this share that 2 of the the until the generate the you the you from a text file a language of the book by the gap what these have another on get let's server that's a very good question I'm actually not sure of the reason we use get have enterprise that the relic so we have an internally hosted version but I suspect it's mostly just for familiarity and did lab is not very popular among US companies were as everyone knows that he is given so I think there's just a little bit less transition costs of getting on board at that the theory that I'm not sure yet the yeah yeah I think I think there's an there's an advantage for us you know our are competitive advantage is not in our source control it's in our software that we right so letting someone else worry about that and they provide the patches and all we have to do is provide a server and it's taking care of I think this is now the yes I know give lenders for class it back it does for class I think most of the had repositories these days will support this kind of model may be the different features and that's pretty pretty similar yeah I want at the end the how do we get
non-technical people to understand that the topic of all of the time but I think there's there's there's 2 ways of 1 is scary working with someone who wants to make a change in giving them some education we teach people they're usually willing to learn there's a lot of great clients out there the other way is actually did have ended up enterprises well has a built-in editor so you can click edit on most files and get an editor then if you using marked down there's no code is just the text and that walks you through the process of pushing a committee an opening a branch of making fork and all that stuff so if you show someone OK where to learn a little bit your example and again have interface but then when you click on it OK had the following makes sense and then when he had say there's all these weird terms and understand but the bottom but most of a force and and in works so that's we we've had some success so that I wouldn't say it's perfectly but I I do feel very strongly that setting up given pages so that things are served in a way that's that's attracted people can just browse to Europe is really really important because even if people are willing to enter the because these findings you easily assuming you have non-technical people reading it it's just engineers then you don't need yeah we are working on a lot of work on the right yeah it's at the boundary with they're willing to do but it's working OK I so before my current job I worked running Drupal development team so I've trained many many many people had editable documents I don't think it's that much more complicated than Drupal is so as I text yeah once you once you get to the text everything is good but not yet that's a so the question is how hard is it to convince the bosses to change the workload and the answer is it actually came from the Boston so it's very easy but yeah RSVP of engineering was the garden of the Rico he has the majority decides what makes it and what doesn't and this is something you know I'm talking about it but it was his idea so you you credit of your enough freedom events and came up with Canada's model and really push it hard but he's also been able to assess the the way to like the agent specs example is that that's all that's all we just do that ourselves different time here the diameter of 5 minutes and questions yes but the how do we decide to use the image right that's a good question and it depends on the project that you're talking about for processes that goes through every piece has this interchange job process they're the ones who murdered now that said they merge most of what comes through that has consensus but once in a while something gets kicked out for the architecture notes we have an architecture team of principal engineers who share that responsibility and each 1 of them will connect captain a pull request and say OK I'm responsible for this area that area this area for the agents specks there really isn't any 1 we haven't you we have a director of engineering but she is really worry as much about how specs work that's more peer based so what we've come up with their is we have a time based system when I open a PR gets that I say Amen emerge this in 3 days most anybody has a question or extend the time happily but if nobody has any feedback it's getting words that's what's happening so we we biased towards merging in moving forward rather than waiting for common what about the the yeah surprise prior programming prior to the system yeah so and the process is used to be a Word doc that was the employee handbook and a lot of stuff that's not very pertinent to engineering and a lot of it was missing a lot of things that we have and I think that's pretty common for most companies specs and technical documentation we had a we had a confluence of we about seeing complements and we still use that for a lot of things but for things like specifications like I said earlier we he's not great if you make a change it's done the changes done there's no period for comments or questions are like is there so you have to do a lot more work offline to socialize changes and make sure everything's good whereas with the system you just take the people alright thank you very much that's what I have really haven't thought about this more of your mother or argues that as well thank you
Offene Menge
Freeware
Software
Bit
Weg <Topologie>
Code
Vorlesung/Konferenz
Frequenz
Hinterlegungsverfahren <Kryptologie>
Computeranimation
Umsetzung <Informatik>
Total <Mathematik>
Selbst organisierendes System
Stab
Gruppenoperation
Physikalismus
Web-Applikation
Hochdruck
Mathematisierung
Gruppenkeim
Zahlenbereich
Geräusch
Kartesische Koordinaten
Analytische Menge
Code
Datenmanagement
Mittelwert
Inverser Limes
Äußere Algebra eines Moduls
Vorlesung/Konferenz
Verband <Mathematik>
Coprozessor
Softwareentwickler
E-Mail
Schreib-Lese-Kopf
App <Programm>
Befehl <Informatik>
Open Source
Elektronische Publikation
Teilbarkeit
Quick-Sort
Office-Paket
Rechenschieber
Softwarewartung
Twitter <Softwareplattform>
Wort <Informatik>
Projektive Ebene
Message-Passing
Verkehrsinformation
Umsetzung <Informatik>
Subtraktion
Prozess <Physik>
Selbst organisierendes System
Gruppenoperation
Gruppenkeim
Zahlenbereich
Code
Homepage
Erwartungswert
Inverser Limes
Vorlesung/Konferenz
Softwareentwickler
E-Mail
Leistung <Physik>
Nichtlinearer Operator
Befehl <Informatik>
Kategorie <Mathematik>
Physikalischer Effekt
Open Source
Güte der Anpassung
Schlussregel
Physikalisches System
Biprodukt
Quick-Sort
Rechenschieber
Projektive Ebene
Message-Passing
Lesen <Datenverarbeitung>
Standardabweichung
Autorisierung
Web Site
Bit
Umsetzung <Informatik>
Prozess <Physik>
Firewall
Open Source
Mathematisierung
Zahlenbereich
Ruhmasse
Physikalisches System
Wiki
Elektronische Publikation
Code
Quick-Sort
Homepage
Texteditor
Dienst <Informatik>
Datenmanagement
Datenfeld
Canadian Mathematical Society
Vorlesung/Konferenz
Inhalt <Mathematik>
Unternehmensarchitektur
Repository <Informatik>
Subtraktion
Prozess <Physik>
Computersicherheit
Mathematisierung
Formale Sprache
Applet
Physikalisches System
Elektronische Publikation
Homepage
Patch <Software>
Informationsmodellierung
Prozess <Informatik>
Softwarearchitektur
Server
Vorlesung/Konferenz
Information
Computerarchitektur
Maßerweiterung
Softwareentwickler
Konfigurationsraum
Software Engineering
Verkehrsinformation
Programmiersprache
Prozess <Physik>
Gemeinsamer Speicher
Selbst organisierendes System
Mathematisierung
Mailing-Liste
Kombinatorische Gruppentheorie
Eins
Knotenmenge
Reelle Zahl
Vorlesung/Konferenz
Wort <Informatik>
Projektive Ebene
Computerarchitektur
Umsetzung <Informatik>
Prozess <Physik>
Punkt
Gemeinsamer Speicher
Selbstrepräsentation
Gruppenoperation
Automatische Handlungsplanung
Kartesische Koordinaten
Term
Eins
Netzwerktopologie
Informationsmodellierung
Prozess <Informatik>
Endogene Variable
Vorlesung/Konferenz
Softwareentwickler
E-Mail
NP-hartes Problem
Lineares Funktional
Materialisation <Physik>
Pay-TV
Open Source
Gebäude <Mathematik>
Systemverwaltung
Schlussregel
Ein-Ausgabe
Quick-Sort
Entscheidungstheorie
Konfiguration <Informatik>
Flächeninhalt
Offene Menge
Rechter Winkel
Basisvektor
Verzweigungspunkt
Projektive Ebene
Entropie
Tabelle <Informatik>
Informationsmodellierung
Bit
Datenmanagement
Prozess <Physik>
Momentenproblem
Offene Menge
Mathematisierung
Vorlesung/Konferenz
Inhalt <Mathematik>
Gerade
Verkehrsinformation
Bildgebendes Verfahren
Bit
Prozess <Physik>
Punkt
Extrempunkt
Gemeinsamer Speicher
Formale Sprache
Versionsverwaltung
Gruppenkeim
Schreiben <Datenverarbeitung>
Binärcode
Richtung
Homepage
Datenmanagement
Vorlesung/Konferenz
Einflussgröße
Dokumentenserver
Güte der Anpassung
Wiki
Algorithmische Programmiersprache
Entscheidungstheorie
Rechter Winkel
Server
Dateiformat
Hadamard-Matrix
Tabelle <Informatik>
Aggregatzustand
Subtraktion
Gruppenoperation
Klasse <Mathematik>
Zahlenbereich
Unrundheit
Physikalische Theorie
Multiplikation
Informationsmodellierung
Datensatz
Arithmetische Folge
Software
Stichprobenumfang
Speicher <Informatik>
Softwareentwickler
Ganze Funktion
Attributierte Grammatik
Autorisierung
Open Source
Mailing-Liste
Binder <Informatik>
Elektronische Publikation
Quick-Sort
Patch <Software>
Offene Menge
Verzerrungstensor
Unternehmensarchitektur
Rückkopplung
Bit
Prozess <Physik>
Mathematisierung
Code
Homepage
Eins
Informationsmodellierung
Client
Hauptideal
Konfluenz <Informatik>
Prozess <Informatik>
Minimum
Endogene Variable
Vorlesung/Konferenz
Softwareentwickler
Bildgebendes Verfahren
Schnittstelle
Umwandlungsenthalpie
Durchmesser
Güte der Anpassung
Verzweigendes Programm
Physikalisches System
Frequenz
Ereignishorizont
Beanspruchung
Texteditor
Forcing
Flächeninhalt
Benutzerschnittstellenverwaltungssystem
Rechter Winkel
Wort <Informatik>
Projektive Ebene
Computerarchitektur
Unternehmensarchitektur
Offene Menge
Freeware
Software
Computeranimation

Metadaten

Formale Metadaten

Titel Pull Requests: Not Just For Code Anymore
Serientitel FrOSCon 2015
Teil 14
Anzahl der Teile 80
Autor Krajcar, Tim
Lizenz CC-Namensnennung 3.0 Unported:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
DOI 10.5446/19620
Herausgeber Free and Open Source software Conference (FrOSCon) e.V.
Erscheinungsjahr 2015
Sprache Englisch

Inhaltliche Metadaten

Fachgebiet Informatik
Abstract Many companies have copied the fork-and-pull-request model from open source because it works so well, even for closed-source projects. So why are company processes and policies written in isolation with no collaboration? I'll present New Relic's implementation of an open-source-inspired workflow that drives all of our internal company processes. Tim Krajcar

Ähnliche Filme

Loading...