[os-engineering] FW: [os-infrastructure] Re: Model discussionboiled dry(er)

[Chris Clark]

On 6/26/2008 9:04 AM, Alex Hanshaw wrote:
>  ....Ray has put together a diagram of
> model a) as a discussion point. I'm sure this list will see the detail
> once some initial refinement has been made. OpenROAD are aware.
>   

This is now ready for prime time at 
http://community.ingres.com/wiki/Community_Model I would like to suggest 
a rule/guideline for this page, you only post what you know is the 
proposal. Discussion should talk place in this list, phone, IM, two tin 
cans and string. Avoiding cruft on the wiki page is going to be useful.

Currently we have "Proposal 1" -- which I *think* is the fresh/stale 
(a/b) options that Andrew put out as initial ideas. This does not 
discuss timing of syncs (or even what/how this is done) so maybe we need 
1.a, 1.b.

We need a buffer example, and I we need the OpenROAD proposal up too 
(which is different code lines than ingres!main).

RE Proposal 1 - we need to start to iron the procedure, I'm not talking 
about avn hooks, piccolo hooks, etc. I'm thinking, what is sync'd this 
isn't not (cannot) be a straight sync of the tree. For instance the 
gateway dir (ingres!main!generic!gateway) is in there and this is closed 
source, I think we have some (provate) signed keys in another dir in 
main etc. Luckily these are in specific directories so I think we are 
talking about limiting the syncs to only dirs - but we need consensus on 
this and we need to document it! :-)

I think Proposal 1 has an implicit, "no closed source" restriction in 
the dirs that are synchronized - is this the vision for this proposal? 
Is this wrong! Lets flesh out the proposals (and get example use cases).

A big thanks to Ray for creating the image, it is IMHO much better than 
an ASCII diagram and very clear.

Chris