Change label from "Fixed by vulnerabilties" to "Fixes vulnerabilities"

[TG1999]

[johnmhoran]

@TG1999 There's no description -- please explain the thinking behind the change you suggest. We've changed the names of these columns several times already in the past -- happy to change again if that what the group wants, but I haven't heard from others that that's what they want.

[johnmhoran]

Not sure if this is helpful, but one way to describe the relationship we're trying to name -- from the PURL's viewpoint, the PURL is "affected by" a vuln or "fixes" a vuln; and from the vuln perspective, the vuln "affects" the PURL or is "fixed by" the PURL. 🤔

[mjherzog]

I think that the current parallel "by" construction makes the most sense.

[DennisClark]

I think that "Fixes vulnerabilities" would be the best solution.

[johnmhoran]

@mjherzog @pombredanne When you have the chance, please share your views on the latest suggestion -- "Fixes vulnerabilities".

[mjherzog]

The terminology is very context dependent as explained by @johnmhoran . So if we are talking about just the Results page context, then changing "Fixed by vulnerabilites" to "Fixes vulnerabilities" make sense. On the Essentials page that changes to:

• Vulnerabilities affecting this package
• Vulnerabilities fixed by this package which makes sense in this context

[pombredanne]

What I see most commonly is "fixed vulnerabilities" from a package point of view, not "fixes vulnerabilities". Juts removing the "by" should be enough

[johnmhoran]

Thanks @pombredanne. I'll make the change you suggest: "Fixed by vulnerabilties" ==> "Fixed vulnerabilities".

[pombredanne]

Closed and merged in the issue https://github.com/nexB/vulnerablecode/issues/1520 that tracks changes in the models, API and UI at once