in-toto doc assessment - Githubissues

jbogarthyde commented 1 year ago

resolves: #163

nate-double-u commented 1 year ago

@thisisobate, could you help @jbogarthyde with the website/technology part of this assessment like you're helping David with the other one?

thisisobate commented 1 year ago

Updated the website section as promised. cc: @jbogarthyde

nate-double-u commented 1 year ago

Some general feedback that came up in the last in-toto community meeting. Some of this may be applicable to more than just this assessment.

Actionable feedback is key
Provide guidelines, exemplars from other projects (We do this, or have a section for it, but may want to surface these kinds of suggestions better)
- Here are some things that you don’t have, but which CNCF projects should consider
- An idea came up to provide an executive summary style introduction that lists the top actionable suggestions
- “easy lifts”
- Checklists not as valuable as examples
The community may take better to sectioned, actionable, feedback, rather than a grade on specific sections out of 5
- When ready, it may be best to parcel out the feedback to specific sections, one at a time

@psgustafson @dwelsch-esi - pinging you as you attended and I don’t want to have missed any important bits of feedback about the process.

jbogarthyde commented 1 year ago

Replacing with new iteration

cncf / techdocs