Commits

Alex Clark committed c30f84c

Remove warnings for :alt: alternate text

Comments (0)

Files changed (104)

2008/04/18/help-me-upgrade-ploneorg/index.html

 </ul>
 <p>Now without further ado, please donate-away! :-)</p>
 <div class="figure align-center">
-<img alt="" src="https://www.paypal.com/en_US/i/scr/pixel.gif" />
+<img alt="alternate text" src="https://www.paypal.com/en_US/i/scr/pixel.gif" />
 </div>
 
     </div><!-- /.entry-content -->

2009/12/31/new-years-python-meme/index.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->      <img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/lenin_packaging.png" style="width: 100%;" />
+</footer><!-- /.post-info -->      <img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/lenin_packaging.png" style="width: 100%;" />
 <div class="section" id="whats-the-coolest-python-application-framework-or-library-you-have-discovered-in-2009">
 <h2>What’s the coolest Python application, framework or library you have discovered in 2009?</h2>
 <p>That would be <a class="reference external" href="http://zenoss.org">Zenoss</a>. I'm very impressed with the application as well as the community, which is awesome. They remind me a lot of the Plone community; I think the two can learn a lot from each other.</p>

2011/02/16/cioppino-sprint-report/index.html

 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a></p>
 </footer><!-- /.post-info -->      <p>The <a class="reference external" href="http://coactivate.org/projects/snow-sprint-west-2011/project-home">Cioppino Sprint</a> was recently held in Bodega Bay, CA. It was a <a class="reference external" href="http://twitpic.com/3y21yk">beautiful location</a> for a gathering of awesome Plone folks; and much was accomplished. Unfortunately on the second morning of the sprint, we were all deeply saddened to hear about the passing of Dorneles Treméa.</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/bodega.jpg" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/bodega.jpg" />
 <div class="section" id="the-passing-of-dorneles-tremea">
 <h2>The passing of Dorneles Treméa</h2>
 <p>I didn't know Dorneles very well, but he was certainly someone I idolized during my initial Plone fascination days (e.g. &quot;Who are all these cool people with such cool names!&quot;). And after digging through my old emails, I now remember we had several pleasant exchanges over the years.</p>

2012/09/21/gittip-is-the-future/index.html

 </ul>
 </blockquote>
 <p>Why? If for no other reason, because it comes from a member of the Python community: Chad Whitacre of <a class="reference external" href="http://aspen.io">http://aspen.io</a> fame. And the Python community has become near and dear to me, second only to my-one-true-open-source-love: Plone. So I want to see open source developers, particularly Python developers, succeed.</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/gittip.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/gittip.png" />
 <p>And succeed they will, with gittip. Some particularly impressive results so far:</p>
 <ul class="simple">
 <li>Chad Whitacre, the founder, is making almost $160 per week: <a class="reference external" href="https://www.gittip.com/whit537/">https://www.gittip.com/whit537/</a></li>

2012/09/21/yes-this-blog-is-now-powered-by-pelican/index.html

 <p>tags: <a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->      <p>As an open source &quot;Plone guy&quot;, I'm always prepared to defend and explain my choice to <strong>not</strong> use Plone for blogging. A couple years ago, I started using Wordpress in order to learn its feature set. I enjoyed my time with it, but after moving to wordpress.com for &quot;trouble free&quot; hosting, I found I couldn't control my category feeds the way I wanted; the honeymoon was over.</p>
 <p>This was a giant let down, because I was hoping to avoid putting any time in to my blogging infrastructure. For weeks I did nothing. I poked at various options: Pelican, Plone, Tumblr, others. Eventually, I found my way back to Pelican and now I'm happy again.</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pelican.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pelican.png" />
 <p>Pelican is a static blog generator, as you may have heard. So <strong>one big advantage</strong> is:</p>
 <ul class="simple">
 <li>You can host it for free, or close to free on any number of free or cheap static website hosting services! (I'm using GitHub Pages)</li>

2012/09/28/pythonpackages-com-one-year-later/index.html

 <li>The ability to release a package with <cite>git push</cite> (by adding the service: <a class="reference external" href="https://github.com/github/github-services/blob/master/services/pythonpackages.rb">https://github.com/github/github-services/blob/master/services/pythonpackages.rb</a>)</li>
 <li>The ability to &quot;manage packages&quot; (see image below)</li>
 </ul>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/manage-packages.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/manage-packages.png" />
 <ul class="simple">
 <li>The ability to &quot;manage organizations&quot; (see image below)</li>
 </ul>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/manage-organizations.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/manage-organizations.png" />
 <ul class="simple">
 <li>The <a class="reference external" href="http://docs.pythonpackages.com/en/latest/create-package.html#create-packages">ability to create packages through the web</a> (i.e. from the web browser to GitHub, whereas normally you'd run PasteScript in your Terminal).</li>
 </ul>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/create-new-package.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/create-new-package.png" />
 <p>And a few more logistical features that are cool:</p>
 <ul class="simple">
 <li>The ability to pay with a credit card (via Stripe)</li>
 </ul>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pay-with-stripe.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pay-with-stripe.png" />
 <ul class="simple">
 <li>The ability to oauth against PyPI:</li>
 </ul>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pypi-oauth.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pypi-oauth.png" />
 <p>Still, we have only scratched the surface of what could potentially be provided to the Python community. Future plans include:</p>
 <ul class="simple">
 <li>The ability to easily <a class="reference external" href="https://bitbucket.org/pythonpackages/pythonpackages.com/issue/28/build-windows-installers">build Windows installers</a> for your Python software.</li>

2012/10/03/plone-4-3-alpha-1-in-production/index.html

 <div class="section" id="customize-templates">
 <h2>Customize templates</h2>
 <p>As you may have noticed above I use <tt class="docutils literal">z3c.jbot</tt> to customize various Plone templates.</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/custom-templates.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/custom-templates.png" />
 </div>
 <div class="section" id="add-content">
 <h2>Add content</h2>
 <div class="section" id="use-sunburst-theme-for-content-editing">
 <h3>Use Sunburst theme for content editing</h3>
 <p>If you are Diazo-savvy, you may notice I completely ignore styling the content editing interface. Instead I rely on the unthemed <a class="footnote-reference" href="#id5" id="id2">[2]</a> site for content editing.</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/edit-ui.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/edit-ui.png" />
 </div>
 <div class="section" id="use-diazo-theme-for-public-facing-view">
 <h3>Use Diazo theme for public facing view</h3>
 <p>Of course, visitors to <a class="reference external" href="http://aclark.net">http://aclark.net</a> see the Diazo theme.</p>
-<img alt="" src="images/diazo-theme.png" />
+<img alt="alternate text" src="images/diazo-theme.png" />
 <p>I'm hoping that the Plone team can unify the content editing experience again in Plone 5, possibly via simplifying the &quot;old style&quot; templates such that it's easier to map them to custom Diazo themes.</p>
 </div>
 </div>
 </div>
 <div class="section" id="the-all-content-view-is-awesome">
 <h3>The <tt class="docutils literal">All content</tt> view is awesome</h3>
-<img alt="" src="images/all-content.png" />
+<img alt="alternate text" src="images/all-content.png" />
 <p>Contributed by Laurence Rowe for Plone 4, I use the <tt class="docutils literal">All content</tt> view in two places:</p>
 <ul class="simple">
 <li><a class="reference external" href="http://aclark.net/services">http://aclark.net/services</a></li>

2012/10/04/looking-for-projects/index.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a></p>
-</footer><!-- /.post-info -->      <img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/use_python.jpg" />
+</footer><!-- /.post-info -->      <img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/use_python.jpg" />
 <p>With <a class="reference external" href="http://blog.aclark.net/2012/09/28/pythonpackages-com-one-year-later/">pythonpackages.com winding down</a>, I am now actively seeking projects for Q4 2012 and beyond. I am good at:</p>
 <ul class="simple">
 <li>Deploying Plone sites: <a class="reference external" href="http://blog.aclark.net/2012/10/03/plone-4-3-alpha-1-in-production/">http://blog.aclark.net/2012/10/03/plone-4-3-alpha-1-in-production/</a></li>

2012/10/17/top-3-favorite-logical-fallacies/index.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/python.html">Python</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a></p>
-</footer><!-- /.post-info -->      <img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/y-u-no-agree.jpg" />
+</footer><!-- /.post-info -->      <img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/y-u-no-agree.jpg" />
 <p>I love to debate issues. The more complex, the better. I have no formal training in <a class="reference external" href="http://en.wikipedia.org/wiki/Debate">debate</a>, but I wish I did. It may have better prepared me to face different personality types with varying degree of communication skill. You don't have to watch the 2012 U.S. Presidential Debates to know that people will say things that are <strong>BATSHIT CRAZY</strong> to make their point. I've done it myself. That's why we need rules to formalize our discussions, because it's hard to stay on point.</p>
 <div class="section" id="fallacy">
 <h2>Fallacy</h2>

2012/10/17/why-i-criticize-the-plone-foundation-board/index.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/python.html">Python</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a></p>
-</footer><!-- /.post-info -->      <img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/aclark-conf.jpg" />
+</footer><!-- /.post-info -->      <img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/aclark-conf.jpg" />
 <p>TL;DR: Because I care.</p>
 <p>As some of you can probably relate to, I've had my fair share of disagreements with the Plone Foundation Board over the years. The good news is, for the most part, it (just like the community) is staffed with <strong>very reasonable people</strong> who if you push them on an issue, will acknowledge that there are always competing viewpoints to any issue you can think of.</p>
 <div class="section" id="the-fallacy-of-false-cause">

2012/10/19/gittip-misunderstood/index.html

 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->      <p>People do not understand gittip. Or, they do not understand how I use it. Worse, they <strong>think</strong> they understand it <a class="footnote-reference" href="#id2" id="id1">[1]</a>. So much so, some choose to comment about it publicly.</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/condescend.jpg" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/condescend.jpg" />
 <p>Remember <a class="reference external" href="http://blog.aclark.net/gittip-is-the-future.html">gittip is the future</a>? Someone commented:</p>
 <blockquote>
 <p>&quot;Nobody likes a beggar.&quot;</p>

2012/10/20/mailing-list-etiquette/index.html

 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a></p>
 </footer><!-- /.post-info -->      <p>I read a lot of mailing lists:</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/unison.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/unison.png" />
 <p>Also, I've been subscribing to, reading, and participating in discussions on mailing lists since about the time Mailman 1.0 was released circa 1999 <a class="footnote-reference" href="#id3" id="id1">[1]</a>. And I have fond memories of interacting administratively with MajorDomo and ListServ software. And by administratively, I mean sending the software commands and getting back a response. In fact, you might say I get along better with the software and machines than I do with the humans that use them. Which is not to say that I'm not a people person: I love people. But I do struggle with striking the right balance between hacking machines and communicating with humans.</p>
 <p>Anyway, as you can imagine: I have <strong>VERY STRONG OPINIONS</strong> about how folks should conduct themselves on mailing lists: call it a code of conduct. And regardless of what you might expect from a self-described &quot;hack&quot;: I work <strong>VERY HARD</strong> to enforce that code of conduct on my own behavior. Do I occasionally step outside the lines? Of course. But make no mistake: I do not communicate in a vacuum. You can be as polite and courteous as The Pope and <strong>STILL GET THE SMACKDOWN</strong> through no fault of your own. Why? Because humans make mistakes. Context gets lost. Do you think you know what's going on enough to make a comment? You might be wrong <a class="footnote-reference" href="#id4" id="id2">[2]</a>:</p>
 <blockquote>

2012/10/20/review-of-aspelis-professional-plone-4-development/index.html

 <p>First let me cover what I <strong>ABSOLUTELY LOVE</strong> about this book.</p>
 <div class="section" id="buildout-eggs">
 <h3>buildout:eggs</h3>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/buildout.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/buildout.png" />
 <p>Aspeli correctly addresses one of my biggest pet peeves (concerns) about what I believe to be an <strong>ANTI-PATTERN</strong> in almost every Plone buildout: buildout:eggs (referring to the eggs parameter of the buildout section; it does not exist, other than as a convenient variable setting).</p>
 <p>If you know me, you know I've spoken about this before and whilst I've moved on from harping on it I will say this: with most software that uses ini-style configuration files when you set a parameter you expect something to happen. But since Buildout is more complicated than the average software that uses ini-style configuration, that expectation is not always met.</p>
 </div>
 <div class="section" id="add-ons">
 <h3>Add-ons</h3>
-<img alt="" src="image://raw.github.com/ACLARKNET/blog/gh-pages/images/addons.png" />
+<img alt="alternate text" src="image://raw.github.com/ACLARKNET/blog/gh-pages/images/addons.png" />
 <p>Did you see? You might have missed it. No mention of <strong>Products</strong> WHAT-SO-EVER. &quot;Product&quot; was a term that Zope2 used for Python libraries that enhanced the functionality of Zope2, and it stuck. Now, it should die in favor of a term everyone else in the world is familiar with (in this context): add-on. Well played, Aspeli. Well played.</p>
 </div>
 </div>

2012/11/23/plone-guide/index.html

 <div class="section" id="what">
 <h2>What</h2>
 <p>Recently with a tweet, I announced the start of a new personal project:</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/tweet.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/tweet.png" />
 </div>
 <div class="section" id="when">
 <h2>When</h2>
 <div class="section" id="how">
 <h2>How</h2>
 <p>I think a lot about what other people think about Plone, so I decided this book will feature comments from the general public in it. E.g.:</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/comments.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/comments.png" />
 </div>
 <div class="section" id="how-much">
 <h2>How much?</h2>

2012/12/29/new-years-python-meme-2012/index.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->      <img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/tarek-meme-reminder.png" />
+</footer><!-- /.post-info -->      <img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/tarek-meme-reminder.png" />
 <p><em>This is my entry for Tarek Ziadé's New Year's Python Meme, a tradition I have come to enjoy. Both to reflect on the current year and look back on previous years. So here it is.</em></p>
 <p>I did this in <a class="reference external" href="http://blog.aclark.net/2009/12/31/new-years-python-meme/">2009</a> &amp; <a class="reference external" href="http://blog.aclark.net/2011/12/21/new-years-python-meme-2011/">2011</a>. Let's try it again.</p>
 <p><strong>1. What’s the coolest Python application, framework or library you have discovered in 2012?</strong></p>

2013/01/09/introducing-the-plone-kitty/index.html

 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->      <p><em>Actually: re-introducing the Plone Kitty from Plone 1!</em></p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/plone-kitty.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/plone-kitty.png" />
 <p><em>Plone Kitty</em> is the name of a theme (then called &quot;skin&quot;) that shipped with the earliest versions of <a class="reference external" href="http://plone.org">Plone</a> (1.1 in the image above). This was a simpler time when the web was new, and everything was possible!</p>
 <p>Today, we know that the <strong>web is hard</strong>. While everything is still possible, building the web requires a tremendous amount of hard work. But it doesn't have to be all drudgery. There is still quite a bit of fun to be had building the web, if you know where to look (in addition to all the unavoidable hard work).</p>
 <p>Enter: Plone. Both the web and Plone have changed drastically since The Plone Kitty once prowled the internet. And while the Plone Kitty is all but extinct, Plone lives on; continously modernizing itself to keep up with the fast pace of today's modern web.</p>

2013/01/10/python-3-porting/index.html

 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->      <p><em>The 3 in 2013 is for Python 3</em></p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/python-3-port.jpg" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/python-3-port.jpg" />
 <p>I tend to like projects that everyone else <strong>hates</strong>, e.g.:</p>
 <ul class="simple">
 <li>Removing persistent Python objects associated with missing classes in ZODB.</li>

2013/01/31/please-help-me-do-open-source-work/index.html

 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->      <p><em>From my 'mid-life-crisis' series of blog entries :-)</em></p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/open-source-work.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/open-source-work.png" />
 <div class="section" id="open-source-work">
 <h2>Open Source Work</h2>
 <p><strong>Open Source Work</strong> has paid my bills for a long time. Starting with <a class="reference external" href="http://plone.org">Plone</a> in the early 2000s, to <a class="reference external" href="http://djangoproject.com">Django</a> in the early 2010s, to now. And for this, I am very grateful. To be clear: it's not exactly the <em>Open Source Work</em> that has paid my bills, it's the consulting work I've been able to secure as a result of my dedication and devotion to open source software and communities. Which is great! (Even more clear: my dedication and devotion to open source software and communities has made learning new skills fun. And those skills have paid my bills for the past 8 years.)</p>

2013/02/08/i-love-checkoutmanager-and-dotfiles/index.html

 <div class="section" id="shell">
 <h2>Shell</h2>
 <p>One of the first things I do on a new system is change my shell to <strong>Zsh</strong> in <tt class="docutils literal">System Preferences <span class="pre">-&gt;</span> Users &amp; Groups <span class="pre">-&gt;</span> Current User <span class="pre">-&gt;</span> Right Click <span class="pre">-&gt;</span> Advanced <span class="pre">Options...</span></tt>. Don't forget to <tt class="docutils literal">Click the lock to make changes</tt> first.</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/zsh.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/zsh.png" />
 <div class="section" id="zsh">
 <h3>Zsh</h3>
 <p>Why <strong>Zsh</strong>? One of my favorite features is <strong>shared history between open sessions</strong>. So I can run a command in one window, and then run the same command from another window by fetching it from the history (with CTRL-R).</p>
 <div class="section" id="xcode">
 <h2>XCode</h2>
 <p>After I take possession of my new laptop (running <strong>Mountain Lion</strong>, the newest OS X at the time of this writing), I head to the App Store to download XCode. <a class="footnote-reference" href="#id12" id="id2">[2]</a> Among many other things, XCode gives me the GNU C Compiler and allows me to type &quot;gcc&quot; in my <tt class="docutils literal">Applications <span class="pre">-&gt;</span> Utilities <span class="pre">-&gt;</span> Terminal</tt>.</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/gcc.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/gcc.png" />
 </div>
 <div class="section" id="id3">
 <h2>Python</h2>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/homebrew.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/homebrew.png" />
 <p>Now I need a Python interpreter <a class="footnote-reference" href="#id13" id="id4">[3]</a>. For development I use the <a class="reference external" href="https://github.com/collective/buildout.python">Collective Python Buildout</a> but I also enjoy using <a class="reference external" href="http://mxcl.github.com/homebrew/">Homebrew's</a> Python 2.7. I use Homebrew for a variety of other things too (e.g. mobile-shell AKA mosh) so here we go:</p>
 <pre class="literal-block">
 $ ruby -e &quot;$(curl -fsSL https://raw.github.com/mxcl/homebrew/go)&quot;
 $ brew install git
 </pre>
 <p>Which reminds me, don't forget that installing the command line utilities in Mountain Lion's XCode requires an additional step in <tt class="docutils literal">Preferences <span class="pre">-&gt;</span> Downloads <span class="pre">-&gt;</span> Command Line Tools <span class="pre">-&gt;</span> Install</tt>:</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/command-line-utils.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/command-line-utils.png" />
 </div>
 <div class="section" id="id5">
 <h2>Dotfiles</h2>

2013/03/15/the-story-of-pillow/index.html

 <p>That release is now done! And I have had an absolute blast working on Pillow full time over the course of the last week or so. So much so, that I'm going to propose you help me continue to have fun and be productive with Pillow… but more on that later. First, about the new release.</p>
 <div class="section" id="about-2-0-0">
 <h2>About 2.0.0</h2>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/story-of-pillow.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/story-of-pillow.png" />
 <p>This release marks the first &quot;serious effort&quot; I have put into Pillow. While I've always enjoyed working on it in my spare time, I knew that there was no way I could finish it in time for PyCon 2013 (as I promised) without getting some financial assistance.</p>
 <p>Enter: The PSF, who graciously offered to fund my work (and the work of one other contributor). Once I had funding in place, I knew exactly what needed to be done:</p>
 <ul class="simple">

2013/04/22/new-pyramid-site/index.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->      <img alt="" src="https://raw.github.com/ACLARKNET/aclarknet/master/screenshot.png" style="width: 98%;" />
+</footer><!-- /.post-info -->      <img alt="alternate text" src="https://raw.github.com/ACLARKNET/aclarknet/master/screenshot.png" style="width: 98%;" />
 <p>For the first time in 10 years, <a class="reference external" href="http://aclark.net">aclark.net</a> is not powered by Plone. Nothing against Plone: it's still one of the greatest loves of my life (inasmuch as you can love a software and community, as I do).</p>
 <div class="section" id="why">
 <h2>Why</h2>

2013/06/22/ploneorg-upgraded/index.html

 <li><p class="first">Run the upgrade locally. With plone.org data this takes about 45 minutes to an hour <a class="footnote-reference" href="#id2" id="id1">[1]</a>.</p>
 </li>
 </ol>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/upgrade.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/upgrade.png" />
 <ol class="arabic simple">
 <li>If the upgrade succeeds, you are ready to launch. If it fails, fix the errors before proceeding.</li>
 </ol>
 <li>Announce the upgrade: preferably a week or two in advance. The plone-developers and plone-users lists are probably sufficient, but you can create a plone.org news item too if you are feeling extra-ambitious. I only had a small window to perform this maintenance, so I skipped this step and proceeded directly to the next one.</li>
 <li>Add a status message to plone.org to indicate a maintenance window is in progress. I chose to customize the <tt class="docutils literal">main_template</tt> to accomplish this, but ideally we'd have some functionality in Plone that allowed site administrators to easily configure status messages.</li>
 </ol>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/upgrade-message.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/upgrade-message.png" />
 <ol class="arabic simple">
 <li>Disable logins. Since the upgrade takes a long time, we don't want content being edited during this process. I chose to use David Glick's technique of disabling PAS. I moved the ldap authentication plugin to the Active Plugin list, thus disabling PAS such that only ZODB users could login. But ideally we'd have some feature in Plone to allow site administrators to disable logins.</li>
 </ol>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pas.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pas.png" />
 <ol class="arabic">
 <li><p class="first">Run the upgrade. I forgot to mention earlier something very important: <strong>On plone.org, you can't access Zope from the internet.</strong> And you can't run the upgrade without accessing Zope. Hence run the following command to access the server, then access Plone via <tt class="docutils literal"><span class="pre">http://localhost:8080</span></tt>:</p>
 <pre class="literal-block">
 <li><p class="first">After the upgrade finishes, click around to make sure you didn't break anything. In my case, I broke something — I normally move <tt class="docutils literal">portal_skins/custom</tt> out of the way before upgrading, but this time I forgot. And when I experienced minor JavaScript issues, I forgot to examine custom; which currently looks like this:</p>
 </li>
 </ol>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/custom.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/custom.png" />
 <p>Even if I had remembered, I didn't want to spend the next few hours examining database customizations. Fortunately, before I realized I had forgotten to check custom, I emailed the plone-developers list —&nbsp;and Nathan Van Gheem to the rescue! He fixed some JavaScript in custom, then I cleared the cache(s). Ideally Plone would report on database customizations during the upgrade process: to indicate the potential for breakage and encourage the site administrator to round-trip those customizations back to the file system.</p>
 </div>
 <div class="section" id="conclusion">

2013/07/02/pillow-2-1-0-is-out/index.html

 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->      <p><em>Pillow is a popular fork of PIL by Alex Clark and Contributors. PIL is the Python Imaging Library by Fredrik Lundh and Contributors</em></p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pillow-2.1.0.png" style="width: 75%;" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pillow-2.1.0.png" style="width: 75%;" />
 <p><a class="reference external" href="https://pypi.python.org/pypi/Pillow/2.1.0">Pillow 2.1.0 is out!</a> With this release, the Pillow team has <em>finally</em> removed support for &quot;import _imaging&quot;, thus completing the move of PIL modules into the PIL namespace <a class="footnote-reference" href="#id3" id="id2">[1]</a>. Many thanks to Eric Soroos (AKA wiredfool) who completed the majority of this work. Also a big thanks to Christopher Gohlke and <a class="reference external" href="https://github.com/Arfrever">Arfrever</a> both of whom rallied around a push to get the 2.1.0 release out on schedule. And I want to thank everyone else who reported an issue and/or sent a pull request to help make this release the best it could be.</p>
 <div class="section" id="quarterly-release-cycle">
 <h2>Quarterly release cycle</h2>

2013/12/29/plonetheme-report/index.html

 plonetheme.wmoWonen
 </pre>
 <p>Not bad! That's a lot of working themes for Plone 4, many of which use Diazo.</p>
-<img alt="" src="/images/plonetheme-report-1.png" />
-<img alt="" src="/images/plonetheme-report-2.png" />
-<img alt="" src="/images/plonetheme-report-3.png" />
+<img alt="alternate text" src="/images/plonetheme-report-1.png" />
+<img alt="alternate text" src="/images/plonetheme-report-2.png" />
+<img alt="alternate text" src="/images/plonetheme-report-3.png" />
 <table class="docutils footnote" frame="void" id="id3" rules="none">
 <colgroup><col class="label" /><col /></colgroup>
 <tbody valign="top">

2014/01/01/pillow-2-3-0-is-out/index.html

 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->      <p><strong>Pillow is the &quot;friendly&quot; PIL fork by Alex Clark and Contributors. PIL is the Python Imaging Library by Fredrik Lundh and Contributors</strong></p>
 <p>Since Pillow 2.0, the Pillow Team has adopted a quarterly release cycle; as such, Pillow 2.3.0 has just been released. Here's what's new in this release:</p>
-<img alt="" src="/images/one-does-not-simply-make-a-release.jpg" />
+<img alt="alternate text" src="/images/one-does-not-simply-make-a-release.jpg" />
 <div class="section" id="id1">
 <h2>2.3.0 (2014-01-01)</h2>
 <ul class="simple">

2014/01/11/hello-plone-updated/index.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->      <img alt="" src="images/hello-plone-updated.jpg" />
+</footer><!-- /.post-info -->      <img alt="alternate text" src="images/hello-plone-updated.jpg" />
 <p>Over two years ago I wrote a blog entry called <a class="reference external" href="http://blog.aclark.net/2011/08/20/hello-plone/">&quot;Hello, Plone!&quot;</a>. I've just updated it in order to:</p>
 <ul class="simple">
 <li>Change the wording</li>

2014/03/19/virtualenv-support-update/index.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->      <img alt="" src="/images/virtualenv-support-update.jpg" />
+</footer><!-- /.post-info -->      <img alt="alternate text" src="/images/virtualenv-support-update.jpg" />
 <p>This is you: I <strong>use virtualenv all the time and I love it!</strong> But I hate having to manually upgrade setuptools within my virtualenvs because the <a class="reference external" href="https://pypi.python.org/pypi/setuptools#changes">PyPA has been so prolific with setuptools releases lately</a>.</p>
 <p>Actually this is me, but it may be you too. If this is you, you may be familiar with the following process. If not, you may want to be.</p>
 <div class="section" id="virtualenv-and-setuptools">

2014/03/20/introducing-plock-pins/index.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->      <img alt="" src="/images/buildout-all-the-plones.jpg" />
+</footer><!-- /.post-info -->      <img alt="alternate text" src="/images/buildout-all-the-plones.jpg" />
 <pre class="literal-block">
 &quot;Plock Pins are the greatest thing to happen to Plone since Buildout&quot;
 

2014/04/07/bro-do-you-even-pillow/index.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->      <img alt="" src="/images/bro-do-you-even-pillow.jpg" />
+</footer><!-- /.post-info -->      <img alt="alternate text" src="/images/bro-do-you-even-pillow.jpg" />
 <p><a class="reference external" href="https://github.com/python-imaging/Pillow">Pillow</a> is a fork of the Python Imaging Library. Here is an update on the status of the project.</p>
 <div class="section" id="released">
 <h2>2.4.0 released</h2>

2014/05/03/we-pioneer/index.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->      <img alt="" src="/images/we-pioneer.jpg" />
+</footer><!-- /.post-info -->      <img alt="alternate text" src="/images/we-pioneer.jpg" />
 <p>One of the subjects I find myself thinking about a lot is: Plone (surprise!) In Plone-land, we deliver the <strong>best Python-based CMS money can't buy on top of an aging Zope 2 &quot;application server&quot;</strong> mixed with newer Zope, Python, and other technologies. In short, this is a challenge.</p>
 <div class="section" id="diazo">
 <h2>Diazo</h2>

2014/05/19/matplotlib-plotting-cookbook-review/index.html

 <div class="section" id="chapter-5">
 <h2>Chapter 5</h2>
 <p>Chapter 5 is all about &quot;working with file output&quot;. For reference, here are some of the images produced by the examples in this chapter (I wrote <tt class="docutils literal">jpg</tt> files instead of <tt class="docutils literal">png</tt> files due to a problem with my libpng: <a class="reference external" href="https://www.google.com/#q=RuntimeError%3A+Could+not+create+write+struct&amp;safe=off">RuntimeError: Could not create write struct</a>.)</p>
-<img alt="" src="http://blog.aclark.net/images/sinc1.jpg" />
-<img alt="" src="http://blog.aclark.net/images/sinc3.jpg" />
+<img alt="alternate text" src="http://blog.aclark.net/images/sinc1.jpg" />
+<img alt="alternate text" src="http://blog.aclark.net/images/sinc3.jpg" />
 <p>Also covered in this chapter is <a class="reference external" href="http://blog.aclark.net/images/sinc.pdf">pdf output</a>.</p>
 </div>
 <div class="section" id="chapter-6">

author/aclark.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="/images/we-pioneer.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="/images/we-pioneer.jpg" />
 <p>One of the subjects I find myself thinking about a lot is: Plone (surprise!) In Plone-land, we deliver the <strong>best Python-based CMS money can't buy on top of an aging Zope 2 &quot;application server&quot;</strong> mixed with newer Zope, Python, and other technologies. In short, this is a challenge.</p>
 <div class="section" id="diazo">
 <h2>Diazo ...</h2></div>
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="/images/bro-do-you-even-pillow.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="/images/bro-do-you-even-pillow.jpg" />
 <p><a class="reference external" href="https://github.com/python-imaging/Pillow">Pillow</a> is a fork of the Python Imaging Library. Here is an update on the status of the project.</p>
 <div class="section" id="released">
 <h2>2.4.0 released</h2>
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="/images/buildout-all-the-plones.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="/images/buildout-all-the-plones.jpg" />
 <pre class="literal-block">
 &quot;Plock Pins are the greatest thing to happen to Plone since Buildout&quot;
 
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="/images/virtualenv-support-update.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="/images/virtualenv-support-update.jpg" />
 <p>This is you: I <strong>use virtualenv all the time and I love it!</strong> But I hate having to manually upgrade setuptools within my virtualenvs because the <a class="reference external" href="https://pypi.python.org/pypi/setuptools#changes">PyPA has been so prolific with setuptools releases lately</a>.</p>
 <p>Actually this is me, but it may be you too. If this is you, you ...</p>
                 <a class="readmore" href="http://blog.aclark.net/2014/03/19/virtualenv-support-update/">read more</a>
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="images/hello-plone-updated.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="images/hello-plone-updated.jpg" />
 <p>Over two years ago I wrote a blog entry called <a class="reference external" href="http://blog.aclark.net/2011/08/20/hello-plone/">&quot;Hello, Plone!&quot;</a>. I've just updated it in order to:</p>
 <ul class="simple">
 <li>Change the wording</li>

author/aclark11.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/lenin_packaging.png" style="width: 100%;" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/lenin_packaging.png" style="width: 100%;" />
 <div class="section" id="whats-the-coolest-python-application-framework-or-library-you-have-discovered-in-2009">
 <h2>What’s the coolest Python application, framework or library you have discovered in 2009?</h2>
 <p>That would be <a class="reference external" href="http://zenoss.org">Zenoss</a>. I'm very impressed with the application as well as the community, which is awesome. They remind me a lot of the Plone community; I think the two can learn a lot ...</p></div>

author/aclark2.html

 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->                <p><em>Pillow is a popular fork of PIL by Alex Clark and Contributors. PIL is the Python Imaging Library by Fredrik Lundh and Contributors</em></p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pillow-2.1.0.png" style="width: 75%;" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pillow-2.1.0.png" style="width: 75%;" />
 <p><a class="reference external" href="https://pypi.python.org/pypi/Pillow/2.1.0">Pillow 2.1.0 is out!</a> With this release, the Pillow team has <em>finally</em> removed support for &quot;import _imaging&quot;, thus completing the move of PIL modules into ...</p>
                 <a class="readmore" href="http://blog.aclark.net/2013/07/02/pillow-2-1-0-is-out/">read more</a>
 <p>There are <a href="http://blog.aclark.net/2013/07/02/pillow-2-1-0-is-out/#disqus_thread">comments</a>.</p>                </div><!-- /.entry-content -->
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="https://raw.github.com/ACLARKNET/aclarknet/master/screenshot.png" style="width: 98%;" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="https://raw.github.com/ACLARKNET/aclarknet/master/screenshot.png" style="width: 98%;" />
 <p>For the first time in 10 years, <a class="reference external" href="http://aclark.net">aclark.net</a> is not powered by Plone. Nothing against Plone: it's still one of the greatest loves of my life (inasmuch as you can love a software and community, as I do).</p>
 <div class="section" id="why">
 <h2>Why</h2>

author/aclark3.html

 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->                <p><em>From my 'mid-life-crisis' series of blog entries :-)</em></p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/open-source-work.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/open-source-work.png" />
 <div class="section" id="open-source-work">
 <h2>Open Source Work</h2>
 <p><strong>Open Source Work</strong> has paid my bills for a long time. Starting with <a class="reference external" href="http://plone.org">Plone</a> in the early 2000s, to <a class="reference external" href="http://djangoproject.com">Django</a> in the early 2010s, to now. And for this, I am very grateful. To be clear: it's not exactly ...</p></div>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->                <p><em>The 3 in 2013 is for Python 3</em></p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/python-3-port.jpg" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/python-3-port.jpg" />
 <p>I tend to like projects that everyone else <strong>hates</strong>, e.g.:</p>
 <ul class="simple">
 <li>Removing persistent Python objects associated with missing classes in ZODB.</li>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->                <p><em>Actually: re-introducing the Plone Kitty from Plone 1!</em></p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/plone-kitty.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/plone-kitty.png" />
 <p><em>Plone Kitty</em> is the name of a theme (then called &quot;skin&quot;) that shipped with the earliest versions of <a class="reference external" href="http://plone.org">Plone</a> (1.1 in the image above). This was a simpler time when the web was new, and everything was possible!</p>
 <p>Today, we know ...</p>
                 <a class="readmore" href="http://blog.aclark.net/2013/01/09/introducing-the-plone-kitty/">read more</a>
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/tarek-meme-reminder.png" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/tarek-meme-reminder.png" />
 <p><em>This is my entry for Tarek Ziadé's New Year's Python Meme, a tradition I have come to enjoy. Both to reflect on the current year and look back on previous years. So here it is.</em></p>
 <p>I did this in <a class="reference external" href="http://blog.aclark.net/2009/12/31/new-years-python-meme/">2009</a> &amp; <a class="reference external" href="http://blog.aclark.net/2011/12/21/new-years-python-meme-2011/">2011</a>. Let's try it again.</p>
 <p><strong>1. What ...</strong></p>

author/aclark4.html

 <div class="section" id="what">
 <h2>What</h2>
 <p>Recently with a tweet, I announced the start of a new personal project:</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/tweet.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/tweet.png" />
 </div>
 <div class="section" id="when">
 <h2>When</h2>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a></p>
 </footer><!-- /.post-info -->                <p>I read a lot of mailing lists:</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/unison.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/unison.png" />
 <p>Also, I've been subscribing to, reading, and participating in discussions on mailing lists since about the time Mailman 1.0 was released circa 1999 <a class="footnote-reference" href="#id3" id="id1">[1]</a>. And I have fond memories of interacting administratively with MajorDomo and ListServ software. And by administratively, I ...</p>
                 <a class="readmore" href="http://blog.aclark.net/2012/10/20/mailing-list-etiquette/">read more</a>
 <p>There are <a href="http://blog.aclark.net/2012/10/20/mailing-list-etiquette/#disqus_thread">comments</a>.</p>                </div><!-- /.entry-content -->
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->                <p>People do not understand gittip. Or, they do not understand how I use it. Worse, they <strong>think</strong> they understand it <a class="footnote-reference" href="#id2" id="id1">[1]</a>. So much so, some choose to comment about it publicly.</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/condescend.jpg" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/condescend.jpg" />
 <p>Remember <a class="reference external" href="http://blog.aclark.net/gittip-is-the-future.html">gittip is the future</a>? Someone commented:</p>
 <blockquote>
 <p>&quot;Nobody likes a beggar.&quot;</p>
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/python.html">Python</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/aclark-conf.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/aclark-conf.jpg" />
 <p>TL;DR: Because I care.</p>
 <p>As some of you can probably relate to, I've had my fair share of disagreements with the Plone Foundation Board over the years. The good news is, for the most part, it (just like the community) is staffed with <strong>very reasonable people</strong> who if ...</p>
                 <a class="readmore" href="http://blog.aclark.net/2012/10/17/why-i-criticize-the-plone-foundation-board/">read more</a>

author/aclark5.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/python.html">Python</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/y-u-no-agree.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/y-u-no-agree.jpg" />
 <p>I love to debate issues. The more complex, the better. I have no formal training in <a class="reference external" href="http://en.wikipedia.org/wiki/Debate">debate</a>, but I wish I did. It may have better prepared me to face different personality types with varying degree of communication skill. You don't have to watch the 2012 U.S. Presidential ...</p>
                 <a class="readmore" href="http://blog.aclark.net/2012/10/17/top-3-favorite-logical-fallacies/">read more</a>
 <p>There are <a href="http://blog.aclark.net/2012/10/17/top-3-favorite-logical-fallacies/#disqus_thread">comments</a>.</p>                </div><!-- /.entry-content -->
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/use_python.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/use_python.jpg" />
 <p>With <a class="reference external" href="http://blog.aclark.net/2012/09/28/pythonpackages-com-one-year-later/">pythonpackages.com winding down</a>, I am now actively seeking projects for Q4 2012 and beyond. I am good at:</p>
 <ul class="simple">
 <li>Deploying Plone sites: <a class="reference external" href="http://blog.aclark.net/2012/10/03/plone-4-3-alpha-1-in-production/">http://blog.aclark.net/2012/10/03/plone-4-3-alpha-1-in-production/</a></li>

author/aclark9.html

 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a></p>
 </footer><!-- /.post-info -->                <p>The <a class="reference external" href="http://coactivate.org/projects/snow-sprint-west-2011/project-home">Cioppino Sprint</a> was recently held in Bodega Bay, CA. It was a <a class="reference external" href="http://twitpic.com/3y21yk">beautiful location</a> for a gathering of awesome Plone folks; and much was accomplished. Unfortunately on the second morning of the sprint, we were all deeply saddened to hear about the passing of Dorneles Treméa.</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/bodega.jpg" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/bodega.jpg" />
 <div class="section" id="the-passing-of-dorneles-tremea">
 <h2>The passing of ...</h2></div>
                 <a class="readmore" href="http://blog.aclark.net/2011/02/16/cioppino-sprint-report/">read more</a>

category/blog.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="/images/we-pioneer.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="/images/we-pioneer.jpg" />
 <p>One of the subjects I find myself thinking about a lot is: Plone (surprise!) In Plone-land, we deliver the <strong>best Python-based CMS money can't buy on top of an aging Zope 2 &quot;application server&quot;</strong> mixed with newer Zope, Python, and other technologies. In short, this is a challenge.</p>
 <div class="section" id="diazo">
 <h2>Diazo ...</h2></div>
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="/images/bro-do-you-even-pillow.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="/images/bro-do-you-even-pillow.jpg" />
 <p><a class="reference external" href="https://github.com/python-imaging/Pillow">Pillow</a> is a fork of the Python Imaging Library. Here is an update on the status of the project.</p>
 <div class="section" id="released">
 <h2>2.4.0 released</h2>
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="/images/buildout-all-the-plones.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="/images/buildout-all-the-plones.jpg" />
 <pre class="literal-block">
 &quot;Plock Pins are the greatest thing to happen to Plone since Buildout&quot;
 
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="/images/virtualenv-support-update.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="/images/virtualenv-support-update.jpg" />
 <p>This is you: I <strong>use virtualenv all the time and I love it!</strong> But I hate having to manually upgrade setuptools within my virtualenvs because the <a class="reference external" href="https://pypi.python.org/pypi/setuptools#changes">PyPA has been so prolific with setuptools releases lately</a>.</p>
 <p>Actually this is me, but it may be you too. If this is you, you ...</p>
                 <a class="readmore" href="http://blog.aclark.net/2014/03/19/virtualenv-support-update/">read more</a>
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="images/hello-plone-updated.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="images/hello-plone-updated.jpg" />
 <p>Over two years ago I wrote a blog entry called <a class="reference external" href="http://blog.aclark.net/2011/08/20/hello-plone/">&quot;Hello, Plone!&quot;</a>. I've just updated it in order to:</p>
 <ul class="simple">
 <li>Change the wording</li>

category/blog11.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/lenin_packaging.png" style="width: 100%;" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/lenin_packaging.png" style="width: 100%;" />
 <div class="section" id="whats-the-coolest-python-application-framework-or-library-you-have-discovered-in-2009">
 <h2>What’s the coolest Python application, framework or library you have discovered in 2009?</h2>
 <p>That would be <a class="reference external" href="http://zenoss.org">Zenoss</a>. I'm very impressed with the application as well as the community, which is awesome. They remind me a lot of the Plone community; I think the two can learn a lot ...</p></div>

category/blog2.html

 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->                <p><em>Pillow is a popular fork of PIL by Alex Clark and Contributors. PIL is the Python Imaging Library by Fredrik Lundh and Contributors</em></p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pillow-2.1.0.png" style="width: 75%;" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pillow-2.1.0.png" style="width: 75%;" />
 <p><a class="reference external" href="https://pypi.python.org/pypi/Pillow/2.1.0">Pillow 2.1.0 is out!</a> With this release, the Pillow team has <em>finally</em> removed support for &quot;import _imaging&quot;, thus completing the move of PIL modules into ...</p>
                 <a class="readmore" href="http://blog.aclark.net/2013/07/02/pillow-2-1-0-is-out/">read more</a>
 <p>There are <a href="http://blog.aclark.net/2013/07/02/pillow-2-1-0-is-out/#disqus_thread">comments</a>.</p>                </div><!-- /.entry-content -->
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="https://raw.github.com/ACLARKNET/aclarknet/master/screenshot.png" style="width: 98%;" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="https://raw.github.com/ACLARKNET/aclarknet/master/screenshot.png" style="width: 98%;" />
 <p>For the first time in 10 years, <a class="reference external" href="http://aclark.net">aclark.net</a> is not powered by Plone. Nothing against Plone: it's still one of the greatest loves of my life (inasmuch as you can love a software and community, as I do).</p>
 <div class="section" id="why">
 <h2>Why</h2>

category/blog3.html

 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->                <p><em>From my 'mid-life-crisis' series of blog entries :-)</em></p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/open-source-work.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/open-source-work.png" />
 <div class="section" id="open-source-work">
 <h2>Open Source Work</h2>
 <p><strong>Open Source Work</strong> has paid my bills for a long time. Starting with <a class="reference external" href="http://plone.org">Plone</a> in the early 2000s, to <a class="reference external" href="http://djangoproject.com">Django</a> in the early 2010s, to now. And for this, I am very grateful. To be clear: it's not exactly ...</p></div>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->                <p><em>The 3 in 2013 is for Python 3</em></p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/python-3-port.jpg" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/python-3-port.jpg" />
 <p>I tend to like projects that everyone else <strong>hates</strong>, e.g.:</p>
 <ul class="simple">
 <li>Removing persistent Python objects associated with missing classes in ZODB.</li>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->                <p><em>Actually: re-introducing the Plone Kitty from Plone 1!</em></p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/plone-kitty.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/plone-kitty.png" />
 <p><em>Plone Kitty</em> is the name of a theme (then called &quot;skin&quot;) that shipped with the earliest versions of <a class="reference external" href="http://plone.org">Plone</a> (1.1 in the image above). This was a simpler time when the web was new, and everything was possible!</p>
 <p>Today, we know ...</p>
                 <a class="readmore" href="http://blog.aclark.net/2013/01/09/introducing-the-plone-kitty/">read more</a>
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/django.html">Django</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/tarek-meme-reminder.png" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/tarek-meme-reminder.png" />
 <p><em>This is my entry for Tarek Ziadé's New Year's Python Meme, a tradition I have come to enjoy. Both to reflect on the current year and look back on previous years. So here it is.</em></p>
 <p>I did this in <a class="reference external" href="http://blog.aclark.net/2009/12/31/new-years-python-meme/">2009</a> &amp; <a class="reference external" href="http://blog.aclark.net/2011/12/21/new-years-python-meme-2011/">2011</a>. Let's try it again.</p>
 <p><strong>1. What ...</strong></p>

category/blog4.html

 <div class="section" id="what">
 <h2>What</h2>
 <p>Recently with a tweet, I announced the start of a new personal project:</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/tweet.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/tweet.png" />
 </div>
 <div class="section" id="when">
 <h2>When</h2>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a></p>
 </footer><!-- /.post-info -->                <p>I read a lot of mailing lists:</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/unison.png" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/unison.png" />
 <p>Also, I've been subscribing to, reading, and participating in discussions on mailing lists since about the time Mailman 1.0 was released circa 1999 <a class="footnote-reference" href="#id3" id="id1">[1]</a>. And I have fond memories of interacting administratively with MajorDomo and ListServ software. And by administratively, I ...</p>
                 <a class="readmore" href="http://blog.aclark.net/2012/10/20/mailing-list-etiquette/">read more</a>
 <p>There are <a href="http://blog.aclark.net/2012/10/20/mailing-list-etiquette/#disqus_thread">comments</a>.</p>                </div><!-- /.entry-content -->
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a></p>
 </footer><!-- /.post-info -->                <p>People do not understand gittip. Or, they do not understand how I use it. Worse, they <strong>think</strong> they understand it <a class="footnote-reference" href="#id2" id="id1">[1]</a>. So much so, some choose to comment about it publicly.</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/condescend.jpg" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/condescend.jpg" />
 <p>Remember <a class="reference external" href="http://blog.aclark.net/gittip-is-the-future.html">gittip is the future</a>? Someone commented:</p>
 <blockquote>
 <p>&quot;Nobody likes a beggar.&quot;</p>
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/python.html">Python</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/aclark-conf.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/aclark-conf.jpg" />
 <p>TL;DR: Because I care.</p>
 <p>As some of you can probably relate to, I've had my fair share of disagreements with the Plone Foundation Board over the years. The good news is, for the most part, it (just like the community) is staffed with <strong>very reasonable people</strong> who if ...</p>
                 <a class="readmore" href="http://blog.aclark.net/2012/10/17/why-i-criticize-the-plone-foundation-board/">read more</a>

category/blog5.html

         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a><a href="http://blog.aclark.net/tag/python.html">Python</a><a href="http://blog.aclark.net/tag/plone.html">Plone</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/y-u-no-agree.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/y-u-no-agree.jpg" />
 <p>I love to debate issues. The more complex, the better. I have no formal training in <a class="reference external" href="http://en.wikipedia.org/wiki/Debate">debate</a>, but I wish I did. It may have better prepared me to face different personality types with varying degree of communication skill. You don't have to watch the 2012 U.S. Presidential ...</p>
                 <a class="readmore" href="http://blog.aclark.net/2012/10/17/top-3-favorite-logical-fallacies/">read more</a>
 <p>There are <a href="http://blog.aclark.net/2012/10/17/top-3-favorite-logical-fallacies/#disqus_thread">comments</a>.</p>                </div><!-- /.entry-content -->
         </address>
 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a><a href="http://blog.aclark.net/tag/python.html">Python</a><a href="http://blog.aclark.net/tag/mozilla.html">Mozilla</a></p>
-</footer><!-- /.post-info -->                <img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/use_python.jpg" />
+</footer><!-- /.post-info -->                <img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/use_python.jpg" />
 <p>With <a class="reference external" href="http://blog.aclark.net/2012/09/28/pythonpackages-com-one-year-later/">pythonpackages.com winding down</a>, I am now actively seeking projects for Q4 2012 and beyond. I am good at:</p>
 <ul class="simple">
 <li>Deploying Plone sites: <a class="reference external" href="http://blog.aclark.net/2012/10/03/plone-4-3-alpha-1-in-production/">http://blog.aclark.net/2012/10/03/plone-4-3-alpha-1-in-production/</a></li>

category/blog9.html

 <p>In <a href="http://blog.aclark.net/category/blog.html">Blog</a>. </p>
 <p>tags: <a href="http://blog.aclark.net/tag/plone.html">Plone</a></p>
 </footer><!-- /.post-info -->                <p>The <a class="reference external" href="http://coactivate.org/projects/snow-sprint-west-2011/project-home">Cioppino Sprint</a> was recently held in Bodega Bay, CA. It was a <a class="reference external" href="http://twitpic.com/3y21yk">beautiful location</a> for a gathering of awesome Plone folks; and much was accomplished. Unfortunately on the second morning of the sprint, we were all deeply saddened to hear about the passing of Dorneles Treméa.</p>
-<img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/bodega.jpg" />
+<img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/bodega.jpg" />
 <div class="section" id="the-passing-of-dorneles-tremea">
 <h2>The passing of ...</h2></div>
                 <a class="readmore" href="http://blog.aclark.net/2011/02/16/cioppino-sprint-report/">read more</a>

content/bro-do-you-even-pillow.rst

 :tags: Django, Plone, Python
 
 .. image:: /images/bro-do-you-even-pillow.jpg
+   :alt: alternate text
 
 `Pillow <https://github.com/python-imaging/Pillow>`_ is a fork of the Python Imaging Library. Here is an update on the status of the project.
 

content/cioppino-sprint-report.rst

 The `Cioppino Sprint`_ was recently held in Bodega Bay, CA. It was a `beautiful location`_ for a gathering of awesome Plone folks; and much was accomplished. Unfortunately on the second morning of the sprint, we were all deeply saddened to hear about the passing of Dorneles Treméa.
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/bodega.jpg
+   :alt: alternate text
 
 The passing of Dorneles Treméa
 ------------------------------

content/gittip-is-the-future.rst

 Why? If for no other reason, because it comes from a member of the Python community: Chad Whitacre of http://aspen.io fame. And the Python community has become near and dear to me, second only to my-one-true-open-source-love: Plone. So I want to see open source developers, particularly Python developers, succeed.
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/gittip.png
+   :alt: alternate text
 
 And succeed they will, with gittip. Some particularly impressive results so far: 
 

content/gittip-misunderstood.rst

 People do not understand gittip. Or, they do not understand how I use it. Worse, they **think** they understand it [1]_. So much so, some choose to comment about it publicly.
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/condescend.jpg
+   :alt: alternate text
 
 Remember `gittip is the future`_? Someone commented: 
 

content/hello-plone-updated.rst

 :tags: Plone, Python
 
 .. image:: images/hello-plone-updated.jpg
+   :alt: alternate text
 
 Over two years ago I wrote a blog entry called `"Hello, Plone!" <http://blog.aclark.net/2011/08/20/hello-plone/>`_. I've just updated it in order to:
 

content/help-me-upgrade-plone-org.rst

 Now without further ado, please donate-away! :-)
 
 .. figure:: https://www.paypal.com/en_US/i/scr/pixel.gif
+   :alt: alternate text
    :align: center
-   :alt: 
 
 .. _working on: http://dev.plone.org/plone/log/PloneOrg/buildouts/branches/3.0

content/i-love-checkoutmanager-and-dotfiles.rst

 One of the first things I do on a new system is change my shell to **Zsh** in ``System Preferences -> Users & Groups -> Current User -> Right Click -> Advanced Options...``. Don't forget to ``Click the lock to make changes`` first.
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/zsh.png
+   :alt: alternate text
 
 Zsh
 ~~~
 After I take possession of my new laptop (running **Mountain Lion**, the newest OS X at the time of this writing), I head to the App Store to download XCode. [2]_ Among many other things, XCode gives me the GNU C Compiler and allows me to type "gcc" in my ``Applications -> Utilities -> Terminal``.
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/gcc.png
+   :alt: alternate text
 
 Python
 ------
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/homebrew.png
+   :alt: alternate text
 
 Now I need a Python interpreter [3]_. For development I use the `Collective Python Buildout <https://github.com/collective/buildout.python>`_ but I also enjoy using `Homebrew's <http://mxcl.github.com/homebrew/>`_ Python 2.7. I use Homebrew for a variety of other things too (e.g. mobile-shell AKA mosh) so here we go::
 
 Which reminds me, don't forget that installing the command line utilities in Mountain Lion's XCode requires an additional step in ``Preferences -> Downloads -> Command Line Tools -> Install``:
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/command-line-utils.png
+   :alt: alternate text
 
 Dotfiles
 --------

content/introducing-plock-pins.rst

 :tags: Plone, Python
 
 .. image:: /images/buildout-all-the-plones.jpg
+   :alt: alternate text
 
 ::
 

content/introducing-the-plone-kitty.rst

 *Actually: re-introducing the Plone Kitty from Plone 1!*
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/plone-kitty.png
+   :alt: alternate text
 
 *Plone Kitty* is the name of a theme (then called "skin") that shipped with the earliest versions of `Plone <http://plone.org>`_ (1.1 in the image above). This was a simpler time when the web was new, and everything was possible!
 

content/looking-for-projects.rst

 :tags: Plone, Python, Mozilla
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/use_python.jpg
+   :alt: alternate text
 
 With `pythonpackages.com winding down`_, I am now actively seeking projects for Q4 2012 and beyond. I am good at:
 

content/mailing-list-etiquette.rst

 I read a lot of mailing lists:
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/unison.png
+   :alt: alternate text
 
 Also, I've been subscribing to, reading, and participating in discussions on mailing lists since about the time Mailman 1.0 was released circa 1999 [1]_. And I have fond memories of interacting administratively with MajorDomo and ListServ software. And by administratively, I mean sending the software commands and getting back a response. In fact, you might say I get along better with the software and machines than I do with the humans that use them. Which is not to say that I'm not a people person: I love people. But I do struggle with striking the right balance between hacking machines and communicating with humans.
 

content/matplotlib-plotting-cookbook-review.rst

 Chapter 5 is all about "working with file output". For reference, here are some of the images produced by the examples in this chapter (I wrote ``jpg`` files instead of ``png`` files due to a problem with my libpng: `RuntimeError: Could not create write struct <https://www.google.com/#q=RuntimeError%3A+Could+not+create+write+struct&safe=off>`_.)
 
 .. image:: http://blog.aclark.net/images/sinc1.jpg
+   :alt: alternate text
 
 .. image:: http://blog.aclark.net/images/sinc3.jpg
+   :alt: alternate text
 
 Also covered in this chapter is `pdf output <http://blog.aclark.net/images/sinc.pdf>`_.
 

content/new-pyramid-site.rst

 :tags: Django, Mozilla, Plone, Python
 
 .. image:: https://raw.github.com/ACLARKNET/aclarknet/master/screenshot.png
-  :width: 98%
+    :width: 98%
+    :alt: alternate text
 
 For the first time in 10 years, `aclark.net <http://aclark.net>`_ is not powered by Plone. Nothing against Plone: it's still one of the greatest loves of my life (inasmuch as you can love a software and community, as I do).
 

content/new-years-python-meme-2012.rst

 :tags: Django, Mozilla, Plone, Python
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/tarek-meme-reminder.png
+   :alt: alternate text
 
 *This is my entry for Tarek Ziadé's New Year's Python Meme, a tradition I have come to enjoy. Both to reflect on the current year and look back on previous years. So here it is.*
 

content/new-years-python-meme.rst

 :tags: Python
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/lenin_packaging.png 
-  :width: 100%
+    :width: 100%
+    :alt: alternate text
 
 What’s the coolest Python application, framework or library you have discovered in 2009?
 ----------------------------------------------------------------------------------------

content/pillow-2-1-0-is-out.rst

 *Pillow is a popular fork of PIL by Alex Clark and Contributors. PIL is the Python Imaging Library by Fredrik Lundh and Contributors*
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/pillow-2.1.0.png
-  :width: 75%
+    :alt: alternate text
+    :width: 75%
 
 `Pillow 2.1.0 is out! <https://pypi.python.org/pypi/Pillow/2.1.0>`_ With this release, the Pillow team has *finally* removed support for "import _imaging", thus completing the move of PIL modules into the PIL namespace [1]_. Many thanks to Eric Soroos (AKA wiredfool) who completed the majority of this work. Also a big thanks to Christopher Gohlke and `Arfrever <https://github.com/Arfrever>`_ both of whom rallied around a push to get the 2.1.0 release out on schedule. And I want to thank everyone else who reported an issue and/or sent a pull request to help make this release the best it could be.
 

content/pillow-2-3-0-is-out.rst

 Since Pillow 2.0, the Pillow Team has adopted a quarterly release cycle; as such, Pillow 2.3.0 has just been released. Here's what's new in this release:
 
 .. image:: /images/one-does-not-simply-make-a-release.jpg
+   :alt: alternate text
 
 2.3.0 (2014-01-01)
 ------------------

content/please-help-me-do-open-source-work.rst

 *From my 'mid-life-crisis' series of blog entries :-)*
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/open-source-work.png
+   :alt: alternate text
 
 Open Source Work
 ----------------

content/plone-4-3-alpha-1-in-production.rst

 As you may have noticed above I use ``z3c.jbot`` to customize various Plone templates.
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/custom-templates.png
+   :alt: alternate text
 
 Add content
 -----------
 
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/edit-ui.png
+   :alt: alternate text
 
 Use Diazo theme for public facing view
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Of course, visitors to http://aclark.net see the Diazo theme.
 
 .. image:: images/diazo-theme.png
+   :alt: alternate text
 
 I'm hoping that the Plone team can unify the content editing experience again in Plone 5, possibly via simplifying the "old style" templates such that it's easier to map them to custom Diazo themes.
 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. image:: images/all-content.png
+   :alt: alternate text
 
 Contributed by Laurence Rowe for Plone 4, I use the ``All content`` view in two places:
 

content/plone-guide.rst

 Recently with a tweet, I announced the start of a new personal project:
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/tweet.png
+   :alt: alternate text
 
 When
 ----
 I think a lot about what other people think about Plone, so I decided this book will feature comments from the general public in it. E.g.:
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/comments.png
+   :alt: alternate text
 
 How much?
 ---------

content/plone-org-upgraded.rst

 #. Run the upgrade locally. With plone.org data this takes about 45 minutes to an hour [1]_.
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/upgrade.png
+   :alt: alternate text
 
 #. If the upgrade succeeds, you are ready to launch. If it fails, fix the errors before proceeding.
 
 #. Add a status message to plone.org to indicate a maintenance window is in progress. I chose to customize the ``main_template`` to accomplish this, but ideally we'd have some functionality in Plone that allowed site administrators to easily configure status messages.
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/upgrade-message.png
+   :alt: alternate text
 
 #. Disable logins. Since the upgrade takes a long time, we don't want content being edited during this process. I chose to use David Glick's technique of disabling PAS. I moved the ldap authentication plugin to the Active Plugin list, thus disabling PAS such that only ZODB users could login. But ideally we'd have some feature in Plone to allow site administrators to disable logins.
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/pas.png
+   :alt: alternate text
 
 #. Run the upgrade. I forgot to mention earlier something very important: **On plone.org, you can't access Zope from the internet.** And you can't run the upgrade without accessing Zope. Hence run the following command to access the server, then access Plone via ``http://localhost:8080``::
 
 #. After the upgrade finishes, click around to make sure you didn't break anything. In my case, I broke something — I normally move ``portal_skins/custom`` out of the way before upgrading, but this time I forgot. And when I experienced minor JavaScript issues, I forgot to examine custom; which currently looks like this:
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/custom.png
+   :alt: alternate text
 
 Even if I had remembered, I didn't want to spend the next few hours examining database customizations. Fortunately, before I realized I had forgotten to check custom, I emailed the plone-developers list — and Nathan Van Gheem to the rescue! He fixed some JavaScript in custom, then I cleared the cache(s). Ideally Plone would report on database customizations during the upgrade process: to indicate the potential for breakage and encourage the site administrator to round-trip those customizations back to the file system.
 

content/plonetheme-report.rst

 Not bad! That's a lot of working themes for Plone 4, many of which use Diazo.
 
 .. image:: /images/plonetheme-report-1.png
+   :alt: alternate text
 .. image:: /images/plonetheme-report-2.png
+   :alt: alternate text
 .. image:: /images/plonetheme-report-3.png
+   :alt: alternate text
 
 .. [1] In the ``plonetheme`` namespace.
 .. [2] Plock is a Plone installer for the pip-loving crowd: https://plock.github.com.

content/python-3-porting.rst

 *The 3 in 2013 is for Python 3*
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/python-3-port.jpg
+   :alt: alternate text
 
 I tend to like projects that everyone else **hates**, e.g.:
 

content/pythonpackages-com-one-year-later.rst

 - The ability to "manage packages" (see image below)
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/manage-packages.png
+   :alt: alternate text
 
 - The ability to "manage organizations" (see image below)
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/manage-organizations.png
+   :alt: alternate text
 
 - The `ability to create packages through the web`_ (i.e. from the web browser to GitHub, whereas normally you'd run PasteScript in your Terminal).
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/create-new-package.png
+   :alt: alternate text
 
 And a few more logistical features that are cool:
 
 - The ability to pay with a credit card (via Stripe)
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/pay-with-stripe.png
+   :alt: alternate text
 
 - The ability to oauth against PyPI:
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/pypi-oauth.png
+   :alt: alternate text
 
 Still, we have only scratched the surface of what could potentially be provided to the Python community. Future plans include:
 

content/review-of-aspeli-plone-4-development.rst

 ~~~~~~~~~~~~~
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/buildout.png
+   :alt: alternate text
 
 Aspeli correctly addresses one of my biggest pet peeves (concerns) about what I believe to be an **ANTI-PATTERN** in almost every Plone buildout: buildout:eggs (referring to the eggs parameter of the buildout section; it does not exist, other than as a convenient variable setting).
 
 ~~~~~~~
 
 .. image:: image://raw.github.com/ACLARKNET/blog/gh-pages/images/addons.png
+   :alt: alternate text
 
 Did you see? You might have missed it. No mention of **Products** WHAT-SO-EVER. "Product" was a term that Zope2 used for Python libraries that enhanced the functionality of Zope2, and it stuck. Now, it should die in favor of a term everyone else in the world is familiar with (in this context): add-on. Well played, Aspeli. Well played.
 

content/the-story-of-pillow.rst

 -----------
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/story-of-pillow.png
+   :alt: alternate text
 
 This release marks the first "serious effort" I have put into Pillow. While I've always enjoyed working on it in my spare time, I knew that there was no way I could finish it in time for PyCon 2013 (as I promised) without getting some financial assistance.
 

content/top-3-favorite-logical-fallacies.rst

 :tags: Mozilla, Python, Plone
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/y-u-no-agree.jpg
+   :alt: alternate text
 
 I love to debate issues. The more complex, the better. I have no formal training in `debate`_, but I wish I did. It may have better prepared me to face different personality types with varying degree of communication skill. You don't have to watch the 2012 U.S. Presidential Debates to know that people will say things that are **BATSHIT CRAZY** to make their point. I've done it myself. That's why we need rules to formalize our discussions, because it's hard to stay on point.
 

content/virtualenv-support-update.rst

 :tags: Django, Plone, Python
 
 .. image:: /images/virtualenv-support-update.jpg
+   :alt: alternate text
 
 This is you: I **use virtualenv all the time and I love it!** But I hate having to manually upgrade setuptools within my virtualenvs because the `PyPA has been so prolific with setuptools releases lately <https://pypi.python.org/pypi/setuptools#changes>`_.
 

content/we-pioneer.rst

 :tags: Django, Plone, Python
 
 .. image:: /images/we-pioneer.jpg
+   :alt: alternate text
 
 One of the subjects I find myself thinking about a lot is: Plone (surprise!) In Plone-land, we deliver the **best Python-based CMS money can't buy on top of an aging Zope 2 "application server"** mixed with newer Zope, Python, and other technologies. In short, this is a challenge.
 

content/whats-new-as-of-plock-0-1-2.rst

     $ plock -l
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/plock-list-addons.png
+    :alt: alternate text
     :width: 95%
     :align: center
 

content/why-i-criticize-the-plone-foundation-board.rst

 :tags: Mozilla, Python, Plone
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/aclark-conf.jpg
+   :alt: alternate text
 
 TL;DR: Because I care.
 

content/yes-this-blog-is-powered-by-pelican.rst

 This was a giant let down, because I was hoping to avoid putting any time in to my blogging infrastructure. For weeks I did nothing. I poked at various options: Pelican, Plone, Tumblr, others. Eventually, I found my way back to Pelican and now I'm happy again.
 
 .. image:: https://raw.github.com/ACLARKNET/blog/gh-pages/images/pelican.png
+   :alt: alternate text
 
 Pelican is a static blog generator, as you may have heard. So **one big advantage** is:
 

feeds/Django.atom.xml

 &lt;div class="section" id="chapter-5"&gt;
 &lt;h2&gt;Chapter 5&lt;/h2&gt;
 &lt;p&gt;Chapter 5 is all about &amp;quot;working with file output&amp;quot;. For reference, here are some of the images produced by the examples in this chapter (I wrote &lt;tt class="docutils literal"&gt;jpg&lt;/tt&gt; files instead of &lt;tt class="docutils literal"&gt;png&lt;/tt&gt; files due to a problem with my libpng: &lt;a class="reference external" href="https://www.google.com/#q=RuntimeError%3A+Could+not+create+write+struct&amp;amp;safe=off"&gt;RuntimeError: Could not create write struct&lt;/a&gt;.)&lt;/p&gt;
-&lt;img alt="" src="http://blog.aclark.net/images/sinc1.jpg" /&gt;
-&lt;img alt="" src="http://blog.aclark.net/images/sinc3.jpg" /&gt;
+&lt;img alt="alternate text" src="http://blog.aclark.net/images/sinc1.jpg" /&gt;
+&lt;img alt="alternate text" src="http://blog.aclark.net/images/sinc3.jpg" /&gt;
 &lt;p&gt;Also covered in this chapter is &lt;a class="reference external" href="http://blog.aclark.net/images/sinc.pdf"&gt;pdf output&lt;/a&gt;.&lt;/p&gt;
 &lt;/div&gt;
 &lt;div class="section" id="chapter-6"&gt;
 &lt;/tbody&gt;
 &lt;/table&gt;
 &lt;/div&gt;
-</summary><category term="Django"></category><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>We Pioneer</title><link href="http://blog.aclark.net/2014/05/03/we-pioneer/" rel="alternate"></link><updated>2014-05-03T10:15:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-05-03:2014/05/03/we-pioneer/</id><summary type="html">&lt;img alt="" src="/images/we-pioneer.jpg" /&gt;
+</summary><category term="Django"></category><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>We Pioneer</title><link href="http://blog.aclark.net/2014/05/03/we-pioneer/" rel="alternate"></link><updated>2014-05-03T10:15:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-05-03:2014/05/03/we-pioneer/</id><summary type="html">&lt;img alt="alternate text" src="/images/we-pioneer.jpg" /&gt;
 &lt;p&gt;One of the subjects I find myself thinking about a lot is: Plone (surprise!) In Plone-land, we deliver the &lt;strong&gt;best Python-based CMS money can't buy on top of an aging Zope 2 &amp;quot;application server&amp;quot;&lt;/strong&gt; mixed with newer Zope, Python, and other technologies. In short, this is a challenge.&lt;/p&gt;
 &lt;div class="section" id="diazo"&gt;
 &lt;h2&gt;Diazo&lt;/h2&gt;
 &lt;/table&gt;
 &lt;/div&gt;
 &lt;/div&gt;
-</summary><category term="Django"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Bro, do you even Pillow?</title><link href="http://blog.aclark.net/2014/04/07/bro-do-you-even-pillow/" rel="alternate"></link><updated>2014-04-07T20:00:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-04-07:2014/04/07/bro-do-you-even-pillow/</id><summary type="html">&lt;img alt="" src="/images/bro-do-you-even-pillow.jpg" /&gt;
+</summary><category term="Django"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Bro, do you even Pillow?</title><link href="http://blog.aclark.net/2014/04/07/bro-do-you-even-pillow/" rel="alternate"></link><updated>2014-04-07T20:00:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-04-07:2014/04/07/bro-do-you-even-pillow/</id><summary type="html">&lt;img alt="alternate text" src="/images/bro-do-you-even-pillow.jpg" /&gt;
 &lt;p&gt;&lt;a class="reference external" href="https://github.com/python-imaging/Pillow"&gt;Pillow&lt;/a&gt; is a fork of the Python Imaging Library. Here is an update on the status of the project.&lt;/p&gt;
 &lt;div class="section" id="released"&gt;
 &lt;h2&gt;2.4.0 released&lt;/h2&gt;
 &lt;/ul&gt;
 &lt;p&gt;Keep using and supporting Pillow!&lt;/p&gt;
 &lt;/div&gt;
-</summary><category term="Django"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Virtualenv Support Update</title><link href="http://blog.aclark.net/2014/03/19/virtualenv-support-update/" rel="alternate"></link><updated>2014-03-19T17:30:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-03-19:2014/03/19/virtualenv-support-update/</id><summary type="html">&lt;img alt="" src="/images/virtualenv-support-update.jpg" /&gt;
+</summary><category term="Django"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Virtualenv Support Update</title><link href="http://blog.aclark.net/2014/03/19/virtualenv-support-update/" rel="alternate"></link><updated>2014-03-19T17:30:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-03-19:2014/03/19/virtualenv-support-update/</id><summary type="html">&lt;img alt="alternate text" src="/images/virtualenv-support-update.jpg" /&gt;
 &lt;p&gt;This is you: I &lt;strong&gt;use virtualenv all the time and I love it!&lt;/strong&gt; But I hate having to manually upgrade setuptools within my virtualenvs because the &lt;a class="reference external" href="https://pypi.python.org/pypi/setuptools#changes"&gt;PyPA has been so prolific with setuptools releases lately&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;Actually this is me, but it may be you too. If this is you, you may be familiar with the following process. If not, you may want to be.&lt;/p&gt;
 &lt;div class="section" id="virtualenv-and-setuptools"&gt;
 &lt;/div&gt;
 </summary><category term="Django"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Pillow 2-3-0 is out!</title><link href="http://blog.aclark.net/2014/01/01/pillow-2-3-0-is-out/" rel="alternate"></link><updated>2014-01-01T18:30:00-05:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-01-01:2014/01/01/pillow-2-3-0-is-out/</id><summary type="html">&lt;p&gt;&lt;strong&gt;Pillow is the &amp;quot;friendly&amp;quot; PIL fork by Alex Clark and Contributors. PIL is the Python Imaging Library by Fredrik Lundh and Contributors&lt;/strong&gt;&lt;/p&gt;
 &lt;p&gt;Since Pillow 2.0, the Pillow Team has adopted a quarterly release cycle; as such, Pillow 2.3.0 has just been released. Here's what's new in this release:&lt;/p&gt;
-&lt;img alt="" src="/images/one-does-not-simply-make-a-release.jpg" /&gt;
+&lt;img alt="alternate text" src="/images/one-does-not-simply-make-a-release.jpg" /&gt;
 &lt;div class="section" id="id1"&gt;
 &lt;h2&gt;2.3.0 (2014-01-01)&lt;/h2&gt;
 &lt;ul class="simple"&gt;
 &lt;p&gt;If you use Pillow professionally, please consider &lt;a class="reference external" href="https://github.com/python-imaging/Pillow#financial"&gt;supporting its development&lt;/a&gt;.&lt;/p&gt;
 &lt;/div&gt;
 </summary><category term="Django"></category><category term="Python"></category><category term="Plone"></category></entry><entry><title>Pillow 2-1-0 is out!</title><link href="http://blog.aclark.net/2013/07/02/pillow-2-1-0-is-out/" rel="alternate"></link><updated>2013-07-02T00:00:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2013-07-02:2013/07/02/pillow-2-1-0-is-out/</id><summary type="html">&lt;p&gt;&lt;em&gt;Pillow is a popular fork of PIL by Alex Clark and Contributors. PIL is the Python Imaging Library by Fredrik Lundh and Contributors&lt;/em&gt;&lt;/p&gt;
-&lt;img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pillow-2.1.0.png" style="width: 75%;" /&gt;
+&lt;img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/pillow-2.1.0.png" style="width: 75%;" /&gt;
 &lt;p&gt;&lt;a class="reference external" href="https://pypi.python.org/pypi/Pillow/2.1.0"&gt;Pillow 2.1.0 is out!&lt;/a&gt; With this release, the Pillow team has &lt;em&gt;finally&lt;/em&gt; removed support for &amp;quot;import _imaging&amp;quot;, thus completing the move of PIL modules into the PIL namespace &lt;a class="footnote-reference" href="#id3" id="id2"&gt;[1]&lt;/a&gt;. Many thanks to Eric Soroos (AKA wiredfool) who completed the majority of this work. Also a big thanks to Christopher Gohlke and &lt;a class="reference external" href="https://github.com/Arfrever"&gt;Arfrever&lt;/a&gt; both of whom rallied around a push to get the 2.1.0 release out on schedule. And I want to thank everyone else who reported an issue and/or sent a pull request to help make this release the best it could be.&lt;/p&gt;
 &lt;div class="section" id="quarterly-release-cycle"&gt;
 &lt;h2&gt;Quarterly release cycle&lt;/h2&gt;
 &lt;/tbody&gt;
 &lt;/table&gt;
 &lt;/div&gt;
-</summary><category term="Django"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>New Pyramid Site</title><link href="http://blog.aclark.net/2013/04/22/new-pyramid-site/" rel="alternate"></link><updated>2013-04-22T12:00:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2013-04-22:2013/04/22/new-pyramid-site/</id><summary type="html">&lt;img alt="" src="https://raw.github.com/ACLARKNET/aclarknet/master/screenshot.png" style="width: 98%;" /&gt;
+</summary><category term="Django"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>New Pyramid Site</title><link href="http://blog.aclark.net/2013/04/22/new-pyramid-site/" rel="alternate"></link><updated>2013-04-22T12:00:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2013-04-22:2013/04/22/new-pyramid-site/</id><summary type="html">&lt;img alt="alternate text" src="https://raw.github.com/ACLARKNET/aclarknet/master/screenshot.png" style="width: 98%;" /&gt;
 &lt;p&gt;For the first time in 10 years, &lt;a class="reference external" href="http://aclark.net"&gt;aclark.net&lt;/a&gt; is not powered by Plone. Nothing against Plone: it's still one of the greatest loves of my life (inasmuch as you can love a software and community, as I do).&lt;/p&gt;
 &lt;div class="section" id="why"&gt;
 &lt;h2&gt;Why&lt;/h2&gt;
 &lt;p&gt;That release is now done! And I have had an absolute blast working on Pillow full time over the course of the last week or so. So much so, that I'm going to propose you help me continue to have fun and be productive with Pillow… but more on that later. First, about the new release.&lt;/p&gt;
 &lt;div class="section" id="about-2-0-0"&gt;
 &lt;h2&gt;About 2.0.0&lt;/h2&gt;
-&lt;img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/story-of-pillow.png" /&gt;
+&lt;img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/story-of-pillow.png" /&gt;
 &lt;p&gt;This release marks the first &amp;quot;serious effort&amp;quot; I have put into Pillow. While I've always enjoyed working on it in my spare time, I knew that there was no way I could finish it in time for PyCon 2013 (as I promised) without getting some financial assistance.&lt;/p&gt;
 &lt;p&gt;Enter: The PSF, who graciously offered to fund my work (and the work of one other contributor). Once I had funding in place, I knew exactly what needed to be done:&lt;/p&gt;
 &lt;ul class="simple"&gt;

feeds/Mozilla.atom.xml

 &lt;div class="section" id="chapter-5"&gt;
 &lt;h2&gt;Chapter 5&lt;/h2&gt;
 &lt;p&gt;Chapter 5 is all about &amp;quot;working with file output&amp;quot;. For reference, here are some of the images produced by the examples in this chapter (I wrote &lt;tt class="docutils literal"&gt;jpg&lt;/tt&gt; files instead of &lt;tt class="docutils literal"&gt;png&lt;/tt&gt; files due to a problem with my libpng: &lt;a class="reference external" href="https://www.google.com/#q=RuntimeError%3A+Could+not+create+write+struct&amp;amp;safe=off"&gt;RuntimeError: Could not create write struct&lt;/a&gt;.)&lt;/p&gt;
-&lt;img alt="" src="http://blog.aclark.net/images/sinc1.jpg" /&gt;
-&lt;img alt="" src="http://blog.aclark.net/images/sinc3.jpg" /&gt;
+&lt;img alt="alternate text" src="http://blog.aclark.net/images/sinc1.jpg" /&gt;
+&lt;img alt="alternate text" src="http://blog.aclark.net/images/sinc3.jpg" /&gt;
 &lt;p&gt;Also covered in this chapter is &lt;a class="reference external" href="http://blog.aclark.net/images/sinc.pdf"&gt;pdf output&lt;/a&gt;.&lt;/p&gt;
 &lt;/div&gt;
 &lt;div class="section" id="chapter-6"&gt;
 &lt;/div&gt;
 </summary><category term="Django"></category><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Pillow 2-3-0 is out!</title><link href="http://blog.aclark.net/2014/01/01/pillow-2-3-0-is-out/" rel="alternate"></link><updated>2014-01-01T18:30:00-05:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-01-01:2014/01/01/pillow-2-3-0-is-out/</id><summary type="html">&lt;p&gt;&lt;strong&gt;Pillow is the &amp;quot;friendly&amp;quot; PIL fork by Alex Clark and Contributors. PIL is the Python Imaging Library by Fredrik Lundh and Contributors&lt;/strong&gt;&lt;/p&gt;
 &lt;p&gt;Since Pillow 2.0, the Pillow Team has adopted a quarterly release cycle; as such, Pillow 2.3.0 has just been released. Here's what's new in this release:&lt;/p&gt;
-&lt;img alt="" src="/images/one-does-not-simply-make-a-release.jpg" /&gt;
+&lt;img alt="alternate text" src="/images/one-does-not-simply-make-a-release.jpg" /&gt;
 &lt;div class="section" id="id1"&gt;
 &lt;h2&gt;2.3.0 (2014-01-01)&lt;/h2&gt;
 &lt;ul class="simple"&gt;
 ----------------------------------------------------------------------------------------
 &lt;/pre&gt;
 &lt;/div&gt;
-</summary><category term="Django"></category><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>New Pyramid Site</title><link href="http://blog.aclark.net/2013/04/22/new-pyramid-site/" rel="alternate"></link><updated>2013-04-22T12:00:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2013-04-22:2013/04/22/new-pyramid-site/</id><summary type="html">&lt;img alt="" src="https://raw.github.com/ACLARKNET/aclarknet/master/screenshot.png" style="width: 98%;" /&gt;
+</summary><category term="Django"></category><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>New Pyramid Site</title><link href="http://blog.aclark.net/2013/04/22/new-pyramid-site/" rel="alternate"></link><updated>2013-04-22T12:00:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2013-04-22:2013/04/22/new-pyramid-site/</id><summary type="html">&lt;img alt="alternate text" src="https://raw.github.com/ACLARKNET/aclarknet/master/screenshot.png" style="width: 98%;" /&gt;
 &lt;p&gt;For the first time in 10 years, &lt;a class="reference external" href="http://aclark.net"&gt;aclark.net&lt;/a&gt; is not powered by Plone. Nothing against Plone: it's still one of the greatest loves of my life (inasmuch as you can love a software and community, as I do).&lt;/p&gt;
 &lt;div class="section" id="why"&gt;
 &lt;h2&gt;Why&lt;/h2&gt;
 &lt;div class="section" id="shell"&gt;
 &lt;h2&gt;Shell&lt;/h2&gt;
 &lt;p&gt;One of the first things I do on a new system is change my shell to &lt;strong&gt;Zsh&lt;/strong&gt; in &lt;tt class="docutils literal"&gt;System Preferences &lt;span class="pre"&gt;-&amp;gt;&lt;/span&gt; Users &amp;amp; Groups &lt;span class="pre"&gt;-&amp;gt;&lt;/span&gt; Current User &lt;span class="pre"&gt;-&amp;gt;&lt;/span&gt; Right Click &lt;span class="pre"&gt;-&amp;gt;&lt;/span&gt; Advanced &lt;span class="pre"&gt;Options...&lt;/span&gt;&lt;/tt&gt;. Don't forget to &lt;tt class="docutils literal"&gt;Click the lock to make changes&lt;/tt&gt; first.&lt;/p&gt;
-&lt;img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/zsh.png" /&gt;
+&lt;img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/zsh.png" /&gt;
 &lt;div class="section" id="zsh"&gt;
 &lt;h3&gt;Zsh&lt;/h3&gt;
 &lt;p&gt;Why &lt;strong&gt;Zsh&lt;/strong&gt;? One of my favorite features is &lt;strong&gt;shared history between open sessions&lt;/strong&gt;. So I can run a command in one window, and then run the same command from another window by fetching it from the history (with CTRL-R).&lt;/p&gt;
 &lt;div class="section" id="xcode"&gt;
 &lt;h2&gt;XCode&lt;/h2&gt;
 &lt;p&gt;After I take possession of my new laptop (running &lt;strong&gt;Mountain Lion&lt;/strong&gt;, the newest OS X at the time of this writing), I head to the App Store to download XCode. &lt;a class="footnote-reference" href="#id12" id="id2"&gt;[2]&lt;/a&gt; Among many other things, XCode gives me the GNU C Compiler and allows me to type &amp;quot;gcc&amp;quot; in my &lt;tt class="docutils literal"&gt;Applications &lt;span class="pre"&gt;-&amp;gt;&lt;/span&gt; Utilities &lt;span class="pre"&gt;-&amp;gt;&lt;/span&gt; Terminal&lt;/tt&gt;.&lt;/p&gt;
-&lt;img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/gcc.png" /&gt;
+&lt;img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/gcc.png" /&gt;
 &lt;/div&gt;
 &lt;div class="section" id="id3"&gt;
 &lt;h2&gt;Python&lt;/h2&gt;
-&lt;img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/homebrew.png" /&gt;
+&lt;img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/homebrew.png" /&gt;
 &lt;p&gt;Now I need a Python interpreter &lt;a class="footnote-reference" href="#id13" id="id4"&gt;[3]&lt;/a&gt;. For development I use the &lt;a class="reference external" href="https://github.com/collective/buildout.python"&gt;Collective Python Buildout&lt;/a&gt; but I also enjoy using &lt;a class="reference external" href="http://mxcl.github.com/homebrew/"&gt;Homebrew's&lt;/a&gt; Python 2.7. I use Homebrew for a variety of other things too (e.g. mobile-shell AKA mosh) so here we go:&lt;/p&gt;
 &lt;pre class="literal-block"&gt;
 $ ruby -e &amp;quot;$(curl -fsSL https://raw.github.com/mxcl/homebrew/go)&amp;quot;
 $ brew install git
 &lt;/pre&gt;
 &lt;p&gt;Which reminds me, don't forget that installing the command line utilities in Mountain Lion's XCode requires an additional step in &lt;tt class="docutils literal"&gt;Preferences &lt;span class="pre"&gt;-&amp;gt;&lt;/span&gt; Downloads &lt;span class="pre"&gt;-&amp;gt;&lt;/span&gt; Command Line Tools &lt;span class="pre"&gt;-&amp;gt;&lt;/span&gt; Install&lt;/tt&gt;:&lt;/p&gt;
-&lt;img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/command-line-utils.png" /&gt;
+&lt;img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/command-line-utils.png" /&gt;
 &lt;/div&gt;
 &lt;div class="section" id="id5"&gt;
 &lt;h2&gt;Dotfiles&lt;/h2&gt;
 &lt;/table&gt;
 &lt;/div&gt;
 </summary><category term="Django"></category><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Please Help Me Do Open Source Work</title><link href="http://blog.aclark.net/2013/01/31/please-help-me-do-open-source-work/" rel="alternate"></link><updated>2013-01-31T13:00:00-05:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2013-01-31:2013/01/31/please-help-me-do-open-source-work/</id><summary type="html">&lt;p&gt;&lt;em&gt;From my 'mid-life-crisis' series of blog entries :-)&lt;/em&gt;&lt;/p&gt;
-&lt;img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/open-source-work.png" /&gt;
+&lt;img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/open-source-work.png" /&gt;
 &lt;div class="section" id="open-source-work"&gt;
 &lt;h2&gt;Open Source Work&lt;/h2&gt;
 &lt;p&gt;&lt;strong&gt;Open Source Work&lt;/strong&gt; has paid my bills for a long time. Starting with &lt;a class="reference external" href="http://plone.org"&gt;Plone&lt;/a&gt; in the early 2000s, to &lt;a class="reference external" href="http://djangoproject.com"&gt;Django&lt;/a&gt; in the early 2010s, to now. And for this, I am very grateful. To be clear: it's not exactly the &lt;em&gt;Open Source Work&lt;/em&gt; that has paid my bills, it's the consulting work I've been able to secure as a result of my dedication and devotion to open source software and communities. Which is great! (Even more clear: my dedication and devotion to open source software and communities has made learning new skills fun. And those skills have paid my bills for the past 8 years.)&lt;/p&gt;
 src="https://www.gittip.com/assets/widgets/0002.js"&gt;
 &lt;/script&gt;&lt;/div&gt;
 </summary><category term="Django"></category><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Python 3 Porting</title><link href="http://blog.aclark.net/2013/01/10/python-3-porting/" rel="alternate"></link><updated>2013-01-10T19:15:00-05:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2013-01-10:2013/01/10/python-3-porting/</id><summary type="html">&lt;p&gt;&lt;em&gt;The 3 in 2013 is for Python 3&lt;/em&gt;&lt;/p&gt;
-&lt;img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/python-3-port.jpg" /&gt;
+&lt;img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/python-3-port.jpg" /&gt;
 &lt;p&gt;I tend to like projects that everyone else &lt;strong&gt;hates&lt;/strong&gt;, e.g.:&lt;/p&gt;
 &lt;ul class="simple"&gt;
 &lt;li&gt;Removing persistent Python objects associated with missing classes in ZODB.&lt;/li&gt;
 &lt;/ul&gt;
 &lt;p&gt;So, there is no time like the present to &lt;strong&gt;take a serious look at Python 3&lt;/strong&gt;.&lt;/p&gt;
 &lt;/div&gt;
-</summary><category term="Django"></category><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>New Year's Python Meme 2012</title><link href="http://blog.aclark.net/2012/12/29/new-years-python-meme-2012/" rel="alternate"></link><updated>2012-12-29T15:30:00-05:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2012-12-29:2012/12/29/new-years-python-meme-2012/</id><summary type="html">&lt;img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/tarek-meme-reminder.png" /&gt;
+</summary><category term="Django"></category><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>New Year's Python Meme 2012</title><link href="http://blog.aclark.net/2012/12/29/new-years-python-meme-2012/" rel="alternate"></link><updated>2012-12-29T15:30:00-05:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2012-12-29:2012/12/29/new-years-python-meme-2012/</id><summary type="html">&lt;img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/tarek-meme-reminder.png" /&gt;
 &lt;p&gt;&lt;em&gt;This is my entry for Tarek Ziadé's New Year's Python Meme, a tradition I have come to enjoy. Both to reflect on the current year and look back on previous years. So here it is.&lt;/em&gt;&lt;/p&gt;
 &lt;p&gt;I did this in &lt;a class="reference external" href="http://blog.aclark.net/2009/12/31/new-years-python-meme/"&gt;2009&lt;/a&gt; &amp;amp; &lt;a class="reference external" href="http://blog.aclark.net/2011/12/21/new-years-python-meme-2011/"&gt;2011&lt;/a&gt;. Let's try it again.&lt;/p&gt;
 &lt;p&gt;&lt;strong&gt;1. What’s the coolest Python application, framework or library you have discovered in 2012?&lt;/strong&gt;&lt;/p&gt;
 &lt;li&gt;Tweet it with the &lt;a class="reference external" href="https://twitter.com/search/realtime?q=%232012pythonmeme&amp;amp;src=typd"&gt;#2012pythonmeme&lt;/a&gt; hashtag&lt;/li&gt;
 &lt;/ul&gt;
 </summary><category term="Django"></category><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Gittip, Misunderstood</title><link href="http://blog.aclark.net/2012/10/19/gittip-misunderstood/" rel="alternate"></link><updated>2012-10-19T03:00:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2012-10-19:2012/10/19/gittip-misunderstood/</id><summary type="html">&lt;p&gt;People do not understand gittip. Or, they do not understand how I use it. Worse, they &lt;strong&gt;think&lt;/strong&gt; they understand it &lt;a class="footnote-reference" href="#id2" id="id1"&gt;[1]&lt;/a&gt;. So much so, some choose to comment about it publicly.&lt;/p&gt;
-&lt;img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/condescend.jpg" /&gt;
+&lt;img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/condescend.jpg" /&gt;
 &lt;p&gt;Remember &lt;a class="reference external" href="http://blog.aclark.net/gittip-is-the-future.html"&gt;gittip is the future&lt;/a&gt;? Someone commented:&lt;/p&gt;
 &lt;blockquote&gt;
 &lt;p&gt;&amp;quot;Nobody likes a beggar.&amp;quot;&lt;/p&gt;
 &lt;/tbody&gt;
 &lt;/table&gt;
 &lt;/div&gt;
-</summary><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Why I Criticize The Plone Foundation Board</title><link href="http://blog.aclark.net/2012/10/17/why-i-criticize-the-plone-foundation-board/" rel="alternate"></link><updated>2012-10-17T20:00:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2012-10-17:2012/10/17/why-i-criticize-the-plone-foundation-board/</id><summary type="html">&lt;img alt="" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/aclark-conf.jpg" /&gt;
+</summary><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Why I Criticize The Plone Foundation Board</title><link href="http://blog.aclark.net/2012/10/17/why-i-criticize-the-plone-foundation-board/" rel="alternate"></link><updated>2012-10-17T20:00:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2012-10-17:2012/10/17/why-i-criticize-the-plone-foundation-board/</id><summary type="html">&lt;img alt="alternate text" src="https://raw.github.com/ACLARKNET/blog/gh-pages/images/aclark-conf.jpg" /&gt;
 &lt;p&gt;TL;DR: Because I care.&lt;/p&gt;
 &lt;p&gt;As some of you can probably relate to, I've had my fair share of disagreements with the Plone Foundation Board over the years. The good news is, for the most part, it (just like the community) is staffed with &lt;strong&gt;very reasonable people&lt;/strong&gt; who if you push them on an issue, will acknowledge that there are always competing viewpoints to any issue you can think of.&lt;/p&gt;
 &lt;div class="section" id="the-fallacy-of-false-cause"&gt;

feeds/Plone.atom.xml

 &lt;div class="section" id="chapter-5"&gt;
 &lt;h2&gt;Chapter 5&lt;/h2&gt;
 &lt;p&gt;Chapter 5 is all about &amp;quot;working with file output&amp;quot;. For reference, here are some of the images produced by the examples in this chapter (I wrote &lt;tt class="docutils literal"&gt;jpg&lt;/tt&gt; files instead of &lt;tt class="docutils literal"&gt;png&lt;/tt&gt; files due to a problem with my libpng: &lt;a class="reference external" href="https://www.google.com/#q=RuntimeError%3A+Could+not+create+write+struct&amp;amp;safe=off"&gt;RuntimeError: Could not create write struct&lt;/a&gt;.)&lt;/p&gt;
-&lt;img alt="" src="http://blog.aclark.net/images/sinc1.jpg" /&gt;
-&lt;img alt="" src="http://blog.aclark.net/images/sinc3.jpg" /&gt;
+&lt;img alt="alternate text" src="http://blog.aclark.net/images/sinc1.jpg" /&gt;
+&lt;img alt="alternate text" src="http://blog.aclark.net/images/sinc3.jpg" /&gt;
 &lt;p&gt;Also covered in this chapter is &lt;a class="reference external" href="http://blog.aclark.net/images/sinc.pdf"&gt;pdf output&lt;/a&gt;.&lt;/p&gt;
 &lt;/div&gt;
 &lt;div class="section" id="chapter-6"&gt;
 &lt;/tbody&gt;
 &lt;/table&gt;
 &lt;/div&gt;
-</summary><category term="Django"></category><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>We Pioneer</title><link href="http://blog.aclark.net/2014/05/03/we-pioneer/" rel="alternate"></link><updated>2014-05-03T10:15:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-05-03:2014/05/03/we-pioneer/</id><summary type="html">&lt;img alt="" src="/images/we-pioneer.jpg" /&gt;
+</summary><category term="Django"></category><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>We Pioneer</title><link href="http://blog.aclark.net/2014/05/03/we-pioneer/" rel="alternate"></link><updated>2014-05-03T10:15:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-05-03:2014/05/03/we-pioneer/</id><summary type="html">&lt;img alt="alternate text" src="/images/we-pioneer.jpg" /&gt;
 &lt;p&gt;One of the subjects I find myself thinking about a lot is: Plone (surprise!) In Plone-land, we deliver the &lt;strong&gt;best Python-based CMS money can't buy on top of an aging Zope 2 &amp;quot;application server&amp;quot;&lt;/strong&gt; mixed with newer Zope, Python, and other technologies. In short, this is a challenge.&lt;/p&gt;
 &lt;div class="section" id="diazo"&gt;
 &lt;h2&gt;Diazo&lt;/h2&gt;
 &lt;/table&gt;
 &lt;/div&gt;
 &lt;/div&gt;
-</summary><category term="Django"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Bro, do you even Pillow?</title><link href="http://blog.aclark.net/2014/04/07/bro-do-you-even-pillow/" rel="alternate"></link><updated>2014-04-07T20:00:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-04-07:2014/04/07/bro-do-you-even-pillow/</id><summary type="html">&lt;img alt="" src="/images/bro-do-you-even-pillow.jpg" /&gt;
+</summary><category term="Django"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Bro, do you even Pillow?</title><link href="http://blog.aclark.net/2014/04/07/bro-do-you-even-pillow/" rel="alternate"></link><updated>2014-04-07T20:00:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-04-07:2014/04/07/bro-do-you-even-pillow/</id><summary type="html">&lt;img alt="alternate text" src="/images/bro-do-you-even-pillow.jpg" /&gt;
 &lt;p&gt;&lt;a class="reference external" href="https://github.com/python-imaging/Pillow"&gt;Pillow&lt;/a&gt; is a fork of the Python Imaging Library. Here is an update on the status of the project.&lt;/p&gt;
 &lt;div class="section" id="released"&gt;
 &lt;h2&gt;2.4.0 released&lt;/h2&gt;
 &lt;/ul&gt;
 &lt;p&gt;Keep using and supporting Pillow!&lt;/p&gt;
 &lt;/div&gt;
-</summary><category term="Django"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Introducing Plock Pins</title><link href="http://blog.aclark.net/2014/03/20/introducing-plock-pins/" rel="alternate"></link><updated>2014-03-20T21:15:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-03-20:2014/03/20/introducing-plock-pins/</id><summary type="html">&lt;img alt="" src="/images/buildout-all-the-plones.jpg" /&gt;
+</summary><category term="Django"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Introducing Plock Pins</title><link href="http://blog.aclark.net/2014/03/20/introducing-plock-pins/" rel="alternate"></link><updated>2014-03-20T21:15:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-03-20:2014/03/20/introducing-plock-pins/</id><summary type="html">&lt;img alt="alternate text" src="/images/buildout-all-the-plones.jpg" /&gt;
 &lt;pre class="literal-block"&gt;
 &amp;quot;Plock Pins are the greatest thing to happen to Plone since Buildout&amp;quot;
 
 &lt;tr&gt;&lt;td class="label"&gt;&lt;a class="fn-backref" href="#id2"&gt;[2]&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Remember to use Python 2.4 for &amp;lt; Plone 4&lt;/td&gt;&lt;/tr&gt;
 &lt;/tbody&gt;
 &lt;/table&gt;
-</summary><category term="Plone"></category><category term="Python"></category></entry><entry><title>Virtualenv Support Update</title><link href="http://blog.aclark.net/2014/03/19/virtualenv-support-update/" rel="alternate"></link><updated>2014-03-19T17:30:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-03-19:2014/03/19/virtualenv-support-update/</id><summary type="html">&lt;img alt="" src="/images/virtualenv-support-update.jpg" /&gt;
+</summary><category term="Plone"></category><category term="Python"></category></entry><entry><title>Virtualenv Support Update</title><link href="http://blog.aclark.net/2014/03/19/virtualenv-support-update/" rel="alternate"></link><updated>2014-03-19T17:30:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-03-19:2014/03/19/virtualenv-support-update/</id><summary type="html">&lt;img alt="alternate text" src="/images/virtualenv-support-update.jpg" /&gt;
 &lt;p&gt;This is you: I &lt;strong&gt;use virtualenv all the time and I love it!&lt;/strong&gt; But I hate having to manually upgrade setuptools within my virtualenvs because the &lt;a class="reference external" href="https://pypi.python.org/pypi/setuptools#changes"&gt;PyPA has been so prolific with setuptools releases lately&lt;/a&gt;.&lt;/p&gt;
 &lt;p&gt;Actually this is me, but it may be you too. If this is you, you may be familiar with the following process. If not, you may want to be.&lt;/p&gt;
 &lt;div class="section" id="virtualenv-and-setuptools"&gt;
 &lt;p&gt;attempting to upgrade Setuptools…&lt;/p&gt;
 &lt;p&gt;attempting to upgrade Setuptools…&lt;/p&gt;
 &lt;/div&gt;
-</summary><category term="Django"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Hello Plone Updated</title><link href="http://blog.aclark.net/2014/01/11/hello-plone-updated/" rel="alternate"></link><updated>2014-01-11T12:30:00-05:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-01-11:2014/01/11/hello-plone-updated/</id><summary type="html">&lt;img alt="" src="images/hello-plone-updated.jpg" /&gt;
+</summary><category term="Django"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>Hello Plone Updated</title><link href="http://blog.aclark.net/2014/01/11/hello-plone-updated/" rel="alternate"></link><updated>2014-01-11T12:30:00-05:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-01-11:2014/01/11/hello-plone-updated/</id><summary type="html">&lt;img alt="alternate text" src="images/hello-plone-updated.jpg" /&gt;
 &lt;p&gt;Over two years ago I wrote a blog entry called &lt;a class="reference external" href="http://blog.aclark.net/2011/08/20/hello-plone/"&gt;&amp;quot;Hello, Plone!&amp;quot;&lt;/a&gt;. I've just updated it in order to:&lt;/p&gt;
 &lt;ul class="simple"&gt;
 &lt;li&gt;Change the wording&lt;/li&gt;
 &lt;/div&gt;
 </summary><category term="Plone"></category><category term="Python"></category></entry><entry><title>Pillow 2-3-0 is out!</title><link href="http://blog.aclark.net/2014/01/01/pillow-2-3-0-is-out/" rel="alternate"></link><updated>2014-01-01T18:30:00-05:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-01-01:2014/01/01/pillow-2-3-0-is-out/</id><summary type="html">&lt;p&gt;&lt;strong&gt;Pillow is the &amp;quot;friendly&amp;quot; PIL fork by Alex Clark and Contributors. PIL is the Python Imaging Library by Fredrik Lundh and Contributors&lt;/strong&gt;&lt;/p&gt;
 &lt;p&gt;Since Pillow 2.0, the Pillow Team has adopted a quarterly release cycle; as such, Pillow 2.3.0 has just been released. Here's what's new in this release:&lt;/p&gt;
-&lt;img alt="" src="/images/one-does-not-simply-make-a-release.jpg" /&gt;
+&lt;img alt="alternate text" src="/images/one-does-not-simply-make-a-release.jpg" /&gt;
 &lt;div class="section" id="id1"&gt;
 &lt;h2&gt;2.3.0 (2014-01-01)&lt;/h2&gt;
 &lt;ul class="simple"&gt;

feeds/Python.atom.xml

 &lt;div class="section" id="chapter-5"&gt;
 &lt;h2&gt;Chapter 5&lt;/h2&gt;
 &lt;p&gt;Chapter 5 is all about &amp;quot;working with file output&amp;quot;. For reference, here are some of the images produced by the examples in this chapter (I wrote &lt;tt class="docutils literal"&gt;jpg&lt;/tt&gt; files instead of &lt;tt class="docutils literal"&gt;png&lt;/tt&gt; files due to a problem with my libpng: &lt;a class="reference external" href="https://www.google.com/#q=RuntimeError%3A+Could+not+create+write+struct&amp;amp;safe=off"&gt;RuntimeError: Could not create write struct&lt;/a&gt;.)&lt;/p&gt;
-&lt;img alt="" src="http://blog.aclark.net/images/sinc1.jpg" /&gt;
-&lt;img alt="" src="http://blog.aclark.net/images/sinc3.jpg" /&gt;
+&lt;img alt="alternate text" src="http://blog.aclark.net/images/sinc1.jpg" /&gt;
+&lt;img alt="alternate text" src="http://blog.aclark.net/images/sinc3.jpg" /&gt;
 &lt;p&gt;Also covered in this chapter is &lt;a class="reference external" href="http://blog.aclark.net/images/sinc.pdf"&gt;pdf output&lt;/a&gt;.&lt;/p&gt;
 &lt;/div&gt;
 &lt;div class="section" id="chapter-6"&gt;
 &lt;/tbody&gt;
 &lt;/table&gt;
 &lt;/div&gt;
-</summary><category term="Django"></category><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>We Pioneer</title><link href="http://blog.aclark.net/2014/05/03/we-pioneer/" rel="alternate"></link><updated>2014-05-03T10:15:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-05-03:2014/05/03/we-pioneer/</id><summary type="html">&lt;img alt="" src="/images/we-pioneer.jpg" /&gt;
+</summary><category term="Django"></category><category term="Mozilla"></category><category term="Plone"></category><category term="Python"></category></entry><entry><title>We Pioneer</title><link href="http://blog.aclark.net/2014/05/03/we-pioneer/" rel="alternate"></link><updated>2014-05-03T10:15:00-04:00</updated><author><name>aclark</name></author><id>tag:blog.aclark.net,2014-05-03:2014/05/03/we-pioneer/</id><summary type="html">&lt;img alt="alternate text" src="/images/we-pioneer.jpg" /&gt;
 &lt;p&gt;One of the subjects I find myself thinking about a lot is: Plone (surprise!) In Plone-land, we deliver the &lt;strong&gt;best Python-based CMS money can't buy on top of an aging Zope 2 &amp;quot;application server&amp;quot;&lt;/strong&gt; mixed with newer Zope, Python, and other technologies. In short, this is a challenge.&lt;/p&gt;
 &lt;div class="section" id="diazo"&gt;
 &lt;h2