[Development] Proposal: Change Qt's Security Policy to Full Disclosure

Knoll Lars Lars.Knoll at digia.com
Thu Oct 25 08:59:13 CEST 2012

Let's close this topic. It's not always the one who shouts loudest that wins an argument.

We have a closed security mailing list, and I want to keep it that way. That seems to also be in agreement with the majority of the maintainers who have been dealing with this topic.

The members of the security list will work hard to keep response time and time to full disclosure at a minimum.

We have an open development mailing list for everything else, as many people have pointed out.


On Oct 25, 2012, at 1:22 AM, d3fault <d3faultdotxbe at gmail.com>

> Made a chart so people who don't want to read this whole thread don't have to.
> Impenetrable logic.
> http://bayfiles.com/file/p3vn/E41lwK/Full.vs.Responsible.Disclosure.Chart.png
> d3fault
> <Full.vs.Responsible.Disclosure.Chart.png>_______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

More information about the Development mailing list