Pruning the oldest issues - July 2022

Attendees

• Jan Ainali
• Eric Herman
• Elena Findley-de Regt (last part of the call)

Notes

We started by reviewing the notes from the last session.

Then we continued with:

• Not all MUST criteria have a clear test in the “How to test” section #314 - work session scheduled for 19 July
• define your product design principles #315 - related to the Implementation guide and should probably be folded into that one instead of the standard (which has it’s next working session on 18 July)
• Providing a definition what transparent, accountable, understandable means in the context of public software #317 - comment made, review again in the next session
• Provide a definition of the core values in the context of public code #318 - comment made, review again in the next session
• Make the “Code in the open” MUST (unless used) more general applicable #324 - work session scheduled for 19 July
• Add anchors to each requirement to make deep links possible #327 - comment made, stays open
• Code of conduct could cater to public organizations better #330 - will be fixed by Replace Code of conduct #643
• Code of conduct is licenced CC-BY #331 - will be fixed by Replace Code of conduct #643
• Possible redundancy and/or conflating requirements #332 - work session scheduled for 26 July