<?xml version="1.0"?>

<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns="http://purl.org/rss/1.0/"
>
<channel rdf:about="http://planet.zope.org">
<title>Planet Zope.org</title>
<link>http://planet.zope.org</link>
<description>
Zope related news
</description>

<image rdf:resource="http://www.zope.org/logo.png" />
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2006-08-27T07:38:03Z</sy:updateBase>

<items>
<rdf:Seq>
<rdf:li resource="http://mg.pov.lt/blog/you-gotta-love-profiling" />

<rdf:li resource="http://baijum81.livejournal.com/33122.html" />

<rdf:li resource="http://blog.repoze.org/Zope.de%20Reviews%20BFG%20Book/" />

<rdf:li resource="http://mg.pov.lt/blog/volunteeritis" />

<rdf:li resource="http://regebro.wordpress.com/2010/03/04/the-knights-who-say-py/" />

<rdf:li resource="http://mg.pov.lt/blog/weekly-zope-irc-meeting" />

<rdf:li resource="http://betabug.ch/blogs/ch-athens/1048" />

<rdf:li resource="http://plone.org/news/thismonthinplone-march2010" />

<rdf:li resource="http://blog.redturtle.it/redturtle-blog/integration-of-plonegazette-and-plone.app.discussion" />

<rdf:li resource="http://www.peterbe.com/plog/massive-improvement-on-sorting-a-fat-list" />

<rdf:li resource="http://ruslanspivak.com/2010/02/26/preview-of-grok-1-0-web-development-by-carlos-de-la-guardia/" />

<rdf:li resource="http://baijum81.livejournal.com/32740.html" />

<rdf:li resource="http://blog.repoze.org/PyCon%202010%3A%20%20repoze.bfg%20Sprinting/" />

<rdf:li resource="http://maurits.vanrees.org/weblog/archive/2010/02/plone-3-for-education" />

<rdf:li resource="http://mockit.blogspot.com/2010/02/using-chameleon-in-django.html" />

</rdf:Seq>
</items>
</channel>

<item rdf:about="http://mg.pov.lt/blog/you-gotta-love-profiling">
  <title><![CDATA[You've got to love profiling]]></title>
  <link>http://mg.pov.lt/blog/you-gotta-love-profiling</link>
  <description><![CDATA[
Yesterday I slashed 50% of run time from our applications functional test
suite by modifying a single function.  I had no idea that function was
responsible for 50% of the run time until I started profiling.<p>
<p>
<p>
<p>
<p>
 and stores
the results in prof.data.<p>
<p>
<p>
<p>

profile viewer, which displays the results visually:<p>
<p>
<p>

The square map display of RunSnakeRun, with the 'render_restructured_text'
function highlighted.<p>

Who knew that ReStructuredText rendering could be such a time waster?  A
short caching decorator and the test suite is twice as fast.  The whole
exercise took me less than an hour.  I should've done it sooner.<p>
<p>

  
  from the standard library lets you load and display profiler results from the
  command line (try 
  
  converts Python profiler data files to a format that the popular profiler
  visualization tool 
  can understand.  It's somewhat less useful now that RunSnakeRun exists.
   by
  yours truly has decorators for easily profiling individual functions instead
  of entire scripts.
   hook
  up the profiler as WSGI middleware for easy profiling of web apps.
  ]]></description>
  <dc:subject></dc:subject>
  <dc:creator>Random notes from mg</dc:creator>
  <dc:date>2010-03-06T17:49:00Z</dc:date>
</item>
<item rdf:about="http://baijum81.livejournal.com/33122.html">
  <title><![CDATA[Building a healthy community around FOSS project]]></title>
  <link>http://baijum81.livejournal.com/33122.html</link>
  <description><![CDATA[
Dear Lazyweb, I am looking for suggestions for building a healthy community around one of my FOSS project.&nbsp; Recently I initiated re-launching of&nbsp; These days, I am thinking more about this project and its success.&nbsp; I know, a FOSS&nbsp;project is not just some source code released. There should be active contributors, regular community activities, good documentation, presence in various events etc.&nbsp; So, how to attract contributors to this project.&nbsp; How to build a healthy successful community around this project.&nbsp; At this point, I have taken the role of &quot;self-assigned release manager&quot;.&nbsp; I think that's a good way to lead this project. I am looking for your thoughts :)
  ]]></description>
  <dc:subject>zope3</dc:subject>
<dc:subject>python</dc:subject>
  <dc:creator>For surely there is an end ...</dc:creator>
  <dc:date>2010-03-06T05:19:44Z</dc:date>
</item>
<item rdf:about="http://blog.repoze.org/Zope.de%20Reviews%20BFG%20Book/">
  <title><![CDATA[Zope.de Reviews BFG Book]]></title>
  <link>http://blog.repoze.org/Zope.de%20Reviews%20BFG%20Book/</link>
  <description><![CDATA[

  ]]></description>
  <dc:subject></dc:subject>
  <dc:creator>Repoze Blog RSS Feed</dc:creator>
  <dc:date>2010-03-06T04:00:00Z</dc:date>
</item>
<item rdf:about="http://mg.pov.lt/blog/volunteeritis">
  <title><![CDATA[Bye, bye, free time!]]></title>
  <link>http://mg.pov.lt/blog/volunteeritis</link>
  <description><![CDATA[
Read and review Python
      Testing: Beginner's GuideGrok
      1.0 Web Development for Packt.  (The links are trackable to my blog,
    but I'm not getting anything out of it.  Other than free copies of the
    e-books, which I already received, in exchange for a promise to review them
    on this blog.)
  
  
    Help 
    folks set up continuous integration (most likely , while powerful, has a steep
    learning curve).
  
  
    Think about becoming the buildbotmaster for Zope.  Originally I intended
    to volunteer to set up a few buildbots for various Zopeish projects
    (ZTK, BlueBream, Grok, Zope 2) since half of the existing
      ones were down or broken.  Then various people fixed some of the
    broken ones and other people chimed in mentioning existing buildbots that
    nobody else knew about.  There is a need for somebody to coordinate all
    this activity: make sure we have up-to-date test results for all kinds of
    projects, aggregate them in one place, chase up build slaves for exotic
    OSes (i.e. Windows)...  I don't think I'm well suited for this kind of
    organisational activity.
  
  
    Push along the various scratch-my-itch open source projects (,
      ).
  
  
    No idea what, but I've been wanting to do something for .  Something small, given the copious
    amounts of free time I have.
  
  
    Then there's the paying work.  On the plus side, there are opportunities
    for fun there (today I slashed functional test run time by a half, by
    adding a small caching decorator in front of a single function.
    
    and 
    rule!)
  
  
    You know what, scratch the Zope buildbotmaster idea.  Maybe I can do
    something technical there, e.g. a cron script to ping the various buildbot,
    scrape HTML/parse emails and aggregate build results.  Maybe.
  
  
    I hope I don't get 
    again.  Because that would suck.  Again.  Been there, done that, didn't
    even get a T-shirt.
  <p>

I really ought to read Getting Things Done.  Reading it has been on my
todo-list for
  ]]></description>
  <dc:subject></dc:subject>
  <dc:creator>Random notes from mg</dc:creator>
  <dc:date>2010-03-05T20:02:41Z</dc:date>
</item>
<item rdf:about="http://regebro.wordpress.com/2010/03/04/the-knights-who-say-py/">
  <title><![CDATA[The Knights Who Say Py!]]></title>
  <link>http://regebro.wordpress.com/2010/03/04/the-knights-who-say-py/</link>
  <description><![CDATA[
---
  ]]></description>
  <dc:subject>plone</dc:subject>
<dc:subject>python</dc:subject>
<dc:subject>irc</dc:subject>
  <dc:creator>Lennart Regebro: Plone consulting</dc:creator>
  <dc:date>2010-03-04T11:38:06Z</dc:date>
</item>
<item rdf:about="http://mg.pov.lt/blog/weekly-zope-irc-meeting">
  <title><![CDATA[Weekly Zope developer IRC meetings]]></title>
  <link>http://mg.pov.lt/blog/weekly-zope-irc-meeting</link>
  <description><![CDATA[
On Tuesday we started what will hopefully become a tradition: weekly IRC
meetings for Zope developers.  Topics covered include buildbot organization and
maintenance, open issues with the ZTK development process, and the fate of Zope
3.5 (= BlueBream 1.0).<p>

  to the mailing list.<p>
My take on this can be summed up as: Zope ain't dead yet!  The project has
fragmented a bit (Zope 2, Zope Toolkit, Grok, BlueBream, Repoze), but we all
share a set of core packages and we want to keep them healthy.<p>
Next meeting is also happening on a Tuesday, at 15:00 UTC on #zope in
FreeNode.
  ]]></description>
  <dc:subject></dc:subject>
  <dc:creator>Random notes from mg</dc:creator>
  <dc:date>2010-03-03T10:09:23Z</dc:date>
</item>
<item rdf:about="http://betabug.ch/blogs/ch-athens/1048">
  <title><![CDATA[Zope 2.12 eggified Installation Stuff Learned]]></title>
  <link>http://betabug.ch/blogs/ch-athens/1048</link>
  <description><![CDATA[
There was a short zope-dev meeting on #zope today. I'm not a zope-dev, but after they were done,
I asked a question^W^W^Wgriped a bit about the new "eggified" Zope 2.12 install procedure. A
big discussion ensued. I learned / noticed a couple of things:
  ]]></description>
  <dc:subject>zope</dc:subject>
  <dc:creator>ch-athens</dc:creator>
  <dc:date>2010-03-02T21:12:16Z</dc:date>
</item>
<item rdf:about="http://plone.org/news/thismonthinplone-march2010">
  <title><![CDATA[This Month in Plone - March 2010]]></title>
  <link>http://plone.org/news/thismonthinplone-march2010</link>
  <description><![CDATA[
It's been busy month for the Plone community as events filled up the 2010 calendar, the Plone Foundation announces its newest members, and the final alpha release before Plone 4 moves to Beta testing.
  ]]></description>
  <dc:subject></dc:subject>
  <dc:creator>Plone News</dc:creator>
  <dc:date>2010-03-02T10:14:24Z</dc:date>
</item>
<item rdf:about="http://blog.redturtle.it/redturtle-blog/integration-of-plonegazette-and-plone.app.discussion">
  <title><![CDATA[Integration of PloneGazette with plone.app.discussion]]></title>
  <link>http://blog.redturtle.it/redturtle-blog/integration-of-plonegazette-and-plone.app.discussion</link>
  <description><![CDATA[
The new product collective.discussionintegration.plonegazette provides the integration of PloneGazette and plone.app.discussion.
  ]]></description>
  <dc:subject>Plone</dc:subject>
<dc:subject>english</dc:subject>
  <dc:creator>RedTurtle Technology</dc:creator>
  <dc:date>2010-03-02T08:32:52Z</dc:date>
</item>
<item rdf:about="http://www.peterbe.com/plog/massive-improvement-on-sorting-a-fat-list">
  <title><![CDATA[Massive improvement on sorting a fat list]]></title>
  <link>http://www.peterbe.com/plog/massive-improvement-on-sorting-a-fat-list</link>
  <description><![CDATA[
]
  ]]></description>
  <dc:subject>Python</dc:subject>
  <dc:creator>Peterbe.com</dc:creator>
  <dc:date>2010-02-28T14:00:00Z</dc:date>
</item>
<item rdf:about="http://ruslanspivak.com/2010/02/26/preview-of-grok-1-0-web-development-by-carlos-de-la-guardia/">
  <title><![CDATA[Preview of Grok 1.0 Web Development by Carlos de la Guardia]]></title>
  <link>http://ruslanspivak.com/2010/02/26/preview-of-grok-1-0-web-development-by-carlos-de-la-guardia/</link>
  <description><![CDATA[
---
  ]]></description>
  <dc:subject>book</dc:subject>
<dc:subject>grok</dc:subject>
<dc:subject>python</dc:subject>
  <dc:creator>Ruslan's Blog</dc:creator>
  <dc:date>2010-02-26T06:20:50Z</dc:date>
</item>
<item rdf:about="http://baijum81.livejournal.com/32740.html">
  <title><![CDATA[Buildout recipe list is growing]]></title>
  <link>http://baijum81.livejournal.com/32740.html</link>
  <description><![CDATA[
Now there are more than  .
  ]]></description>
  <dc:subject>zope3</dc:subject>
<dc:subject>python</dc:subject>
  <dc:creator>For surely there is an end ...</dc:creator>
  <dc:date>2010-02-25T07:41:51Z</dc:date>
</item>
<item rdf:about="http://blog.repoze.org/PyCon%202010%3A%20%20repoze.bfg%20Sprinting/">
  <title><![CDATA[PyCon 2010:  repoze.bfg Sprinting]]></title>
  <link>http://blog.repoze.org/PyCon%202010%3A%20%20repoze.bfg%20Sprinting/</link>
  <description><![CDATA[
Andrew Sawyers, Chris Shenton, Shane Hathaway, and Reed O'Brien worked on an
example "BFG Cookbook" application, intended to run in the Google App Engine
cloud.  They succeeded in indirecting the storage of the recipe entries, with
working backends based on the GAE Big Table API, ZODB, Mongo, and an in-memory
(nonpersistent) storage.<p>
<p>
<p>

Reed also worked on re-doing the Mongo-based URL shortener he wrote at last
year's sprint, this time using the Ming bindings.  He is working to have
an example which uses none of the  packaages, in order to show
how BFG can be used in a variety of ways.
Chris McDonough and Chris Rossi have been sprinting with the Pylons and
TurboGears folks on a package code-named "Marco."  Marco moves some of the
dispatching logic of BFG down into a package intended to be useful as the
basis for a version of Pylons:  if it succeeds, Pylons and BFG would become
"personality" layers on top of the shared Marco library.<p>
<p>
Tres Seaver has been working on a CMS architecture which he has been
mulling for a long while now, code-named "Bonzai".  The architecture
decouples "asset repositories" from the "site layout" applications which
consume them, imposing a RESTy service layer between the two.<p>
<p>
In reaction to the perhaps overly cute mascots adopted by a certain other
nameless framework, the BFG sprint team has adopted the "flying" or "war" pig
as a mascot (
  ]]></description>
  <dc:subject></dc:subject>
  <dc:creator>Repoze Blog RSS Feed</dc:creator>
  <dc:date>2010-02-24T04:00:00Z</dc:date>
</item>
<item rdf:about="http://maurits.vanrees.org/weblog/archive/2010/02/plone-3-for-education">
  <title><![CDATA[A final look at Erik Rose: Plone 3 for Education]]></title>
  <link>http://maurits.vanrees.org/weblog/archive/2010/02/plone-3-for-education</link>
  <description><![CDATA[
on the Plone 3 for Education book by
Erik Rose, here are my final impressions.  I will cover the whole book
now.  To make it very practical, for each chapter I will recommend
which of my  at Zest Software should read it.  For some it
will just be a reminder of what they already know, but freshening up
your knowledge and perhaps picking up some small tips on the go are
always good.  Note that some have multiple roles, so someone may be
listed first as trainer and later as programmer.<p>

This is about creative application of the default Plone content types.
It explains how to use some features of standard Plone, like
collections, large folders and default pages.  Recommended for Esther
(Partner), Robin (Marketing/Sales), and Angela (Management Assistant).<p>
<p>
The Plone4ArtistsCalendar product is used as a nice way of showing
events; this looks like a good solution for sites with lots of events.
The chapter teaches best practices for using events and collections.
You also get some tips about how best to apply security and
permissions.  Recommended for Esther (Partner), Robin
(Marketing/Sales), and perhaps Mirella (Project Manager), mostly because they may be doing content management on some client sites or on our own site.<p>
<p>
The add-on product Faculty/Staff Directory can be seen as a
departmental website in a box.  It uses membrane, remember and
relations.  It is a versatile product, which could be useful in
several occasions.  Recommended for Jean-Paul (Partner) and Robin
(Marketing/Sales): they should know this product is available; also
recommended for the programmers (Mark, Fred, Vincent, me): they should
see if this product fits the bill, before making something from
scratch.  It can also serve as a good example of how to use the
membrane and remember products.<p>
<p>
The standard product shown in the previous chapter is now extended
using archetypes.schemaextender.  Recommended for Mark, Fred and
Vincent (programmers): look at this to freshen up your knowledge of
archetypes.schemaextender (or for your first look at this).<p>
<p>
This is a look at the out-of-the-box blogging potential of Plone
(which may be enough), and at add-on products.  Erik calls these &quot;free
as in puppies&quot;: they are cute, but you should be aware that they come
with responsibilities.  All add-on products that you may want to add
in your site, should first be tested on a copy of that site, including
trying to uninstall it.  The QuillsEnabled and Scrawl products are
introduced for blogging, including using them in combination if
needed.  For forums the judgement is clear: use Ploneboard.
Recommended for Mark as consultant and Fred as consultant/trainer.<p>
<p>
For embedding audio and video, Erik recommends collective.flowplayer
as the most flexible and trouble-free solution.  Plone4ArtistsVideo is
mentioned once for podcasting support, but perhaps Plone4ArtistsAudio
is meant, as that one is explained.  In some cases, for example
embedding YouTube videos, you need to write some pure html yourself,
so enabling the  tags is explained; I did not
notice before that there was an embed-tab button that you can enable
in Site Setup, Visual Editor, Toolbar.  Again recommended for Mark as
consultant and Fred as trainer.<p>
<p>
.
Recommended for Esther (Partner), Robin (Marketing/Sales), Mark
(Consultant), Fred (Trainer).  This was a handy chapter for me as well; I just <p>
<p>
This chapter explains the Zope 2 way versus the Zope 3 way of theming.
Depending on which parts of your site you want to style, you will need
to learn both ways.  You will learn about through-the-web versus
development on the file system.  You use paster for creating a basic
theme product.  Erik shows  as the easiest way of
overriding templates from Plone's sometimes difficult viewlet and
portlet machinery.  Recommended for Mirella and Laurens (CSS
Specialists) for perhaps a better understanding of <p>
<p>
This is all about buildout, a zeo setup, CacheFu, Squid and Apache.
Recommended for the programmers when dealing with Squid instead of the
varnish that we mostly use; and a fresh look at the CacheFu settings
would not hurt.<p>
<p>
The instructions to pack manually give wrong directions, which will
have you end up in the ZMI in the Plone Site root, without a Zope
Control Panel in sight.  Instead you should simply go to Site Setup
and then to Maintenance.  Other than that, this chapter has no
surprises, but if you come working for us as 
this is the first chapter you should read.<p>
<p>
Plone 3 for Education is a very practical book.  It shows you a safe
route through Plone land, giving solid advice that will keep you out
of the pitfalls of this great CMS.
Disclaimer: I got this book for free from Packt Publishing in exchange
for a review.  Ordering the book via one of the  in this article
will land me some money.
  ]]></description>
  <dc:subject>books</dc:subject>
<dc:subject>plone</dc:subject>
<dc:subject>zest</dc:subject>
  <dc:creator>Weblog</dc:creator>
  <dc:date>2010-02-23T23:37:27Z</dc:date>
</item>
<item rdf:about="http://mockit.blogspot.com/2010/02/using-chameleon-in-django.html">
  <title><![CDATA[Using Chameleon in Django]]></title>
  <link>http://mockit.blogspot.com/2010/02/using-chameleon-in-django.html</link>
  <description><![CDATA[
Using alternative template engines is a popular pastime these days and so I thought I'd give
  ]]></description>
  <dc:subject></dc:subject>
  <dc:creator>Mock It!</dc:creator>
  <dc:date>2010-02-23T06:50:00Z</dc:date>
</item>
</rdf:RDF> 
<!-- //creation//ok// -->