Talk:Plone (software)

Regarding CVE
What is the thought here for this section ? As far as I am concerned the CVE is a valid industry comparison of security breaches known to users. You cannot track the unknown. What you can track is the known. CVE table identifies this and relates fact. Fact is that some CMS's (and all software in general) either add ons or core have inherent higher risk associated to past historical coding issues and their architectural footprint in general. It would be misleading to not give this comparison, and dismiss the issue al together. 2001:470:1F11:16E:0:0:0:1BD (talk) 23:10, 28 May 2013 (UTC)
 * For discussion of the CVE table please do that on the Drupal talk page. 217.211.59.24 (talk) 23:18, 28 May 2013 (UTC)


 * Please refrain from directing conversation outside the context at hand. 2001:470:1F11:16E:0:0:0:1BD (talk) 23:40, 28 May 2013 (UTC)


 * This is not at all outside of the context. Drupal is one of the included subjects in the table and I try to keep all the discussion at one place. Also information about Drupal and Wordpress is disputed. See the Drupal talk page for more. 217.211.59.24 (talk) 23:44, 28 May 2013 (UTC)


 * I would prefer to replace the CVE table with references to studies done on the security of various CMS systems, such as the German Government study. I don't think providing raw numbers from the NVDA is useful or appropriate MatthewWilkes (talk) 04:16, 2 January 2015 (UTC)


 * The CVE table highlighted with blue looks more and more like an advertisement, I fixed the table a few years ago when it compared "CVE's to date" and plome had 0 ? someone keeps changing this article from insdie the company. Also the CMS should be compared against similar technology made CMS's such as Mezzanine which is a django CMS done with python. 176.72.248.21 (talk) 13:57, 2 February 2016 (UTC)