[Objectbridge-jdo-dev] let's go !

[Mahler T. <tho...@it...>]

Hi all,

I just had a look at the subcription list of the jdo-dev mailing list. I was
quite impressed: there are already 19 registered subscribers!

That should be enough to get started.

How to start?

First of all I want to invite you to comment on my proposal.

A. Strategy

1. I am proposing to start with a rapid prototype to get a feeling what
implementing JDO based on the PersistenceBroker kernel is all about. We can
try to reuse things from the ODMG implementation (e.g LockManagement or
state transition).

2. factor out all things that the JDO and the ODMG implementation have in
common and put it in a separate package ojb.otm.

3. refactor the JDO and the ODMG implementations to use the OTM internally.

I believe this implementation strategy will reduce risks and allow to get
first results quickly.
What do you think? 

If there are no objections we should fix this as our chosen strategy.

B. responsibilities.
I believe it's important to have fixed responsibilities. People should
commit themselves to be resonsible for certain tasks.
- Frido offered to work as our documentator
- I'm offering to work as code integrator and release manager 

Of course we also need people doing "the real" work i.e designing and
coding.
May be we need someone working as Quality Assurance manager, etc.

What would you like to do? What are you willing to commit yourself to?

Once we have agreed on responsibilities we can start with the real work!

C. Decisions
How to come to decisions? I'm not a friend of formalizing such things but
maybe we need a transparent way of handlig conflicting ideas and come to
comppromises all can agree on.
Maybe we need some kind of "steering comittee" for such cases? What do you
think?

-- Thomas