oscerd opened a new issue, #131: URL: https://github.com/apache/camel-kit/issues/131
## Description Once the security model added by #6 (issue #5) is accepted, register it where downstream users and automated triage look for it: - add **Apache Camel Kit** under the Apache Camel entry in [`apache/security-site` `scripts/project-coordinates.json`](https://github.com/apache/security-site/blob/main/scripts/project-coordinates.json), with `security_model_link` `https://github.com/apache/camel-kit/blob/main/docs/security-model.md` and `security_model_source` `https://raw.githubusercontent.com/apache/camel-kit/main/docs/security-model.md`, so it appears on https://security.apache.org/projects/ like Camel K, Camel Quarkus, Camel Karaf, Camel Kamelets and Camel Kafka Connector; - list Camel Kit among the sub-projects with their own security model on https://camel.apache.org/security/ (the page currently names Camel Quarkus, Camel Spring Boot, Camel Karaf, Camel Kamelets, Camel Kafka Connector and Camel K). This tracks open question Q10 of `docs/security-model.md`. As noted in the review of #6, #5 should not be considered complete before this is done. ## Expected Behavior `security.apache.org/projects/` and `camel.apache.org/security/` point at the Camel-Kit security model, so a report against Camel-Kit is triaged against the right document. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
