[sldev] Philip's viewer; was: Tuesday Hippotropolis Meeting w/voice

[Mike Monkowski]

Very good meeting, but I still have questions about the process.

One thing that was brought up was that code review is a good thing.  So 
make the code review the gatekeeper.  Nothing gets into Philip's branch 
unless it goes through a code review, which could be a regularly 
scheduled meeting on Hippotropolis (or elsewhere) or it could be called 
by Philip whenever he feels like it.  Anyone could comment on the code, 
but Philip would be the ultimate "go" or "no go" authority.

Is documentation (on the wiki?) required for a "go"?

Before I spend my time coding, I might want to know whether it has a 
chance of making it into Philip's viewer.  Do we need a design review as 
well?

That gets stuff in, but how does it get back out to trunk?  How often? 
Who does it?

And how do other changes to trunk (or RC?) get into Philip's branch? 
Who keeps the two in sync?  What happens when LL code changes break the 
new features?  What about when my feature breaks your feature?  Who is 
responsible for fixing them?  If I fix something that came from trunk or 
RC, how does it get fixed back there?

If someone abandons his code, how does it get removed?

I'll probably think of more questions, but this will do for now.

Mike
Mm Alder