<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The Varnish Developers Guide on Varnish Cache</title><link>https://example.org/docs/dev-guide/</link><description>Recent content in The Varnish Developers Guide on Varnish Cache</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 24 Feb 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://example.org/docs/dev-guide/index.xml" rel="self" type="application/rss+xml"/><item><title>Bundling VMODs with the Varnish distribution</title><link>https://example.org/docs/dev-guide/bundling-vmods-with-the-varnish-distribution/</link><pubDate>Wed, 24 Feb 2021 00:00:00 +0000</pubDate><guid>https://example.org/docs/dev-guide/bundling-vmods-with-the-varnish-distribution/</guid><description>&lt;p&gt;Decisions about whether to add a new Varnish module (VMOD) to those
bundled with Varnish are guided by these criteria.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The VMOD is known to be in widespread use and in high demand for
common use cases.&lt;/li&gt;
&lt;li&gt;Or, if the VMOD is relatively new, it provides compelling features
that the developer group agrees will be a valuable enhancement for
the project.&lt;/li&gt;
&lt;li&gt;The VMOD does not create dependencies on additional external
libraries. VMODs that are &amp;ldquo;glue&amp;rdquo; for a library come from third
parties.
&lt;ul&gt;
&lt;li&gt;We don&amp;rsquo;t want to add new burdens of dependency and compatibility
to the project.&lt;/li&gt;
&lt;li&gt;We don&amp;rsquo;t want to force Varnish deployments to install more than
admins explicitly choose to install.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;The VMOD code follows project conventions (passes make distcheck,
follows source code style, and so forth).
&lt;ul&gt;
&lt;li&gt;A pull request can demonstrate that this is the case (after any
necessary fixups).&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;The developer group commits to maintaining the code for the long run
(so there will have to be a consensus that we&amp;rsquo;re comfortable with
it).&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>How our website works</title><link>https://example.org/docs/dev-guide/how-our-website-works/</link><pubDate>Wed, 24 Feb 2021 00:00:00 +0000</pubDate><guid>https://example.org/docs/dev-guide/how-our-website-works/</guid><description>&lt;p&gt;The principle of eating your own dogfood is important for software
quality, that is how you experience what your users are dealing with,
and I am not the least ashamed to admit that several obvious improvements
have happened to Varnish as a result of running the project webserver.&lt;/p&gt;
&lt;p&gt;But it is also important to externalize what you learn doing so, and
therefore I thought I would document here how the projects new &amp;ldquo;internal
IT&amp;rdquo; works.&lt;/p&gt;</description></item><item><title>How to contribute content to varnish-cache.org</title><link>https://example.org/docs/dev-guide/how-to-contribute-content-to-varnish-cache-org/</link><pubDate>Wed, 24 Feb 2021 00:00:00 +0000</pubDate><guid>https://example.org/docs/dev-guide/how-to-contribute-content-to-varnish-cache-org/</guid><description>&lt;p&gt;This is where we walk you through the mechanics of adding content to
varnish-cache.org (see phk&amp;rsquo;s note &lt;code&gt;homepage_dogfood&lt;/code&gt; for an
insight into the innards of site).&lt;/p&gt;
&lt;h2 id="git-repository"&gt;Git Repository&lt;/h2&gt;
&lt;p&gt;The web site contents live in github at:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/varnishcache/homepage"&gt;https://github.com/varnishcache/homepage&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;To offer your own contribution, fork the project and send us a pull
request.&lt;/p&gt;
&lt;h2 id="sphinx-and-rst"&gt;Sphinx and RST&lt;/h2&gt;
&lt;p&gt;The web site sources are written in &lt;a href="http://docutils.sourceforge.net/rst.html"&gt;RST&lt;/a&gt; &amp;ndash; reStructuredText, the
documentation format originally conceived for Python (and also used in
the Varnish distribution, as well as for formatting VMOD
docs). &lt;a href="http://www.sphinx-doc.org/"&gt;Sphinx&lt;/a&gt; is used to render web
pages from the RST sources.&lt;/p&gt;</description></item><item><title>Who is ... ?</title><link>https://example.org/docs/dev-guide/who-is/</link><pubDate>Wed, 24 Feb 2021 00:00:00 +0000</pubDate><guid>https://example.org/docs/dev-guide/who-is/</guid><description>&lt;p&gt;Not quite &lt;a href="https://wiki.lspace.org/mediawiki/Twurp%27s_Peerage"&gt;Twurp&amp;rsquo;s Peerage&lt;/a&gt; but a Who&amp;rsquo;s Who of the Varnish Cache project.&lt;/p&gt;
&lt;h2 id="anders-berg"&gt;Anders Berg&lt;/h2&gt;
&lt;p&gt;Blame Anders! He is the one who got the crazy idea that the world
needed another HTTP proxy server software, and convinced his employer,
the norwegian newspaper &lt;a href="http://www.vg.no"&gt;Verdens Gang&lt;/a&gt; to pay for the
first version to be developed.&lt;/p&gt;
&lt;p&gt;Here is an interview with Anders about &lt;a href="http://info.varnish-software.com/blog/celebrating-10-years-of-varnish-cache-qa-with-the-man-behind-the-idea"&gt;how it all began&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="dag-erling-smørgrav"&gt;Dag-Erling Smørgrav&lt;/h2&gt;
&lt;p&gt;DES was working at Redpill-Linpro, a norwegian UNIX/Open Source company
when Anders floated his idea for a &amp;ldquo;forward HTTP cache&amp;rdquo;, he lured PHK
into joining, was one of the original developers (doing Linux), project
manager and release engineer for the first three years of the project,
and forced us to adopt a non-US-ASCII charset from the start.&lt;/p&gt;</description></item></channel></rss>