<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel">
    <title>gmane.comp.web.pyblosxom.devel</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2392"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2391"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2390"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2389"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2388"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2387"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2386"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2385"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2384"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2383"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2382"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2381"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2380"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2379"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2378"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2377"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2376"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2375"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2374"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2373"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2392">
    <title>Fwd: Pyblosxom plugin (breadcrumbs)</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2392</link>
    <description>&lt;pre&gt;Florian: I'm forwarding this to the pyblosxom-devel mailing list because 
I don't have time to do anything with it. Thank you for sending this 
email, though. A breadcrumbs plugin sounds super!

Pyblosxom devs: If someone wants to add the plugin, the repository is 
the pyblosxom-web one on gitorious. Let me know when it's added and I 
can rebuild the site.

If someone wants to look into the pi_bl thing, it's probably prudent to 
figure out what the behavior should be, write some tests, apply the fix, 
and then we can go from there. It's possible the behavior is documented. 
I vaguely remember there are a few template variables that were 
sketchy--this might have been one of them.

Rock on!

/will


-------- Original Message --------
Subject: Pyblosxom plugin (breadcrumbs)
Date: Wed, 16 May 2012 21:35:52 +0200
From: Florian Bäuerle &amp;lt;florian.bae&amp;lt; at &amp;gt;googlemail.com&amp;gt;
To: willg&amp;lt; at &amp;gt;bluesock.org

Hi, my name is Florian Bäuerle.
I recently wrote a little Plugin for Pyblosxom that generates a
Breadcrumb-Path.
It is only w&lt;/pre&gt;</description>
    <dc:creator>will kahn-greene</dc:creator>
    <dc:date>2012-05-17T00:19:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2391">
    <title>Re: Patch for pagination in static-rendering mode</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2391</link>
    <description>&lt;pre&gt;Another thing that might be considered, by the way, to make plugins for
changing the pagination style easier, would be to add another callback so
that the plugin author would not have to rewrite the whole of
truncatelist (or copy it).  Instead he'd be passed in the number of
subpages, all their URLs, and the page number of the current page.

On Fri, Mar 16, 2012 at 04:54:20PM -0400, Norman Yarvin wrote:

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
&lt;/pre&gt;</description>
    <dc:creator>Norman Yarvin</dc:creator>
    <dc:date>2012-03-16T21:08:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2390">
    <title>Re: Patch for pagination in static-rendering mode</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2390</link>
    <description>&lt;pre&gt;Most of the code I added can easily be moved out to a plugin, since it
falls under the cb_truncatelist callback which the existing 'paginate'
plugin uses.  (That's why that plugin should still work.)

The remainder of what I added is core infrastructure that would probably
be necessary to support pagination under static rendering however it was
done.  Without it, a plugin would have to find some way to add more files
to the list of files to be rendered statically, when it found that an
index page overflowed, and to do that in the middle of said rendering.
(I didn't see a callback that would permit that, but perhaps there is
one.)  Then some other piece of code would have to detect that the page
to be rendered is a followup page, and render it accordingly.  It's
simpler to just add a loop in the static-rendering code that iterates
through the followup pages, passing down a variable which indicates 'now
render followup page N', which is what I did.

I considered moving the code that falls under cb_truncatelist&lt;/pre&gt;</description>
    <dc:creator>Norman Yarvin</dc:creator>
    <dc:date>2012-03-16T20:54:20</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2389">
    <title>Re: Patch for pagination in static-rendering mode</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2389</link>
    <description>&lt;pre&gt;I don't think it should be in the core. It's less an issue of "who 
would never use pagination" and more an issue of "are there different 
kinds of pagination behavior and thus should be supported in plugins". 
So I'm -1 on adding this to the core.

I'll toss this and the patch into the issue tracker at some point and 
someone can look at absorbing the changes into the pagination plugin.

/will


On Fri 16 Mar 2012 05:03:34 AM EDT, Norman Yarvin wrote:

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
&lt;/pre&gt;</description>
    <dc:creator>will kahn-greene</dc:creator>
    <dc:date>2012-03-16T11:21:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2388">
    <title>Patch for pagination in static-rendering mode</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2388</link>
    <description>&lt;pre&gt;Attached is a patch that enables pagination in static-rendering mode,
pagination being the rendering of index pages which are longer than
num_entries by writing them out to multiple pages, combined with the
production of navigation strings which the user can include in the
templates for those pages.  Since:

-- doing this as a plugin seemed somewhere between painful and
impossible, and

-- I think this really should be core functionality anyway,

I went ahead and implemented the whole thing in the core.  It should work
for dynamic rendering, too (or whatever one calls the opposite of static
rendering), but I haven't tested that mode.  It is meant to supersede the
present "paginate" plugin, but the latter should still work (again,
untested).  It uses all the same config variables, except for
"paginate_count_from", which I thought was far too much in the
bikeshedding direction to be worth saving.  The variable
"paginate_linkstyle" accepts, besides the old settings (0 or 1), the more
descriptive settings "1 &lt;/pre&gt;</description>
    <dc:creator>Norman Yarvin</dc:creator>
    <dc:date>2012-03-16T09:03:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2387">
    <title>Re: 1.5 status -- anything more to do?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2387</link>
    <description>&lt;pre&gt;
Anything is fine by me.  Patches sent to the mailing list, pull requests 
on github, issues on github with comments on how to fix the issue, pinging 
me on IRC, ...


On Sat, 17 Dec 2011, Akai wrote:

------------------------------------------------------------------------------
Learn Windows Azure Live!  Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for 
developers. It will provide a great way to learn Windows Azure and what it 
provides. You can attend the event by watching it streamed LIVE online.  
Learn more at http://p.sf.net/sfu/ms-windowsazure
&lt;/pre&gt;</description>
    <dc:creator>Will Kahn-Greene</dc:creator>
    <dc:date>2011-12-17T22:46:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2386">
    <title>1.5 status -- anything more to do?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2386</link>
    <description>&lt;pre&gt;
I worked through the remaining bugs sitting in the 1.5 milestone today. 
Now there are no more bugs sitting in the 1.5 milestone.

If there's anything outstanding that I haven't finished up, let me know in 
the next two days.  Barring any issues, I'm going to ship 1.5 next week.

After 1.5 goes out, I'm going to spend some time moving interesting bugs 
to the issue tracker on github and then take a hiatus from Pyblosxom 
development for a while.  I will continue to work through patches 
submitted by other people whether they code or docs or fixes to the 
website.

/will

------------------------------------------------------------------------------
Learn Windows Azure Live!  Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for 
developers. It will provide a great way to learn Windows Azure and what it 
provides. You can attend the event by watching it streamed LIVE online.  
Learn more at http://p.sf.net/sfu/ms-windowsazure
&lt;/pre&gt;</description>
    <dc:creator>Will Kahn-Greene</dc:creator>
    <dc:date>2011-12-17T15:17:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2385">
    <title>Re: project infrastructure</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2385</link>
    <description>&lt;pre&gt;I know both well... :-) what I implied is that the git repo is essentially the same. I hardly ever view the web ui of my githhub projects, and you can always mix with better infrastructure, ie bug trackers from assembla.com or whatnot.
That having said, github is certainly cool.
Sebastian





------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
&lt;/pre&gt;</description>
    <dc:creator>Sebastian-7CH+t18bm0uELgA04lAiVw&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2011-12-03T19:38:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2384">
    <title>Re: project infrastructure</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2384</link>
    <description>&lt;pre&gt;
You removed the context for that statement in your reply.  It doesn't 
lock us in because I don't really care about leaving issues if we 
switch trackers.



Pretty sure I've talked about this already, but I'm game for iterating 
through it again.

Roundup doesn't have milestones by default.  I've added mediocre 
milestone stuff based on the original round of milestone stuff that 
Jack at OpenHatch did.  However, the urls for milestones are awful and 
generally I find the ui to be problematic.  There are bugs in Roundup 
that irritate me.  One of them is that the ExportCSV action doesn't 
check the querystring _before_ writing stuff to output.  So when it 
hits a problem, it's already written stuff to output and thus you get 
back an HTTP 200 response with gibberish in it.  The problem there is 
that Google bot and other search engines for some reason put bad stuff 
in the querystring and thus I get a ton of error emails.  I tried to 
fix this in Roundup and write up a test case, but the Roundup code is 
re&lt;/pre&gt;</description>
    <dc:creator>will kahn-greene</dc:creator>
    <dc:date>2011-12-02T19:21:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2383">
    <title>Re: project infrastructure</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2383</link>
    <description>&lt;pre&gt;On Fri, 02 Dec 2011 13:23:03 -0500
will kahn-greene &amp;lt;willg-kCrUpeWqBLNg9hUCZPvPmw&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


GH issues doesn't lock us in? is that a typo or am i missing something?


what's wrong with roundup?

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
&lt;/pre&gt;</description>
    <dc:creator>Dieter Plaetinck</dc:creator>
    <dc:date>2011-12-02T18:37:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2382">
    <title>Re: project infrastructure</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2382</link>
    <description>&lt;pre&gt;
I dig what you're saying.  I definitely don't want to repeat another SF 
situation--that sucked.

I currently plan to use github for code, the issue tracker, and patch 
workflow.  We can trivially move the code elsewhere.  The patch 
workflow is transient, so if we move elsewhere we'll lose that and 
change workflows.

That brings us to the issue tracker.  I'm pretty ok with ditching 
issues in one system and moving to a new system.  More often than not, 
issues that languish are either fixed, uninteresting, not fleshed out 
or in some state where ditching it isn't a big deal.  I don't want this 
project to accrue task-debt.  We either work on things we're interested 
in, or we don't.  The set of issues we're interested in working on 
changes.  If I had my druthers, I'd have our bug system auto-expire 
bugs that haven't been touched in a couple of months.  Given that, 
switching to the github issue tracker is fine and doesn't lock us in.  
I'm game for hosting our own bug tracker, but I don't want to use Tr&lt;/pre&gt;</description>
    <dc:creator>will kahn-greene</dc:creator>
    <dc:date>2011-12-02T18:23:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2381">
    <title>Re: project infrastructure</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2381</link>
    <description>&lt;pre&gt;
Github can host the project website for you as well, and a wiki.

The one disadvantage is that it's not open source whereas gitorious is.
Hosting your git repo on github doesn't tie you down to anything as you
can always move it somewhere else if you want to. But the more you come
to depend on github's extra features like the issue tracker, the wiki,
etc., the more you're becoming dependent on a proprietary platform.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
&lt;/pre&gt;</description>
    <dc:creator>seanh</dc:creator>
    <dc:date>2011-12-02T18:05:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2380">
    <title>Re: project infrastructure</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2380</link>
    <description>&lt;pre&gt;On Thu, 01 Dec 2011 16:25:18 +0100
Sebastian Spaeth &amp;lt;Sebastian-6b102mguJBqELgA04lAiVw&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


I know you meant that as a joke, but seriously, github and gitorious are quite different.
personally i find gitorious very hard to navigate, their UI/menus aren't very well thought out.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d_______________________________________________
Pyblosxom-devel mailing list
Pyblosxom-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
&lt;/pre&gt;</description>
    <dc:creator>Dieter Plaetinck</dc:creator>
    <dc:date>2011-12-02T08:10:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2379">
    <title>Re: project infrastructure</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2379</link>
    <description>&lt;pre&gt;
A bit lateish, but I have no strong opinions on gitorious vs github (I
think keeping the repo at gitorious would be fine). But I am always for
hosting things at existing infrastructure, relieving you from the burden
of maintaining that. So using some bug tracker at github, assembla or
whereever, sounds good to me. github or gitorious? ppff, it's just a
different git&amp;lt; at &amp;gt; URL ;-)

Sebastian
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d_______________________________________________
Pyblosxom-devel mailing list
Pyblosxom-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f&amp;lt; at &amp;gt;public.gmane.org
https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
&lt;/pre&gt;</description>
    <dc:creator>Sebastian Spaeth</dc:creator>
    <dc:date>2011-12-01T15:25:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2378">
    <title>Re: project infrastructure</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2378</link>
    <description>&lt;pre&gt;
Heh.. That was my first time trying to look for pyblosxom in Gitorious. Then 
again, was very new to this 'git' thing, and forks, and clones, etc. But quite 
at home with our install at the office.

So github it is? +1 on that for me.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
&lt;/pre&gt;</description>
    <dc:creator>wari.wahab-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2011-11-24T09:39:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2377">
    <title>Re: project infrastructure</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2377</link>
    <description>&lt;pre&gt;On Thu, 24 Nov 2011 10:30:05 +0800
"Wari Wahab" &amp;lt;wari-kHev7oNUZbzsrOwW+9ziJQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:


because it's a really good application, integrates well, is free and the people who run it
are capable and very active in open source communities (ruby, git and more)

personally I find it a pain to navigate in gitorious.  I have the impression that what I'm looking for
is usually not where I expect to find it.

The last time this came up I was pro github, and I still am :)


Dieter





------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
&lt;/pre&gt;</description>
    <dc:creator>Dieter Plaetinck</dc:creator>
    <dc:date>2011-11-24T08:00:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2376">
    <title>Re: project infrastructure</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2376</link>
    <description>&lt;pre&gt;&amp;lt;quote who="Will Kahn-Greene"&amp;gt;

Wow, hey, I'm totally not against this. I use Gitorious on our private
install
in our company and it's a great product for that. Since we have Redmine as
our
bugtracker/documentation store, these two worked somewhat seemlessly and has
been something that the company is accustomed to.

Moving to Github is definitely a plus as you gain the all-in-one
featureset of
a bug tracker, repository, etc. And to top it all up, I love the edit-in-
place-auto-fork-and-merge-request in less than a minute of kung-fu moves
feature, etc.

And the community around it, it makes Gitorious like a quiet boy sitting in
the corner. I have no idea why Github is so popular.


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense&lt;/pre&gt;</description>
    <dc:creator>Wari Wahab</dc:creator>
    <dc:date>2011-11-24T02:30:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2375">
    <title>Re: project infrastructure</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2375</link>
    <description>&lt;pre&gt;
Makes sense to me.  Github is nice.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
&lt;/pre&gt;</description>
    <dc:creator>Tim Gray</dc:creator>
    <dc:date>2011-11-24T03:13:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2374">
    <title>project infrastructure</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2374</link>
    <description>&lt;pre&gt;
I updated the roundup package on bluesock (the server that hosts the 
Pyblosxom bug tracker) and inadvertently stomped on the fix I made to 
roundup.  Then I started getting lots of error emails from roundup because 
it's "helpful".  Took me about 30 minutes to figure out how I fixed it the 
last time and re-fix it.  Irritating.

That got me thinking.  A while back, when we talked about switching to git 
and picking a host, I remember a lot of people said they already had 
github accounts.  I picked gitorious because at the time is was close 
enough feature-wise and it was Free Software.  I picked roundup because it 
seemed like a decent choice.

At this point, I want to revisit those decisions.  I'm thinking of moving 
things around in this way:

1. Move from gitorious to github.  In doing this, we gain post-commit 
hooks some of which are wildly useful, an issue tracker, inline comments 
for pull requests, probably an order of magnitude more people who already 
have github accounts and who are used to dri&lt;/pre&gt;</description>
    <dc:creator>Will Kahn-Greene</dc:creator>
    <dc:date>2011-11-24T00:20:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2373">
    <title>Re: Installing plugins</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2373</link>
    <description>&lt;pre&gt;I can't remember if I mentioned it or not, yet, but this is one of the
other things I changed last week: all core plugins have documentation in
the Pyblosxom manual now.  It's all in "part 2" of the manual:

http://pyblosxom.bluesock.org/1.5/index.html#part-2-core-plugin-documentation

The documentation is extracted from the docstring at the top of the file
with a script.  In this way, we can update the plugins and the
documentation for the plugins all at once and then it gets pulled into
the manual automatically.

This also solves the problem of "Where's the damn docs for this plugin I
enabled with 'Pyblosxom.plugins.xyz'?"

Also, I did some minor renaming:

* rst -&amp;gt; rst_parser
* markdown -&amp;gt; markdown_parser

Changes are covered in the updated WHATSNEW section for 1.5rc4 (which
might end up being 1.5final--we'll see):

http://pyblosxom.bluesock.org/1.5/whatsnew.html#what-s-new-in-1-5-rc4-in-development

/will


On 11/09/2011 07:26 AM, will kahn-greene wrote:

-------------------------------------------------&lt;/pre&gt;</description>
    <dc:creator>will kahn-greene</dc:creator>
    <dc:date>2011-11-09T12:33:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2372">
    <title>Re: Installing plugins</title>
    <link>http://permalink.gmane.org/gmane.comp.web.pyblosxom.devel/2372</link>
    <description>&lt;pre&gt;The comments plugin requires more setup than just adding it to the 
load_plugins list.  There's documentation here:

http://pyblosxom.bluesock.org/1.5/plugins/comments.html

Hope that helps!

/will


On Tue 08 Nov 2011 08:18:56 PM EST, Akai wrote:

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
&lt;/pre&gt;</description>
    <dc:creator>will kahn-greene</dc:creator>
    <dc:date>2011-11-09T12:26:19</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.web.pyblosxom.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.web.pyblosxom.devel</link>
  </textinput>
</rdf:RDF>

