Etria Lists

Hi everyone. :)

I thought I should mention that I got my migration to work last week:

  http://svn.qutang.net/svn/projects/COREBlog2QuillsMigration/trunk/migrateCOREBlog2Quills.py

I didn't really want to revive the External Method into trunk of
Quills, and I wanted to version control all of my edits without
spamming people who listen to Plone SVN, so that's why it's here.

I preserved the original copyright and added Reinout and myself.  I
don't know who all have worked on this but I figure adding one name is
better than just myself. ;)

This script has a variable that must be set which is the name of the
existing weblog.  It creates a new Quills blog as _new, because
COREBlog2 clearly does not like being renamed, and this migration will
leave you with the existing blog, as is, which BTW also worked fine in
Plone3 for me, and a new Quills blog which does not get whiny if you
rename it after deleting the original coreblog.

I still am interesting in pursuing QuillsEnabled as a migration
option.  I'm not sure I would, as Tim suggested, want to leave the
entire old COREBlog2 in place forever, because this is a double
dependency, sort of killing what I feel is the main advantage to
QuillsEnabled, that your content won't break as long as Plone itself
keeps working with ATCTs.  That said, it could be a great intermediary
step.

One of my reasons for wanting an ATCT-driven design for Quills was to
encourage other Zope / Plone weblog authors to consider a similar
approach, so that it would be easier to switch between weblog tools
and to have healthy competition.  It is a big responsibility, and has
been for a long time, for Quills to *be* blogging on Plone, and it may
stymie Quills' development that there isn't more great competition
around.  In that light, I'm thinking of copying some of Tim's work
from QuillsEnabled to do a COREBlog2Enabled.

I'm not really a huge fan of COREBlog2 so this will be a back burner
project, but it could really improve the story.  If several Ploneable
blogging modules go the 'enabled' route, and have their own maintained
migration from custom types to ATCTs, it will naturally be very easy
to switch between blogging tools, and even to experiment with more
than one or two over a period of time on one set of content, with no
pain.