Re: Re: What I think we should focus on now

R. David Murray wrote:
> A real, *concrete* problem is what is needed to get this process
> kick started, not a discussion of what tools we *think* we might want.
> 
> (Keep in mind that I'm on the fringes of z3 development myself as
> I don't have as much time as I'd like to work on code for it.
> So my perception could be off base.  Hopefully other developers
> will correct me if I'm wrong.  And hopefully I'll start work on
> my own hybrid Zope2/Zope3 application sometime in the next
> month, and will get a lot more active.)

Same here.  It will help a lot to actually know what I am talking about 
;-)  Personally, I'm interested in starting by developing the catalog 
more, since I think that's what's standing in the way of any really 
useful apps.

The next step is a concrete migration problem.  We are way off 
implementing a backwards-compatibility layer, so porting or developing 
Zope2 products which are forwards-compatible definitely seems like the 
way forward.  SteveA has outlined some ideas about the probable process 
already.

Hmm, perhaps a new forum product?  That seems feasible.  Someone 
mentioned that they were making a blogging product recently, too.

> So *I* think this list is about developing techniques and (non-software)
> tools to *manage the migration process*.  Code tools are in scope
> for discussion, but not the primary focus, IMO.

I agree.  I imagine a primary tool in our box will be documentation 
accompanied with examples.  However, there may be some code involved 
which will make it easier to get started with cross-compatible products. 
  Actual implementation of that code should probably take place off this 
list, though..?  I guess we should just wait and see what happens.

seb