Hey folks, Long time lurker, first time emailer. In my free time, I've done several cursory, albeit brief, explorations with Yetus to help out our reviewing efforts and reduce time to merge, but got a bit lost figuring out where to dig in. I will frame the this note by saying that I am not deep into the Hadoop ecosystem as a whole, so some level of knowledge or experiences that others may have could be absent.
I had the opportunity to attend Allen's Yetus talk today at ApacheCon Big Data (great job! would be great to see some of these items make their way onto the site when available) which most certainly helped illuminate a couple of points for me. Coming to the project with some guiding insights from a few folks I talked to, my impression was a kind of "ecosystem of components." To further clarify, it seemed like each component was kind of dependent on the others and there was a full package of functionality. Allen's sweet architecture diagram kind of put things into perspective for me and cleared up that there are a few different personas and the various components cater to different audiences. * Precommit for those handling patch review * Release Doc maker for the RM * Shelldoc for those people/projects doing scripting in their project efforts to generate Javadoc like functionality * Audience Annotations for those designing APIs and extension points. In full disclosure, this is all quite obvious to me in light of the talk but things did not quite mesh viewing the docs in isolation or without sufficient attention. A quick start or similar that lets folks self select for certain roles could be quite nice, something akin to: * "I'm a code reviewer and would like to avoid the motions of commit monotony.", * "I'm an RM and my project needs great release notes.", * "I'm a developer and want my program to be extensible but have certain caveats about some areas.", and so on. Again, nice work on the presentation today and on the efforts of the project.
