Re: [PATCH] doc: Add technical overview

[Baurzhan Ismagulov <ibr@radix50.net>]

On Tue, Aug 08, 2017 at 01:11:02PM +0200, Henning Schild wrote:
> I did not really read this yet. At the moment i think we have too many
> changes in the q to add such a document to the repository. Any change
> would just mean heaving to keep it up to date.
> We talked about the need for such a document for the possible OE
> integration. I think it is valuable for that already.
> 
> That should be added after we all are happy with the feature-set of
> Isar, until then it would just be another file to update when changing
> how things work.

This is exactly one of the goals of documenting this at this stage. It is
important to document architecture changes, in small steps along the way.
Otherwise, later it will be difficult to understand the big picture and the
motivation for the changes from the many patches. I think that changing a
couple of paragraphs in the 110 lines of a really high-level overview shouldn't
be that difficult to do and is well worth it.

On a related note, my problem with some of the patches at this list is that I
see what the code does, but don't see the context and motivation. So, if a
patch requires a change in the document, providing it will only speed up the
review process.

With kind regards,
Baurzhan.