On 29 Jun 2019, at 06:48, Craig Russell <[email protected]> wrote:
[ snip useful summary ] > Given the D&I objectives for this program, I'd say that code is a byproduct > and not the deliverable. While that is true (re-defining `code’ here as anything/work that is part of that what the communities are about - be it it code, scripts, build improvements, sites, beter CVE finding, bug-triage, doc-templates, dependency simplification) — I’d love to somehow keep `code’ in the primary path of what is on offer. As it is (pride in) that which, in my opinion, drives the feedbackloop that improves and keeps our communities long term stable. The mere hint of introducing a class of `byproduct code’ may lessen the K in that feedback loop below 1. And keep the `byproduct’ your aforementioned: > During program reviews, communities get feedback on how to reduce barriers to > entry and how to increase/encourage participation. Dw.
