[Development] QtCS2019 Notes from "Evolving the Qt Security Policy" session

Notes from the session are in https://wiki.qt.io/Qt_Contributor_Summit_2019_-_Security_Policy See QUIP for proposal - https://codereview.qt-project.org/c/meta/quips/+/ 278819 * Make the security core team a very small ** Must be Qt Project Approver * Subscribed people to the security list is

[Development] QTCS2019 Notes from QtQml session

Hi, these are the notes on the QtQml session: Grouped properties -- Grouped properties are incredibly buggy and basically unusable for anything but font and anchors right now. The language would be better off without the concept, allowing only the replacement of the full

[Development] QtCS2019 notes from "Improving the Contributor Experience" session

Hi, Here and below are the notes from this session: https://wiki.qt.io/Qt_Contributors_Summit_2019_-_Contributor_Experience Cheers, Volker === Framing the discussion === * See JIRA task: https://bugreports.qt.io/browse/QTBUG-74429 * Getting started as a new contributor requires a list

[Development] QtCS2019 Notes from "API Review Process" session

Hi, Here and below are the notes from this session: https://wiki.qt.io/Qt_Contributors_Summit_2019_-_API_Review_Process Cheers, Volker Current processes as part of final release preparations: * https://wiki.qt.io/API_change_review * http://quips-qt-io.herokuapp.com/quip-0010-API-review.html

[Development] QtCS2019 Notes from "Branch Policy" discussion

Hi, Here and below are the notes from this session: https://wiki.qt.io/Qt_Contributors_Summit_2019_-_Branch_Policy Cheers, Volker == Discussed and Agreed Proposal == * We move to a workflow where we make all changes in dev, and then cherry-pick relevant changes from dev down into stabler

[Development] QtCS2019 Notes from "Fuzzing Qt" BoF session

Hi, Here and below are the notes from this session: https://wiki.qt.io/Qt_Contributors_Summit_2019_-Fuzzing_Qt Cheers, Robert == Introduction == * Explained briefly what fuzzing is in general * Showed how to fuzz Qt itselfSee readme file:

Re: [Development] QtCS2019 Notes from "Fuzzing Qt" BoF session

On Thu, Nov 21, 2019 at 12:13:55PM +, Robert Loehning wrote: === Which code needs fuzz testing the most? === Agreed criteria: Code that operates on possibly untrusted data Proposals from the audience: * Classes ** [https://doc.qt.io/qt-5/qcommandlineparser.html QCommandLineParser] **

Re: [Development] QtCS2019 Notes from "Branch Policy" discussion

On Thu, Nov 21, 2019 at 08:50:10AM +, Volker Hilsheimer wrote: == Discussed and Agreed Proposal == We start with Qt 5.15/14/12 (ie 5.15 is “dev” in the Qt 5 series), and continue to merge 5.15 into dev until 5.15 has reached feature freeze. this has NOT been agreed upon. what actually

[Development] QtCS2019 Notes: Qt for Python and beyond

Hi, Following the notes from the Qt for Python session - Continuation of the plenary session - Right now status is same as PyQt - What can we do to make a difference and improve on QtfP - Tooling ○ Around pyside and… ○ Make it

[Development] QtCS2019 Notes: Qt CMake Workshop

can be found here https://wiki.qt.io/CMake_Port/Workshop_2019_11 ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] QtCS2019 Notes: Qt for Python and beyond

Hello, As a follow-up, you can find the notes from the Qt for Python Documentation notes here: https://wiki.qt.io/Qt_Contributors_Summit_2019_Program/Qt_for_Python_Documentation Cheers On 11/21/19 3:06 PM, Maurice Kalinowski wrote: > Hi, > > Following the notes from the Qt for Python session

Re: [Development] QtCS2019 Notes: Clang-based cpp parser for lupdate

On Thu, Nov 21, 2019 at 04:38:28PM +, Joerg Bornemann wrote: There is the ongoing effort to replace the old outdated parser with a clang, similar to what's been done in qdoc. The corresponding JIRA issue is QTBUG-71835. a more radical and much simpler approach would be switching to gettext

[Development] QtCS2019 Notes: QtCore

Written here: https://wiki.qt.io/Qt_Contributor_Summit_2019_-_QtCore Thanks, -- Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - The Qt, C++ and OpenGL Experts

Re: [Development] QtCS2019 Notes: Clang-based cpp parser for lupdate

On Thu, Nov 21, 2019 at 07:48:41PM +0100, Oswald Buddenhagen wrote: > On Thu, Nov 21, 2019 at 04:38:28PM +, Joerg Bornemann wrote: > > There is the ongoing effort to replace the old outdated parser with a > > clang, similar to what's been done in qdoc. The corresponding JIRA > > issue is

Re: [Development] QtCS2019 Notes: Clang-based cpp parser for lupdate

Am 21.11.19 um 20:23 schrieb André Pönitz: On Thu, Nov 21, 2019 at 07:48:41PM +0100, Oswald Buddenhagen wrote: a more radical and much simpler approach would be switching to gettext The most prominent difference is the (usually) per-class automatic context which I always found too clever to be

Re: [Development] QTCS2019 Notes from QtQml session

Hi Ulf, thanks for clarifying. You're absolutely right, no other language supports importing different versions of dependencies but I think it is a great feature of QML that helps a lot in maintaining the old code. Would be sad to see it gone in QML 3. Cheers PS I'm forwarding this email to the