[Starlingx-discuss] Vulnerability Management guidelines - improving visibility

[Waines, Greg]

We do have a high level view of 'CVE Maintenance' in docs.starlingx.io .
https://docs.starlingx.io/security/kubernetes/cve-maintenance-723cd9dd54b3.html
We could provide a reference/link here to the more detailed page in the wiki .

Greg.

-----Original Message-----
From: Ildiko Vancsa <ildiko at openinfra.dev> 
Sent: Tuesday, July 11, 2023 4:51 PM
To: StarlingX ML <starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility

CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi StarlingX Community,

The StarlingX project has been gaining new users and contributors lately, and the community already started to look into providing more on-boarding related materials and help people to find their ways around.

Related to the above, I wanted to bring up the project’s Vulnerability Management guidelines. While there is some documentation available on the StarlingX wiki[1] currently, it is not the easiest to find. As this is a crucial area, I think it would be a good time to both make sure that the information there is up to date, as well as to make the documentation easier to find.

Would it make sense to move the content of the aforementioned wiki over to the Documentation website? Regardless of where the information lives, where do you think would be good to add pointers to it, ie. the project’s homepage, the docs homepage, etc?

Best Regards,
Ildikó

[1] https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management

———

Ildikó Váncsa
Director of Community
Open Infrastructure Foundation






_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io