(a) +1 for sure. STREAMS-348: Create coding guidelines document for website STREAMS-349: Maven plugin that can validate all classes have a sensible javadoc header STREAMS-350: Bring codebase into compliance with requirement for sensible javadoc headers.
(b) +1 I think. I agree with minimizing, but think where we draw the boundary and how broadly we purge it may warrant more discussion. Let’s start by getting it out of: streams-util streams-config streams-core streams-pojo streams-pojo-extensions streams-schemas/* streams-verbs STREAMS-441: Remove compile dependency on guava for core packages If it can be stripped out of streams-components/* and streams-contrib/* that’s good but I don’t see as much of a problem with some of those modules using it as needed where it’s truly useful. Steve On October 24, 2016 at 11:41:53 AM, Suneel Marthi (smar...@apache.org) wrote: I had 2 things in mind that we need to work in tandem with adding/improving functionality in Streams. (a) Remove author info from all code that has it, and add sensible JavaDocs for each class (b) Now that we are officially Java 8, minimize Guava API use and migrate most Guava stuff to Java 8 where possible. Suneel
