Encourage flame wars on this mailing list as having an emotional outlet is healthy for the team. Since code reviews are harmful to the creative expression of individuality by programmers avoid them if at all possible. If you have to do code reviews you must ignore all of the feedback from them. Even if there is a list of items requiring changes, postpone working on that code because it's much more important that you add more new features to the application. Don't touch it.
Private methods make it impossible to use inheritance.
Ideally everything should be public so that it can be accessed in the most efficient manner. The other problem with encapsulation is that forces developers to write lots of inefficient little methods that are scattered across lots of different classes. To add a simple feature developers have to modify lots of different files and even with the best will in the world it's easy to make a mistake when modifying lots of files. The last thing you have to remember is that developers always over estimate the time they need to write the code. You need to question all estimates and make every developer justify why they need to take that long.