coreinfrastructure/best-practices-badge

documentation_security: N/A should be an option

ljharb opened this issue · 4 comments

ljharb commented

This metric says:

The project MUST document what the user can and cannot expect in terms of security from the software produced by the project

Many projects produce no software at all, so for these projects, it should be N/A - but that's not an option.

Hmm... you're right!! Okay, we'll have to fix that. Thanks for letting us know.

ljharb commented

I will add that I found the words "project produce software" very confusing - to me, the project IS software, and it only PRODUCES software if it's generating code. However, I've started to suspect that the way this is intended is that the project is conceptual, and the software it "produces" is whatever's released?

The intent was to be clear. The "software produced by the project" is whatever software the project produces. The ideas is that a software being produced is a thing; the project is the group of people, processes, etc., that produce the software. Does that help?

ljharb commented

Yes, I think that clarifies the intent - I'd misunderstood it because to me, the project is the software, not the people.