Prepare invited reviewer feedback

[sdruskat]

Decide governance/decision processes for definition draft and feedback, i.e., how feedback will be

• filtered,
• used, and
• credited.

Also,

• identify what feedback we want to get from the invited reviewers, and
• how we will collect this, along with
• communication materials around this.

Finally,

• Gather taxonomies here as well

Types of feedback

Potential types of feedback are:

• Comments on the document draft itself. These have worked well in the past to improve the document.
• A survey to understand how people would want to use the definition. This could be useful for clarifying the format and documentation of the definition.

A survey may be more representative in the community feedback round (#50), but it may be worth thinking about doing a small survey to avoid major changes later.

[sdruskat]

Questions to reviewers

• The criteria exclude accountability (crit. 4). Do we need a place/a subsection "Beyond authorship", where we say that while authorship excludes this responsibility, there should be other places in a project where it lies, e.g., the project governance and the license? E.g., Apache 2.0 includes exclusion of Warranty, etc.