Qt Contributors Summit 2019 Program: Difference between revisions
(Linking to a proposal for an evolved security policy on code review) |
|||
| Line 196: | Line 196: | ||
''Volker Hilsheimer'' | ''Volker Hilsheimer'' | ||
During summer, the Qt Project Security Policy was moved from a wiki page into [/quips-qt-io.herokuapp.com/quip-0015-Security-Policy.html QUIP-15], and during that review process, some changes and additions were proposed to strengthen the project's capability to respond to security issues. Those changes were not taken into the QUIP as part of the move, since for the moment we only wanted to move the content. Suggestions included a clearer statement how security fixes are applied to LTS releases; the integration of CVE handling when disclosing vulnerabilities; the documentation of processes established by the Qt Company; and a general review of the way the "core team of developers" is organized, and operating. | During summer, the Qt Project Security Policy was moved from a wiki page into [https://quips-qt-io.herokuapp.com/quip-0015-Security-Policy.html QUIP-15], and during that review process, some changes and additions were proposed to strengthen the project's capability to respond to security issues. Those changes were not taken into the QUIP as part of the move, since for the moment we only wanted to move the content. Suggestions included a clearer statement how security fixes are applied to LTS releases; the integration of CVE handling when disclosing vulnerabilities; the documentation of processes established by the Qt Company; and a general review of the way the "core team of developers" is organized, and operating. | ||
Discussing these (and additional) proposals, and agreeing on what should become part of the policy (and thus the responsibility of the Qt project) is the purpose of this session. | Discussing these (and additional) proposals, and agreeing on what should become part of the policy (and thus the responsibility of the Qt project) is the purpose of this session. A proposal is available here: https://codereview.qt-project.org/c/meta/quips/+/278819 | ||
=== Qt for Python and beyond === | === Qt for Python and beyond === | ||
Revision as of 15:10, 23 October 2019
Back to Qt Contributors Summit 2019
Table of topics
Please add a longer session description with topic owner in the lower part of the page!
Tuesday, 2019-11-19
First day is reserved for topics that are of interest to the majority, and main location is the Assembly Hall. If you have something to present please coordinate beforehand on IRC or via mail.
| Time | Assembly Hall |
|---|---|
| 8:00 - 9:00 | Registration |
| 9:00 - 9:20 | Introduction and sponsors |
| 9:20 - 10:30 | Keynote: Towards Qt 6 (Lars Knoll) |
| 10:30 - 11:00 | Coffee Break |
| 11:00 - 11:30 | QML version 3 |
| 11:30 - 12:00 | CMake Port |
| 12:00 - 13:30 | Lunch Break |
| 13:30 - 14:00 | Branch policy for Qt 6 |
| 14:00 - 14:30 | Qt Marketplace |
| 14:30 - 15:00 | KDE experience in attracting and nurturing contributors |
| 15:00 - 15:30 | Coffee Break |
| 15:30 - 16:00 | Qt 6 Graphics Overview |
| 16:00 - 16:30 | Qt for Python |
| 16:30 - 17:00 | Agenda Overview |
Wednesday, 2019-11-20
| Time | Assembly Hall | 1.3.14 (Zoo) | 1.1.9 (Landsberger Allee) | 1.1.8 (Greifwalder Str) |
|---|---|---|---|---|
| 9:00 - 9:40 | Qt Marketplace | |||
| 9:50 - 10:30 | ||||
| 10:30 - 10:50 | Coffee Break | |||
| 10:50 - 11:30 | ||||
| 11:40 - 12:20 | ||||
| 12:20 - 13:20 | Lunch Break | |||
| 13:20 - 14:00 | ||||
| 14:10 - 14:50 | ||||
| 14:50 - 15:10 | Coffee Break | |||
| 15:10 - 15:50 | ||||
| 16:00 - 17:00 | Plenary Session |
Thursday, 2019-11-21
| Time | Assembly Hall | 1.3.14 (Zoo) | 1.1.9 (Landsberger Allee) | 1.1.8 (Greifwalder Str) |
|---|---|---|---|---|
| 9:00 - 9:40 | Qt CMake Workshop | |||
| 9:50 - 10:30 | ||||
| 10:30 - 10:50 | Coffee Break | |||
| 10:50 - 11:30 | ||||
| 11:40 - 12:20 | ||||
| 12:20 - 13:20 | Lunch Break | |||
| 13:20 - 14:00 | ||||
| 14:00 - 15:00 | Plenary Session |
Sessions
Qt Marketplace
Tino Pyssysalo and Marko Finnig
Qt Marketplace status, existing and planned features, launch schedule, content publishing process, and content usage.
Qt 6 Graphics Overview
Laszlo & co.
Let's have an overview of graphics related changes in Qt 6. The keynote will probably mention some of these, the goal in this session is to expand on them a bit. There can then be deeper individual discussions on specific topics during the next two days, if there is interest.
C++17 language and std library features for Qt 6
Volker Hilsheimer
With Qt 6 we want to be able to use some C++ 17 language and std library features. Not all compilers and platforms we are going to care about by the time Qt 6 comes around will support evertyhing, so this needs a balanced discussion of up- and down-sides, leading to a pragmatic subset that we can rely on. See https://bugreports.qt.io/browse/QTBUG-77477 for details.
Code Review: Sharing the load
Sometimes we wait and wait for anyone to review our changes. Sometimes we struggle to keep up with all the reviews we're asked to look at. How can we organise this so that no-one waits too long but all of us still have time to hack on code ? Time To Be Arranged.
API Review Process
Volker Hilsheimer
As experienced during Qt 5.13 and Qt 5.14 releases, some changes to APIs were getting feedback only very late in the release process, when the header diff was uploaded for sanity review. This seems a bit late. I'd like to see if we can find a more effective way of integrating API reviews into the general code review process. Perhaps changes that change public headers require a slightly different process than fixes and changes that touch only the implementation.
Evolving the Qt Project Security Policy
Volker Hilsheimer
During summer, the Qt Project Security Policy was moved from a wiki page into QUIP-15, and during that review process, some changes and additions were proposed to strengthen the project's capability to respond to security issues. Those changes were not taken into the QUIP as part of the move, since for the moment we only wanted to move the content. Suggestions included a clearer statement how security fixes are applied to LTS releases; the integration of CVE handling when disclosing vulnerabilities; the documentation of processes established by the Qt Company; and a general review of the way the "core team of developers" is organized, and operating.
Discussing these (and additional) proposals, and agreeing on what should become part of the policy (and thus the responsibility of the Qt project) is the purpose of this session. A proposal is available here: https://codereview.qt-project.org/c/meta/quips/+/278819
Qt for Python and beyond
Cristián Maureira-Fredes
After one year since the official release of Qt for Python we have been getting many new ideas for features to include in the next releases. Most of the features are explained in the latest blog post we wrote, but nevertheless we should try to build the next versions in favor of the Qt ecosystem, this means not only improving the Qt for Python project, but more like answering the question "How Qt for Python can improve the Qt project?". Please join us in this session to discuss how we can make Qt for Python a first-class citizen in the project by giving it more responsibility.
Improve the contributor experience of the Qt project
Cristián Maureira-Fredes
After the following steps:
- Creating Qt account,
- Creating Gerrit account,
- Agreeing with the CLA,
- Configure gerrit locally.
You are ready to start contributing.
If you think that it is too much, you should join this discussion. We aim to focus on having a welcoming and easy-to-do process for getting more people involved in contributing to Qt. Check the related task on JIRA