So the topic of code review has been around the cloister before. Thanks for pointing that out little, from what I read there was noone saying: "No that's a bad idea..". So what happened last time to make this erm not happen?

--

I'd second this full-heartedly.

Which begs the question "How do we get it going in practice?"

• Hijack the code snippets section -- not very nice for the 'ego-full juniors' who want to understandably show their worth.
• Wait for the Everything folks to have time to implement a new section?
• Hijack the obfuscated code section ;-)
A short term solution might be the code snippets after all, but with the snippet title containing an appropriate 'For Review' tag. Would it work?

" So what happened last time to make this erm not happen?"
dunno

but I guess it was forgotten. Actually I think Tim Vroom is very busy with is exams and stuff, so he's got no time. As I understand the everything engine, it'S very simple to add a new section, but harder to mainatin it. So actually I think we should simply have the next polling asking for:

"What about a code review section?"
• We need that
• might be nice
• don't bother
• blah ...

Or Tim might think about letting have some of the Saints in our Book acces to site but not mainly the engine to work and to develope the Site, because the most content and structure of the site resides in XML files and structure definitions outside the code.

Have a nice day
All decision is left to your taste