You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by GitBox <gi...@apache.org> on 2020/09/02 06:10:58 UTC
[GitHub] [lucene-site] dsmiley opened a new pull request #29: Cve 2020 13941
dsmiley opened a new pull request #29:
URL: https://github.com/apache/lucene-site/pull/29
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] janhoy commented on pull request #29: Cve 2020 13941
Posted by GitBox <gi...@apache.org>.
janhoy commented on pull request #29:
URL: https://github.com/apache/lucene-site/pull/29#issuecomment-690927237
The CVE template here I think is a copy of a kind of a layout some projects use for ANNOUNCE mails for CVEs, such as https://lists.apache.org/thread.html/rd48c72bd3255bda87564d4da3791517c074d94f8a701f93b85752651%40%3Cannounce.apache.org%3E, but I see that the style of those emails vary a lot. However, for the web site news it makes sense to keep the same structure since they are all listed in the same place.
The new CMS also has a possibility to define more "variables" on top of the template, so we could in theory define all CVE headings as structured metadata that could then be used in other templates such as the table on top of security page. But I think what we have now is a good balance?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] janhoy commented on pull request #29: Cve 2020 13941
Posted by GitBox <gi...@apache.org>.
janhoy commented on pull request #29:
URL: https://github.com/apache/lucene-site/pull/29#issuecomment-690927237
The CVE template here I think is a copy of a kind of a layout some projects use for ANNOUNCE mails for CVEs, such as https://lists.apache.org/thread.html/rd48c72bd3255bda87564d4da3791517c074d94f8a701f93b85752651%40%3Cannounce.apache.org%3E, but I see that the style of those emails vary a lot. However, for the web site news it makes sense to keep the same structure since they are all listed in the same place.
The new CMS also has a possibility to define more "variables" on top of the template, so we could in theory define all CVE headings as structured metadata that could then be used in other templates such as the table on top of security page. But I think what we have now is a good balance?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] dsmiley commented on pull request #29: Cve 2020 13941
Posted by GitBox <gi...@apache.org>.
dsmiley commented on pull request #29:
URL: https://github.com/apache/lucene-site/pull/29#issuecomment-686556863
Updated. I didn't add "Vendor" which seems pointless. Where did this template/convention come from?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] janhoy commented on pull request #29: Cve 2020 13941
Posted by GitBox <gi...@apache.org>.
janhoy commented on pull request #29:
URL: https://github.com/apache/lucene-site/pull/29#issuecomment-690927237
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] dsmiley merged pull request #29: Cve 2020 13941
Posted by GitBox <gi...@apache.org>.
dsmiley merged pull request #29:
URL: https://github.com/apache/lucene-site/pull/29
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] dsmiley merged pull request #29: Cve 2020 13941
Posted by GitBox <gi...@apache.org>.
dsmiley merged pull request #29:
URL: https://github.com/apache/lucene-site/pull/29
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] dsmiley merged pull request #29: Cve 2020 13941
Posted by GitBox <gi...@apache.org>.
dsmiley merged pull request #29:
URL: https://github.com/apache/lucene-site/pull/29
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] janhoy commented on pull request #29: Cve 2020 13941
Posted by GitBox <gi...@apache.org>.
janhoy commented on pull request #29:
URL: https://github.com/apache/lucene-site/pull/29#issuecomment-690927237
The CVE template here I think is a copy of a kind of a layout some projects use for ANNOUNCE mails for CVEs, such as https://lists.apache.org/thread.html/rd48c72bd3255bda87564d4da3791517c074d94f8a701f93b85752651%40%3Cannounce.apache.org%3E, but I see that the style of those emails vary a lot. However, for the web site news it makes sense to keep the same structure since they are all listed in the same place.
The new CMS also has a possibility to define more "variables" on top of the template, so we could in theory define all CVE headings as structured metadata that could then be used in other templates such as the table on top of security page. But I think what we have now is a good balance?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org