As part of our goal to improve how we operate. I think this is a good time for us to review ourselves. I'd like for us to look over our code - services, scripts, UI, etc. Now is a good opportunity to make sure we're doing things the right way. The outline of the review is not set, and I'd like your input on what it should cover. Basically, we're looking for what we need to fix/refactor and lessons for how we ought to do things going forward. I have three broad topic areas for the review in this google doc: https://docs.google.com/a/lbl.gov/document/d/1ebc6jWxnudsOtZWo3RNoWDhFFDFG33... Feel free to add/change and comment on it over email and in the doc. Let's try and have this done today. And start the review on Tuesday. Operationally, the review will be each developer describing their code to another person in the context of the review areas. And then each developer will write up a couple sentences on dependencies and things that need to be refactored. And everyone will work out a list of topics for what we can improve on. Hopefully, this will be a fast process and we can report back on our next Monday call 3/18. Paramvir