<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/wordpress-mu-1.2.5" -->
<rss version="0.92">
<channel>
	<title>OpenCore Software</title>
	<link>http://www.openplans.org/projects/opencore/blog</link>
	<description>Just another  weblog</description>
	<lastBuildDate>Thu, 24 Jul 2008 18:16:52 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>opencore 0.12.1 released</title>
		<description> Hi folks, opencore 0.12.1 was released today.
  
  This is a bugfix release with no user-visible new features. 
  

As with the previous release, it still doesn't work via easy_install, you have to get it by checking out the tag from subversion: https://svn.openplans.org/svn/opencore/branches/0.12.1 and then install ...</description>
		<link>http://www.openplans.org/projects/opencore/blog/2008/07/24/opencore-0121-released/</link>
			</item>
	<item>
		<title>Opencore 0.12.0 released</title>
		<description>

Get it from https://svn.openplans.org/svn/opencore/tags/0.12.0

I am not uploading a package to Pypi because we still have some work to do before opencore works as an egg. I expect to be working on this over the next few releases. For now, the most reliable way to install is still setup.py develop (or ...</description>
		<link>http://www.openplans.org/projects/opencore/blog/2008/07/11/opencore-0120-released/</link>
			</item>
	<item>
		<title>Opencore version number plan</title>
		<description>A decree from the release manager:

Until further notice, we will use the common three-component major.minor.patch version numbering scheme, as popularized by Apache and many other projects.
  


Major releases (e.g. 1.0.0, 2.0.0) indicate major featureset milestones or large backward incompatibilities.
  Our major release number will remain 0 until further ...</description>
		<link>http://www.openplans.org/projects/opencore/blog/2008/07/10/opencore-version-number-plan/</link>
			</item>
	<item>
		<title>Hi, I&#8217;m the Opencore Release Manager</title>
		<description>I'm going to be playing Opencore Release Manager, starting now. Let me explain what that means, and relay some plans.
Scope

I'm just talking about opencore, the Plone extension at the heart of the openplans software stack.

I'm not talking about any other part of the openplans software stack (tasktracker, wordpress, deliverance, ...)

I'm ...</description>
		<link>http://www.openplans.org/projects/opencore/blog/2008/06/27/hi-im-the-opencore-release-manager/</link>
			</item>
	<item>
		<title>Our Build Process</title>
		<description> Rob Miller has been thinking about zc.buildout lately, and providing a buildout-based bootstrap for our stack (even if it only calls out immediately to fassembler).&#160; This got me to thinking, and I finished a reflection post about fassembler.

At the end I almost talked myself into refactoring stuff to make ...</description>
		<link>http://www.openplans.org/projects/opencore/blog/2008/06/19/our-build-process/</link>
			</item>
	<item>
		<title>GrassyKnoll: a pluggable search engine in Python</title>
		<description> This past Tuesday I attended the NYC Python User's Group meeting at the offices of DayLife.

The presentation this week was by Peter Fein about GrassyKnoll, a text search engine written in Python.

From TOPP's point of view there are several interesting things about it:


  It could provide us with ...</description>
		<link>http://www.openplans.org/projects/opencore/blog/2008/06/19/grassyknoll-a-pluggable-search-engine-in-python/</link>
			</item>
	<item>
		<title>XML and ZPT</title>
		<description>
   So, Zope's handling of XML page templates is kind of broken.

As a result, all of opencore's page templates are parsed in ZPT's "html mode". This makes for some surprising validation behavior (e.g. unclosed tags is not an error, but putting content in a "link" tag is an ...</description>
		<link>http://www.openplans.org/projects/opencore/blog/2008/06/03/xml-and-zpt/</link>
			</item>
	<item>
		<title>Graphing memory vs. access log</title>
		<description>This showed up on my radar today. It's a cute little hack, if a bit rough. (I've already posted a couple patches).
  

&#160;

It could easily be generalized, there's nothing really zope-specific about it, all it really cares about is a path to a common-apache-format access log and the PID ...</description>
		<link>http://www.openplans.org/projects/opencore/blog/2008/05/30/graphing-memory-vs-access-log/</link>
			</item>
	<item>
		<title>NetSquared debrief</title>
		<description>I spent the last two days at the Cisco facility in San Jose, attending the third NetSquared conference. NetSquared is a conference that focuses on the intersection of activism and technology. It brings together people from NGOs, foundations, and technology providers to foster conversation, collaboration, fund-raising, and just to generally ...</description>
		<link>http://www.openplans.org/projects/opencore/blog/2008/05/30/netsquared-debrief/</link>
			</item>
	<item>
		<title>openplans.org permissions</title>
		<description> I've stated before one thing I like about openplans is the "simple" permission simple.&#160; I use the quotes because there are several caveats, one of which I'll address here.&#160; For a particular project, the permission system is essentially a 3x4 table:




  
    agent\project type
  ...</description>
		<link>http://www.openplans.org/projects/opencore/blog/2008/05/22/openplansorg-permissions/</link>
			</item>
</channel>
</rss>
