On Mon, Mar 30, 2009 at 11:41, Rickard Öberg <[email protected]> wrote:
> I would suggest that the following are removed in their entirety:
> * The Chronos app. Niclas, do you ever see this being finished? If yes, then
> I suggest to move it outside of the Qi4j project. If no, then scrap it. Up
> to you.

+1 to move it out.

> * What is the status of the Struts2 binding? Production quality? If not,
> what's left?

I think somebody is using this. I'm not sure what other feature is required.


> * lib-general: lots of domain-specific stuff. Scrap it, and if we want a
> place to put some domain-specific code that can be "reused", then better put
> it in a sample app so that people can copy/paste/adapt it. Domain code is
> always going to depend on the local usecases!

+1

> * lib-quikit: Scrap?

Scrap, probably need to rethink what web framework should be used.

> * lib-spring: rename to ext-spring, as it is more of an extension than a
> library.
+1
> * ddd-sample: scrap and re-import the new 1.1 version as there's a LOT of
> rewriting in it
+1

> * tutorial-cargo: scrap or keep? if keep, then it needs to be updated
Keep and make the implementation to be 1-1 with the DDD book.

> In short, keep the intros and the composite+service tutorials, fix the
> Service tutorial to be complete and add one on Entities. Then we should have
> a decent baseline for documentation.

+1

> That's about it! I hope noone takes personal offense because of these
> suggestions. There's a LOT in the above that is my own code, I should point
> out. What I'm concerned with is focus and quality. Better have a lot of
> effort on something that is good, rather than a little effort here and there
> on stuff that won't work in the end.

How about DCI work that both you and Steen are doing?
Shouldn't that be part of qi4j codebase?

Regards,
Edward Yakop

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to