Re: MidCOM and its further adaption to new Midgard versions - AKA Midgard core quality

Hi,

On 2/9/06, Piotras <[email protected]> wrote:
> I will ask a question for every question because I can not be the only
> one who is responsible for midgard logic.

That's reasonable and not really the problem. The problem is that
nobody is currently taking responsibility for the bigger architectural
issues. I tried doing some of that last year but right now I just feel
too frustrated to keep trying. The current development attitude of
"program first, define API later" isn't too supportive for long term
planning.

> Plan for 1.8 is very simple.
>         * improved, faster and partially refactored core with QB
>         * metadata for any midgard type
>                 Maybe I am the only one who heard that
>                 midcom's metadata is its killer?
>         * Midgard Reflection
>         * New Quota
>         * New datatypes like ISO datetimes

And things like a new configuration mechanism, etc. Compare this list
with the one in the 1.8alpha1 release notes and you get my point about
not having a clearly defined release plan.

> What we do now is not about "taking care of the managerial and
> architectural issues in Midgard", it is about doing all the stuff which
> is absolutely mandatory to be done.

I think this pretty much summarizes the problem at hand. Different
definitions for "absolutely mandatory" (paraphrasing heavily :-):

Piotras: bug fixes, optimizations, new features
Jukka:   taking care of the managerial and architectural issues
Torben:  proper documentation and a better development process

> If I would like to make parser improvements right now , how should I do
> it after style mRFC has been passed? How caching features similiar to
> MMP should look like after this mRFC has been passed? Should I move it
> to midgard-php or midgard-apache? How should looks like request
> handling?
>
> I asked these questions because no one focused on such "details" while
> we voted for full rewrite of code in three midgard modules.

I answered all these questions when mRFC 0022 was discussed. The fact
that I need to repeat myself over and over again is one reasons I feel
so frustrated about taking any sort of responsibility over the
architectural design. This problem is not related to just this issue
but was repeated many times during the discussions last year.

BR,

Jukka Zitting

--
Yukatan - http://yukatan.fi/ - [email protected]
Software craftmanship, JCR consulting, and Java development