The technology.pmc's list has basically checking that
https://www.eclipse.org/legal/guidetolegaldoc2.php has been followed,
plus Try to reduce bloat. There are a lot of checkboxes on there and a
number of them haven't been met. But I assume that IP people have
tools that check this automatically.
For example, there is no about.html in every bundle and the
package-info.java files don't have copyright header.
I don't really want to do the check manually if there is automation later.
Additionally, "Author(s): Self", I assume that other people at
DLS were involved in coding this :-)
side-bar I am not fond of this:
* There is no strict format for code, such as you must indent using a
tab rather than four spaces or your imports should be in a specific
order. Or a line limit other than the one Java suggests. If a reviewer
asks for this you should refer to this guideline!
but if you have that, I am glad you have:
* Avoid reformatting code just for 'readability' because it creates
false diffs. Better to tolerate the original developer's formatting.
Having worked on the 15 year old CDT project for a long time, it is an
absolute nuisance that random files are formatted in randomly
different ways. I am very fond of the growing number of projects that
enforce (via automation) strict code formatting rules. For example
py4j and PyDev are now in this situation and the code is easier to
work on because you can rely on the tools to help (like formatting).
