<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>writing on Tim Shadel</title>
    <link>https://www.timshadel.com/tags/writing/</link>
    <description>Recent content in writing on Tim Shadel</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    
	<atom:link href="https://www.timshadel.com/tags/writing/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>O&amp;#8217;Reilly changing its process?</title>
      <link>https://www.timshadel.com/posts/craftsmanship/2003-12-29-oreilly-chaning-its-process/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://www.timshadel.com/posts/craftsmanship/2003-12-29-oreilly-chaning-its-process/</guid>
      <description>I touched on O’Reilly’s publishing process in this post a little while ago, but I found an interesting note in James Duncan Davidson’s blog about his latest O’Reilly publishing experience. It will be interesting to watch how this type of work progresses.</description>
    </item>
    
    <item>
      <title>Refactoring the Publishing Process</title>
      <link>https://www.timshadel.com/posts/craftsmanship/2003-12-23-refactoring-the-publishing-process/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://www.timshadel.com/posts/craftsmanship/2003-12-23-refactoring-the-publishing-process/</guid>
      <description>Erik Hatcher and Steve Loughran mention a future paper I’d really like to read in this excerpt of antbook-update.pdf (application/pdf Object)
 Some day soon we will explain how the book was done, and how books could be done better in future in a little paper, Refactoring the Publishing Process [4]. For now, key points are:
 CVS server on a Redhat 7.1 system, “eiger” in the home DMZ. Home stateful firewall (WebRamp) set to allow port 22, ssh through.</description>
    </item>
    
  </channel>
</rss>