[Fwd: Re: [Poop-group] [announce] The Object Persistathon! (2nd try)]

[Terrence B. <te...@hc...>]

-------- Original Message --------
Subject: Re: [Poop-group] [announce] The Object Persistathon! (2nd try)
Date: Mon, 29 Nov 2004 21:45:24 -0800 (PST)
From: Darren Duncan <darren@DarrenDuncan.net>
To: Sam Vilain <sa...@vi...>, Dave Rolsky <au...@ur...>,        Terrence 
Brannon <te...@hc...>, Gerald Richter <ri...@ec...>,        Ovid 
<pub...@ya...>,        Kurt Starsinic <kst...@gm...>, 
Tim Bunce <Tim...@po...>,        david nicol <dav...@pa...>, 
       Matthew Simon Cavalletto <si...@ca...>
CC: darren@DarrenDuncan.net

Apparently, sourceforge.net implemented a change where emails from a
domain lacking a postmaster address wouldn't work.  I never needed one
before, but I just set it up and will try again.  ...  That didn't seem to
work, or there is a delay before it will work.

Meanwhile, will one of you, the first one to not see one of the others do
it, please forward any messages of mine to
poo...@li...?  Thank you.

---------- Forwarded message ----------
Date: Mon, 29 Nov 2004 21:23:39 -0800 (PST)
From: Darren Duncan <darren@DarrenDuncan.net>
To: Sam Vilain <sa...@vi...>
Cc: poo...@li..., cdb...@gr...,
      tan...@ho...,
      Alz...@li...,
      ope...@li...
Subject: Re: [Poop-group] [announce] The Object Persistathon!

On Tue, 30 Nov 2004, Sam Vilain wrote:
> Simon Cozens is including a chapter on POOP in _Advanced Programming
> Perl, 2nd edition_, an O'Reilly book.
> As he is busy with a new direction in his life, I have agreed to
> co-ordinate gathering material and code for possible inclusion in the
> chapter from authors and users of POOP frameworks.
> The challenge is:
> Implement classes to drive this schema (minimally remodelling as you
> feel appropriate):
<snip>
> And produce a test script to do the following things:
<snip>
> And a couple of maintenance scripts:
<snip>

I will reply to this using 2-3 multiple separate messages that are more
targeted.  All of *those* will go to poo...@li....

First of all, I would *definitely* be interested in implementing the
things you mention using my bleeding-edge Rosetta/SQL::Routine framework.
This sort of thing is just the kind of exposure they need, and will
provide a good documentation opportunity to demonstrate how to do certain
common tasks, both on an objective and a comparative basis.

Unfortunately, I have started having new bad sectors appearing on my hard
disk, and will be having it replaced tomorrow under warranty.  This will
take a few days, during which I probably won't have computer access
necessary to do the work.  I will also need a minimum of a week after
those few days to get my implementation ready.  Having 2-4 weeks is
preferred.  But suffice to say that working on these modules is more or
less my full time job at the moment, so I'm putting in long hours.

So, when do you / does Simon need these implementations by, either full or
partial?  Eg, when are early drafts and final drafts needed?  Is the book
on a rigorous publishing schedule?

Also, do the implementations need to be able to work as is for a
long period of time, or is it okay that details may require small changes
later due to module API changes?  While I'm mostly nailed down, there are
still a few pending API changes to my modules.  They *are* pre-alpha.

I'll send separate replies about task list details and suggested
task additions; they will all go to poo...@li....

Also, if anyone is interested in my modules, I accept offers of
assistance.  (Aside from replies to some RFC emails over the last 2 years,
I've been doing them entirely on my own.)  I also have no list specific to
developing or using my modules yet, but may start one later when they
start to get a user base or multiple interested developers.

Thank you. -- Darren Duncan






-- 
Terrence Brannon, te...@hc...