<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Markus Latzel</title>
    <description></description>
    <link>https://speakerdeck.com/mlatzel</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/mlatzel.rss"/>
    <lastBuildDate>2016-11-07 09:38:10 -0500</lastBuildDate>
    <item>
      <title>Pushing Git Where It Doesn't Belong</title>
      <description>In this talk, I present our approach to using Git in an environment where it conceptually does not belong: Business Operations. 

As a custom CMS provider, we asked ourselves: could we somehow force communication officers, marketing gurus, bloggers and content editors to fall in line with our PHP coders and adhere to common version control principles? And if so, what would we gain? Would we find a stream of seamless pull requests, or a never-ending disaster of merge conflicts, blames, and end-user frustration?

 I will share how we saw a bit of both, describe challenges of managing content like code, and our approaches for integrating Git with a powerful XML/XSLT templating engine. 

But also, I hope to discuss the enormous gains that can be achieved when mapping DevOps processes onto the business world.

</description>
      <media:content url="https://files.speakerdeck.com/presentations/9b9300ac12ce44acba7118522d8b0352/preview_slide_0.jpg?7136648" type="image/jpeg" medium="image"/>
      <content:encoded>In this talk, I present our approach to using Git in an environment where it conceptually does not belong: Business Operations. 

As a custom CMS provider, we asked ourselves: could we somehow force communication officers, marketing gurus, bloggers and content editors to fall in line with our PHP coders and adhere to common version control principles? And if so, what would we gain? Would we find a stream of seamless pull requests, or a never-ending disaster of merge conflicts, blames, and end-user frustration?

 I will share how we saw a bit of both, describe challenges of managing content like code, and our approaches for integrating Git with a powerful XML/XSLT templating engine. 

But also, I hope to discuss the enormous gains that can be achieved when mapping DevOps processes onto the business world.

</content:encoded>
      <pubDate>Sat, 05 Nov 2016 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/mlatzel/pushing-git-where-it-doesnt-belong</link>
      <guid>https://speakerdeck.com/mlatzel/pushing-git-where-it-doesnt-belong</guid>
    </item>
  </channel>
</rss>
