> I was enjoying a 1-week holiday in France.

I hope you had a great and relaxing week. Have two next time! =)

> Now that we're continuing to get more developers, we should look at
> the way that we're organized.
> We can divide ourselves into task-groups with the following responsiblities:
> * Documentation group: create and maintain user and developer documentation.
> * Database layer group: This group will focus on improving the
> database layer. Providing a solid interface
> * Delivery and retrieval group: This group will focus on improving 
> and maintaining the delivery and retrieval code (this is the stuff
> Paul is currently working on).
> 
> Division into these groups might make for a more stable database
> layer. Better focus on where to find speed etc. What do you guys
> think? I think this might decentralize core decisions somewhat more.
> I'm not implying that people should only work on one part of the code
> of course, but more that the responsibility for some code might be
> shifted towards groups of people.

Great idea.

I would like to be a part of the database layer group if you want
me there. I'd like to get both feet in on the database action and
then get the damn thing documented.

-=Dead2=-

Reply via email to