What do on the team we need to know about our dev work?D: I really need best practices on executing on well-defined work. A: Seems to me what is not clear about changes is: Why? Who will benefit? Who will it hurt? D: I usually know these answers from the issue and acceptance criteria, I do not understand the immediate impacts of our changes and it is really procedural implications. W: "hard place that's a good place" and these are hard questions, but these are growing pains in the maturity of the project. D's feedback is also an important issue.W: We have to break out the kinds of work and what layer of the project it touches (Metaschema, document, research effort) What do we want the community to know about our dev work? D: We don't really "count" on issue comments, votes, etc. A: how would they understand what to comment on and/or vote on? D: 3-5% is really the maximal extent to what we can expect for participation in any community, so 3-4% is optimistic.