Re: [Development] Nominating Dennis Oberst for approver rights

[Alex Blasche via Development]

Congratulations to Dennis. Approver rights have been granted.

--
Alex




From: Development  on behalf of Alexey 
Edelev via Development 
Sent: Thursday, 30 May 2024 08:46
To: development@qt-project.org
Subject: [Development] Nominating Dennis Oberst for approver rights


Hi all,

I would like to nominate Dennis Oberst for approver rights in the Qt project.

Dennis joined in 2022 and did a great job in various Qt subprojects, providing 
strong patches and insightful reviews. I personally appreciate his 
contributions to QtGrpc, which he continues to make.

Changes owned:
* https://codereview.qt-project.org/q/owner:dennis.obe...@qt.io

Changes commented/voted on:
* https://codereview.qt-project.org/q/commentby:dennis.obe...@qt.io

Regards,
Alexey.


Alexey Edelev

Software Engineer

Qt Group
Erich-Thilo-Str. 10 12489
Berlin, Germany

alexey.ede...@qt.io

www.qt.io

[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/Qt-Group-logo-black-1.png]
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/facebook-x2-right.png]

[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/twitter-x2.png] 
 
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/linkedin-x2.png]
 
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/youtube-x2.png] 

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Changing Qt's Binary Compatibility policy

[Alex Blasche via Development]

>From: Development  on behalf of apoenitz 
>
>Sent: Friday, 14 June 2024 19:32

>There are by now ~240 QT_DEPRECATED_VERSION_X_6_* in qtbase alone. Fixing them
>today involves touching thousands line of code in my code base(s). Very few of
>them are truly, clearly necessary. The bulk is "nice to have" or "should have
>been like that from the beginning (but the benefit is not sufficient to
>the drop the original)", and a few are just pain without (significant) gain.

Our biggest issue is the adoption of Qt by users moving from one major release 
to the next. The deprecations start to become a liability and while they keep 
SC compatibility in check for Qt 6 they become a serious concern for any 
adoption of Qt 7. While doing changes when it is necessary is OK as part of a 
major patch release, I totally agree with Andre that a lot of deprecations are 
nice to have and not mandatory. I would like to propose a far more restrictive 
process on when a deprecation is accepted (unless somebody has a better idea on 
how to curb this flood gate any other way).

If you need any further prove of the seriousness of this problem, have a look 
at how long it took for KDE to adopt Qt 6 or look at the still incoming issues 
for Qt 5.15. Based on what I see, performance differences are the most common 
reason why Qt 6 is not ported to. The second one is the effort to port to Qt 6 
due to mechanical porting from one API to the next. 

Qt 7 deprecations show an alarming trend and those mostly don't even involve 
truly needed architecture changes like potential QIODevice or QFileSystemEngine 
changes yet. (I only use these two classes examples to highlight the point and 
not that there is actual work being decided or ongoing)

>As an example for the latter: QCryptographicHash::addData() went from
>QByteArray plus ptr/len overload to a single addData(QByteArrayView bytes).
>Most of the existing uses were of the addData(reinterpret_castY*(), sizeof(something)) kind - ugly enough already, but now it needs
>an additional QByteArrayView() wrapped around. Why? Why can't the ptr/len
>overload just stay? One line, inline, on the library side? Because someone
>doesn't like raw pointers but a struct with a raw pointer and an int will
>save the world?

Based on current adoption issues with Qt 5.15, these changes constitute an 
alarming adoption problem for Qt 7. I cannot even argue to a customer what good 
this change would do to his code or even Qt. The right way should have been to 
add the new function, leave the old one in and remove the old one from the 
docs/mark it as \internal.

On Friday 24 May 2024 13:29:41 GMT-3 Giuseppe D'Angelo via Development wrote:
>2) We stop guaranteeing forward binary compatibility within the same
>minor version.

For what it is worth, I agree too.

--
Alex
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Tim Blechmann for approver

[Alex Blasche via Development]

Congratulations to Tim. Approver rights have been granted.


--

Alex




From: Development  on behalf of Jøger 
Hansegård via Development 
Sent: Wednesday, 22 May 2024 10:52
To: development@qt-project.org 
Subject: [Development] Nominating Tim Blechmann for approver

Hi all,

I would like to nominate Tim Blechmann for approver rights in the Qt project.

Since 2013, Tim has been an active contributor to Qt, providing strong patches 
and insightful reviews. Currently, he is doing excellent work on the GStreamer 
backend in Qt Multimedia.

Changes owned:
* https://codereview.qt-project.org/q/owner:t...@klingt.org

Changes commented/voted on:
* https://codereview.qt-project.org/q/commentby:t...@klingt.org

Best regards,
Jøger Hansegård

--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Update for bugreports.qt.io

[Alex Blasche via Development]

The update is complete. Please report any issues you might experience to 
jira-ad...@qt-project.org.


--

Alex




From: Alex Blasche 
Sent: Friday, 17 May 2024 14:34
To: development@qt-project.org 
Subject: Update for bugreports.qt.io

Hi,

The server will receive a Jira maintenance update. The update will start on Mo 
27.5. at 7:00 am CEST. The outage is expected to last about 2h.

For further questions please use jira-ad...@qt-project.org.

--
Alex
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Update for bugreports.qt.io

[Alex Blasche via Development]

Hi,

The server will receive a Jira maintenance update. The update will start on Mo 
27.5. at 7:00 am CEST. The outage is expected to last about 2h.

For further questions please use jira-ad...@qt-project.org.

--
Alex
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Lucie Gerard for approver rights

[Alex Blasche via Development]

Congratulations to Lucie. Approver rights have been granted.


--

Alex




From: Development  on behalf of Jörg 
Bornemann via Development 
Sent: Wednesday, 24 April 2024 09:45
To: Qt development mailing list 
Subject: [Development] Nominating Lucie Gerard for approver rights

I'd like to nominate Lucie Gerard as an approver for the Qt project.

Lucie has been working on qttools since quite some years, contributed
to the clang-based lupdate and clazy. Lately, she's taken care of the
license checker.

I trust her to be a good approver.

Authored changes:
https://codereview.qt-project.org/q/owner:lucie.gerard%2540qt.io
Reviews:
https://codereview.qt-project.org/q/reviewer:lucie.gerard%2540qt.io

Disclaimer: We are working in the same team.

--
Jörg Bornemann | The Qt Company

--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Stepping down as a maintainer of Qt OPC UA

[Alex Blasche via Development]

From: Development  on behalf of Frank 
Meerkötter 

>I would like to nominate Jannis Völker  as
>the new maintainer.

>https://codereview.qt-project.org/q/owner:jannis.voel...@basyskom.com

+1 from me and I have met Jannis and Frank :)

--
Alex
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Jøger Hansegård for approver rights

[Alex Blasche via Development]

Congratulations to Jøger, approver rights have been set.
--
Alex



From: Development  on behalf of Tor Arne 
Vestbø via Development 
Sent: Thursday, 14 March 2024 10:06
To: development
Subject: [Development] Nominating Jøger Hansegård for approver rights

Hi,

I would like to nominate Jøger Hansegård for approver rights in the Qt project.

Jøger joined The Qt Company 10 months ago and has since then been getting his 
hands dirty in Qt Multimedia, and lately focusing on color management.

Jøger is a thorough and responsible engineer and I trust that he will make a 
good approver for the Qt project.

Authored changes: 
https://codereview.qt-project.org/q/owner:joger.hansegard%2540qt.io
Reviews: https://codereview.qt-project.org/q/reviewer:joger.hansegard%2540qt.io

Cheers,
Tor Arne
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Dr. Máté Barany as an approver for the Qt project

[Alex Blasche via Development]

Congratulations to Máté. Approver rights have been granted.

--
Alex



From: Development  on behalf of Axel Spoerl 
via Development 
Sent: Wednesday, 6 March 2024 23:09
To: development@qt-project.org
Subject: [Development] Nominating Dr. Máté Barany as an approver for the Qt 
project

Dear Colleagues,

I hereby nominate Dr. Máté Barany as an approver for the Qt project.
Máté has been a valuable contributor and reviewer, providing sound code, 
guidance and input.
As a reference, see his dashboard 
here:https://codereview.qt-project.org/dashboard/1010490

I fully trust his advice, expertise and judgement. I am certain that he will 
exercise approver rights to the benefit of the Qt project.

I am neither working in Máté's team, nor sharing an office with him.
Máté and I do know each other personally.

Kind regards
Axel


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Piotr Wierciński for approval status

[Alex Blasche via Development]

Congratulations to Piotr. Approver rights have been granted.

--
Alex



From: Development  on behalf of Morten 
Sørvig via Development 
Sent: Thursday, 8 February 2024 09:39
To: development@qt-project.org
Subject: [Development] Nominating Piotr Wierciński for approval status

I would like to nominate Piotr Wierciński for approver rights in the Qt project.

Piotr joined the Qt company early 2013 and has since then contributed to Qt for 
WebAssembly. This includes many bugfixes and also larger efforts such as 
getting tests running in the CI system.

Piotr is a pleasure to work with and I trust that he will make a good approver 
for the Qt project.

Changes:  https://codereview.qt-project.org/q/owner:piotr.wiercinski
Reviews:  https://codereview.qt-project.org/q/commentby:piotr.wiercinski 


Best regards,
Morten
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Hatem ElKhrarashy for approval status

[Alex Blasche via Development]

Congratulations to Hatem, approver rights have been granted.

--
Alex




From: Development  on behalf of Janne 
Koskinen via Development 
Sent: Tuesday, 6 February 2024 10:18
To: 'Qt development mailing list'
Cc: Hatem ElKharashy
Subject: [Development] Nominating Hatem ElKhrarashy for approval status

I would like to nominate Hatem Elkharashy for approver rights in the Qt project.

Hatem has been working on Qt Graphics for 2,5 years contributing to QtQuick3D, 
QtCharts, QtDeclarative, QtBase and most recently on QtSvg.

Changes where he is the author:
https://codereview.qt-project.org/q/owner:hatem.elkharashy%2540qt.io

Changes where he is reviewer:
https://codereview.qt-project.org/q/reviewer:hatem.elkharashy%2540qt.io

-Janne Koskinen
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating David Redondo for approval status

[Alex Blasche via Development]

Congratulations to David, approver rights have been granted.

--
Alex



From: Development  on behalf of David 
Edmundson 
Sent: Thursday, 1 February 2024 15:10
To: development
Subject: [Development] Nominating David Redondo for approval status

I would like to nominate David Redondo for approver rights in the Qt project.

David's first contributions to Qt started in November 2020, but has
ramped up this last year working on the Qt Wayland platform. Not only
has he fixed a lot of issues within Qt Wayland, but he has also
managed to push changes into upstream wayland and un-break a lot of
important Qt functionality.
David and I work together at Blue Systems for the last 4 years. I have
full confidence in his ability to review code correctly and also to
use any new privileges appropriately.

Changes where he is the author:
https://codereview.qt-project.org/q/author:qt%2540david-redondo.de
Changes where he commented/voted on:
https://codereview.qt-project.org/q/reviewer:qt%2540david-redondo.de

David
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Vlad Zahorodnii for approval status

[Alex Blasche via Development]

Congratulations to Vlad, Approver rights have been granted.

--
Alex



From: Development  on behalf of David 
Edmundson 
Sent: Thursday, 1 February 2024 15:11
To: development
Subject: [Development] Nominating Vlad Zahorodnii for approval status

I would like to nominate Vlad Zahorodnii for approver rights in the Qt project.

Vlad has also been working on the QtWayland backend, providing insight
based on his other role as one of the kwin maintainers.
Vlad and I have been working together at Blue Systems for 5 years. He
is extremely technically competent and very thorough in reviews. I
trust that he would exercise approver rights responsibly.

Changes where he is the author:
https://codereview.qt-project.org/q/author:vlad.zahorodnii%2540kde.org
Changes where he commented/voted
https://codereview.qt-project.org/q/reviewer:vlad.zahorodnii%2540kde.org
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Matthias Rauter for approval status

[Alex Blasche via Development]

Congratulations to Matthias. Approver rights have been granted.

--
Alex



From: Development  on behalf of Paul Tvete 
via Development 
Sent: Tuesday, 30 January 2024 13:11
To: Qt development mailing list
Subject: [Development] Nominating Matthias Rauter for approval status

Hi,

I would like to nominate Matthias Rauter as an approver for the Qt Project.

Matthias has been working on Qt for more than a year now. In this time, he has 
done great work on Qt Location and Qt SVG, among other. I have had the pleasure 
to work with him on the Curve Rendering project in Qt Quick Shapes where he has 
made impressive contributions. He has been consistently professional in 
development and review, and I am certain that he will exercise his approver 
powers responsibly.

List of changes made by Matthias: 
https://codereview.qt-project.org/q/owner:matthias.rauter%2540qt.io
Matthias's review activity: 
https://codereview.qt-project.org/q/commentby:matthias.rauter%2540qt.io

Cheers,
 - Paul
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] About the timeline and phases to support C++20 with and in Qt

[Alex Blasche via Development]

Hi,

For Qt 6.8 we continue to work on Phase 1 item 
https://bugreports.qt.io/browse/QTBUG-109360. In other words we will not  
mandate C++20 compilers in Qt 6.8 yet. An LTS release is not the right for such 
a breaking change anyway. The possible releases for such a drastic change are 
6.9 or 6.12 (releases immediately following an LTS release). Note that I am not 
cofirming those releases but merely point out which type of releases could be 
potential options.

Considering the track record we have when getting Phase 1 items into the 
release and considering existing customer concerns I have a hard time believing 
that 6.9 is a serious option. This is my personal opinion.

--
Alex



From: Development  on behalf of Thiago 
Macieira 
Sent: Saturday, 3 February 2024 18:13
To: development@qt-project.org
Subject: Re: [Development] About the timeline and phases to support C++20 with 
and in Qt

On Wednesday, 21 December 2022 09:51:52 PST Vladimir Minenko via Development
wrote:
> We got four user stories on Qt Bug Reports:
>
> 1. Use C++20 code with Qt - https://bugreports.qt.io/browse/QTBUG-109360
> 2. C++20 is required for the development of Qt itself -
> https://bugreports.qt.io/browse/QTBUG-109361
> 3. C++20 is mandatory for users of Qt -
> https://bugreports.qt.io/browse/QTBUG-109362

Those tasks haven't got any updates recently. What's the status?

I'd like to ask that we go to #3 for 6.8 or 6.9.


--
Thiago Macieira - thiago.macieira (AT) intel.com
  Cloud Software Architect - Intel DCAI Cloud Engineering
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Question about the licensing of the Protobuf-Module

[Alex Blasche via Development]

The fix is here: https://codereview.qt-project.org/c/qt/qtgrpc/+/533391

--
Alex




From: Development  on behalf of Frank 
Meerkötter 
Sent: Tuesday, 23 January 2024 09:19
To: development@qt-project.org
Subject: Re: [Development] Question about the licensing of the Protobuf-Module

Thank you for the clarification

On 22.01.24 19:53, Elias Steurer via Development wrote:
> This was (sadly) a bug, see comments:
> https://bugreports.qt.io/browse/QTBUG-117783
>
> Cheers ,
>
> Eli
>
> On 1/22/2024 10:29 AM, Frank Meerkötter wrote:
>> I am looking for a clarification on the licensing of the
>> Protobuf-Module.
>>
>> The code in https://code.qt.io/cgit/qt/qtgrpc.git/tree/src/protobuf
>> has // SPDX-License-Identifier: LicenseRef-Qt-Commercial OR
>> LGPL-3.0-only OR GPL-2.0-only OR GPL-3.0-only
>>
>> While the code in
>> https://code.qt.io/cgit/qt/qtgrpc.git/tree/src/protobufqttypes/protobufqtcoretypes
>> has // SPDX-License-Identifier: LicenseRef-Qt-Commercial OR
>> GPL-3.0-only WITH Qt-GPL-exception-1.0
>>
>> Is this intentional?
>>
>> Can I - wearing a LGPL3-hat - use the protobuf module?
>>
>> Thank you,
>> Frank
>>
--
Frank Meerkötter
Development Lead

basysKom GmbH
Robert-Bosch-Str. 7 | 64293 Darmstadt | Germany
Tel: +49 6151 870 589 - 161 | Fax: -199
frank.meerkoet...@basyskom.com | http://www.basyskom.com/

Handelsregister: Darmstadt HRB 9352
Geschaeftsfuehrende Partner: Heike Ziegler, Alexander Sorg

--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Jira update on 5th January 2024

[Alex Blasche via Development]

The update has concluded.

--
Alex



From: Development  on behalf of Alex 
Blasche via Development 
Sent: Wednesday, 3 January 2024 08:59
To: development@qt-project.org
Subject: [Development] Jira update on 5th January 2024

Hi,

We will update Jira on 5th January 2024. The update will cause about two hours 
of service outage and starts at 7:00 am CET.

For those interested in details, we will update Jira from version 9.4.6 to 
9.4.14. This being an LTS release branch, the update brings a lot of bug fixes 
but no new features. If you are interested in patch details check out:

https://confluence.atlassian.com/jirasoftware/jira-software-9-4-x-release-notes-1178869757.html

Please report any issues and concerns to jira-ad...@qt-project.org.
--
Alex

--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Jira update on 5th January 2024

[Alex Blasche via Development]

Hi,

We will update Jira on 5th January 2024. The update will cause about two hours 
of service outage and starts at 7:00 am CET.

For those interested in details, we will update Jira from version 9.4.6 to 
9.4.14. This being an LTS release branch, the update brings a lot of bug fixes 
but no new features. If you are interested in patch details check out:

https://confluence.atlassian.com/jirasoftware/jira-software-9-4-x-release-notes-1178869757.html

Please report any issues and concerns to jira-ad...@qt-project.org.
--
Alex

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Semih Yavuz as an approver for the Qt project

[Alex Blasche via Development]

Congratulations to Semih. Approver rights have been granted.

--
Alex




From: Development  on behalf of Sami 
Shalayel via Development 
Sent: Friday, 8 December 2023 15:50
To: development@qt-project.org
Subject: Re: [Development] Nominating Semih Yavuz as an approver for the Qt 
project

Hi,

Semih has been doing good work for the QML Language Server and the
QmlDom, +1 from me.

Disclaimer: He is working in my team and we share the same office.

Best regards,

Sami

On 07.12.23 15:45, Fabian Kosmale via Development wrote:
> Hi,
>
> I would like to nominate Semih Yavuz for approver rights to the Qt project.
>
> Semih has been working on the Qt project since September 2022. He has been 
> mainly focusing
> on the QML tooling story, including work on qmlformat and the QML language 
> server. In addition,
> he is also taking care of the (non-LSP based ) Qt Creator QML integration.
> Finally, he has also been reviewing changes in all parts of QML.
>
> I fully trust his judgement in reviewing and approving changes.
>
> Changes where he is the author: 
> https://codereview.qt-project.org/q/owner:semih.yavuz%2540qt.io
> Changes where he commented/voted on: 
> https://codereview.qt-project.org/q/commentby:semih.yavuz%2540qt.io
>
> Disclosure: Semih is working in my team and we share the same office.
>
> Kind Regards,
> Fabian
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] HEADS-UP: Branching from 'dev' to '6.7' done

[Alex Blasche via Development]

I'd like to request an extension for the following features:

1.) The Embedding QML into Native Android patch series did not make it due to 
Integrity issues:
- Android QPA series starting with 
https://codereview.qt-project.org/c/qt/qtbase/+/511975
- QMLItemView series starting with 
https://codereview.qt-project.org/c/qt/qtdeclarative/+/501890

2.) The chromium rebase v118 needed to go in first due to complexity which just 
merged this weekend. Subsequently two smaller WebEgnine features still need to 
merge:
- https://codereview.qt-project.org/c/qt/qtwebengine/+/487442 (dd new API for 
screen capturing)
- https://codereview.qt-project.org/c/qt/qtwebengine/+/442539 (Add new API for 
screen capturing)

3.) Formatting support for JS files has been delayed due to CI shenanigans
https://codereview.qt-project.org/c/qt/qtdeclarative/+/519854 (QmlFormat: 
Support .js files (CLI tool))


--
Alex



From: Development  on behalf of Jani 
Heikkinen via Development 
Sent: Monday, 11 December 2023 07:15
To: development@qt-project.org
Subject: [Development] HEADS-UP: Branching from 'dev' to '6.7' done

Hi!

Branching from ‘dev’ to ‘6.7’ is now done and the Qt 6.7 Feature Freeze is in 
effect! So from now on all changes targeted to the Qt 6.7 must have 'Pick-to: 
6.7' and 'dev' is for Qt 6.8.



Unfortunately there were (and still are) issues with CI's INTEGRITY builds, so 
if something urgent was left out because of this, please request an exception 
to be able to integrate them into the 6.7 branch as well.



br,

Jani Heikkinen

Release Manager


From: Development  On Behalf Of Jani 
Heikkinen via Development
Sent: perjantai 8. joulukuuta 2023 16.06
To: development@qt-project.org
Subject: [Development] HEADS-UP: Qt 6.7 Feature Freeze


Hi!



Qt 6.7 Feature Freeze will be in effect today. If your changes are ready and 
approved by the end of today, you can still continue staging those in 'dev' 
over the weekend. The plan is to branch from "6.7" to "dev" on Monday morning 
next week.



If your feature isn't ready by the end of today, you'll either need to postpone 
it to Qt 6.8 or request an exception.



br,

Jani Heikkinen

Release Manager

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Jaishree Vyas as approver

[Alex Blasche via Development]

Congratulations to Jaishree. Approver rights have been granted.

--
Alex



From: Development  on behalf of Paul 
Wicking via Development 
Sent: Wednesday, 8 November 2023 10:00
To: development@qt-project.org
Subject: [Development] Nominating Jaishree Vyas as approver

Hi everyone,

I would like to nominate Jaishree Vyas for approver rights in the Qt project.

Jai has joined TQtC as a Documentation Engineer back in February 2022. Since 
then, she's been actively making and reviewing changes. I fully trust Jai's 
judgment in reviewing and approving changes, and see her as a positive addition 
to the Qt Project.

Her authored changes are here: 
https://codereview.qt-project.org/q/owner:jaishree.vyas%40qt.io
As reviewer: 
https://codereview.qt-project.org/q/reviewer:jaishree.vyas%2540qt.io

//! Paul

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Nominating QtGRPC & Qt Protobuf maintainers

[Alex Blasche via Development]

Hi,

Qt GRPC and Qt Protobuf were added to Qt a while ago. However until now they 
have been in Tech Preview mode. As we investigate the remaining issues which 
might prevent us from leaving TP, we need to address the open issue of 
maintainer-ship.

I'd like to nominate Tatiana Borisova as maintainer for Qt Protobuf and Alexey 
Edelev as maintainer for Qt GRPC. In fact, both have been working on this code 
base even before they officially became part of Qt. I am glad they agreed to 
continue this work going forward in the context of Qt Development.

--
Alex

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Adrian Herrmann as approver for the Qt project

[Alex Blasche via Development]

Congratulations to Adrian. Approver rights have been granted.

--
Alex




From: Development  on behalf of Shyamnath 
Premnadh via Development 
Sent: Tuesday, 22 August 2023 09:35
To: development@qt-project.org
Subject: [Development] Nominating Adrian Herrmann as approver for the Qt project

Hi All,

I would like to nominate Adrian Herrmann for approver rights to the Qt project.

Adrian has been working on the Qt for Python project for more than a year now, 
and has made significant contributions to bug fixing, QtAsyncio (enables 
interoperability between Python's asyncio package and Qt) etc. I trust Adrian's 
judgment in review and approving changes.

Changes where he is the author: 
https://codereview.qt-project.org/q/owner:adrian.herrmann%2540qt.io
Changes where he commented/voted on: 
https://codereview.qt-project.org/q/commentby:adrian.herrmann%2540qt.io

Regards,
Shyam


Shyamnath, Premnadh

Senior Software Engineer - Qt for Python

The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany

shyamanath.premn...@qt.io

+49 15780598679

www.qt.io

Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen Sitz der 
Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B

[https://www.qt.io/]
[https://www.facebook.com/qt/]
[https://twitter.com/qtproject]  
[https://www.linkedin.com/company/qtgroup/] 
 
[https://www.youtube.com/QtStudios] 









-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Artem Sokolovskii

[Alex Blasche via Development]

Congratulations to Artem. Approver rights have been set.

--
Alex



From: Development  on behalf of Marcus 
Tillmanns via Development 
Sent: Tuesday, 8 August 2023 15:25
To: development@qt-project.org
Subject: [Development] Nominating Artem Sokolovskii

Hello all,

I would like to nominate Artem Sokolovskii for approver rights in the Qt 
project.

Artem is a member of the Qt Creator Team and has been working on Code 
formatting and is now creating a DAP integration for the Creator.

You can see his merged changes here:
https://codereview.qt-project.org/q/owner:artem.sokolovskii%2540qt.io+is:merged

And his reviews here:
https://codereview.qt-project.org/q/reviewer:artem.sokolovskii%2540qt.io

Cheers,
Marcus
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Kwanghyo Park as approver

[Alex Blasche via Development]

Congrats to Kwanghyo. Approver rights have been granted.

--
Alex



From: Development  on behalf of Tomi 
Korpipää via Development 
Sent: Monday, 14 August 2023 08:54
To: development@qt-project.org
Subject: [Development] Nominating Kwanghyo Park as approver

Hi,

I'd like to nominate Kwanghyo Park for approver status. He is the main 
developer for Surface3D graphs for the QtGraphs module, and has been 
contributing to QtDataVisualization, QtQuick3D, and QtLottie as well.

https://codereview.qt-project.org/q/owner:kwanghyo.park%2540qt.io
https://codereview.qt-project.org/q/reviewer:kwanghyo.park%2540qt.io

He has been and continues being a productive member of the Oulu Graphics team.


Tomi Korpipää

Senior Manager, R

The Qt Company Oy
Tutkijantie 4C
90590 Oulu
Finland

tomi.korpi...@qt.io

+358445312522

www.qt.io

[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/Qt-Group-logo-black.png]
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/facebook-x2-right_2023-03-01-095511_zhlr.png]
 
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/twitter-x2.png] 
 
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/linkedin-x2.png]
 
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/youtube-x2.png] 


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QtFluentMQ

[Alex Blasche via Development]

+1 from me as it is the Foundation area which will mostly support the 
process/development.

--
Alex



From: Development  on behalf of team 
fluentmq 
Sent: Sunday, August 27, 2023 03:55
To: Volker Hilsheimer; development@qt-project.org
Subject: Re: [Development] QtFluentMQ

Hello,

Thanks for welcoming the project everybody.

> AFAIR we haven't bike shedded over the commercial value of a new repository, 
> the architecture of the code it shall hold, or its licensing before. I don't 
> think we need to.
To be fair, while we're Qtifying our API to give back to the community as Qt 
has been good for us for a long time going, we're also looking forward to 
acheive framework community grade robustness through a Qt integration as this 
is the most sensitive part of our product designed for (extra) large scale 
distributions. We did ask for an intent of integration had the project held its 
ground in term of compatibility with the Qt project for us to allocate the 
ressources for that which is why Volker mentioned the need for internal 
discussions. Using the playground as an assessment buffer for the integration 
sounds like a party !

> You should fill in at least the basic information, though: name and 
> description, responsible person, and desired location.

name: QtFluentMQ
description:

The "QtFluentMQ" project aims to create a user-friendly and versatile message 
queue (MQ) client using the Qt 6 framework. This client seamlessly handles 
communication with major MQ platforms. The first release would implement the 
AMQP protocol thus supporting RabbitMQ, ActiveMQ, Apollo, Artemis, IBM MQ, 
Amazon MQ and more. It will also migrate the existing Kafka implementation to 
Qt to support the Kafka platform as well, the current MQ market leader.

At its core, the project involves a top-layer abstraction called QMQInstance. 
This layer acts as a bridge between the application and various MQ platforms. 
Within this layer, there are two main components: QConsumer and QProducer, 
which can also be referred to as QQmlConsumer and QQmlProducer when working 
with QML.

QMQInstance provides a unified QMessage Interface that simplifies the process 
of sending and receiving data to and from different MQ brokers. This uniform 
interface streamlines the interaction with multiple MQ platforms, making it 
easier for developers to integrate messaging functionality into their 
applications.

One of the standout features of this project is its dynamic configurability. 
The client can be configured through a JSON input. This flexibility allows 
developers to adapt the client's behavior to specific use cases and 
requirements without significant code changes.

Additionally, the project supports queues context switching. This means that 
the client can seamlessly switch between different queues or channels within 
the MQ platforms. This feature is particularly useful for managing multiple 
communication channels efficiently and ensuring the smooth flow of data.

Finally, the QtFluentMQ actively supports open-source initiatives like 
Plumber, a versatile CLI tool for 
seamless interaction with various messaging systems, including Kafka and 
RabbitMQ. By collaborating with projects like Plumber, Fluent MQ enhances the 
CI/CD process by offering an all-in-one tooling package that streamlines 
operations and simplifies integration tasks."

In summary, QtFluentMQ project offers a comprehensive and easy-to-use solution 
for interacting with various MQ platforms. Its abstraction layer, dynamic 
configurability, and support for queues context switching contribute to a 
seamless messaging experience for developers working with Qt 6 applications.

responsible person:  George Ransdall

desired location: Playground

 Br
QtFluentMQ Team



From: Volker Hilsheimer 
Sent: Saturday, August 26, 2023 11:34 AM
To: Ulf Hermann ; development@qt-project.org 

Subject: Re: [Development] QtFluentMQ

> On 26 Aug 2023, at 10:09, Ulf Hermann via Development 
>  wrote:
>
> Hi,
>
> The usual way to request a repository, playground or not, is a mail like this:
>
> https://lists.qt-project.org/pipermail/development/2022-August/042900.html
>
> If the request is not totally outlandish it's usually granted, possibly after 
> some bike shedding over the name and location.
>
> AFAIR we haven't bike shedded over the commercial value of a new repository, 
> the architecture of the code it shall hold, or its licensing before. I don't 
> think we need to.
>
> You should fill in at least the basic information, though: name and 
> description, responsible person, and desired location.
>
> At least sometimes, we have used the lazy consensus mechanism for repository 
> requests in the past. This seems a good idea to me. I will +1 this one if the 
> (still missing) basics are reasonable.
>
> We can still discuss the way to integrate with 

[Development] New "In Review" workflow state in Jira

[Alex Blasche via Development]

Hi,

During recent times we got more and more requests from developers to have an 
"In Review" status in Jira. The idea is to park tasks in this state while one 
waits for more feedback on gerrit. Whether you keep it in this state while you 
continue to actively incorporate review feedback or move it back to "In 
Progress" is mostly up to individual decision. 

My recommendation would be to shift it back to "In Progress" if the review 
feedback causes you to undergo larger rework. As long as you still have pending 
work (but parts are up for review already)  I suggest to keep it  "In Progress" 
to indicate your active development state.

In particular on scrum or Kanban boards this might come in very handy as one 
can indicate a certain openness for new tasks.

As a consequence I modified the workflow to have this additional step. I 
attached a diagram to illustrate the modification. It is totally optional 
though. You can still directly jump from "In Progress" to "Closed". Also note 
that Jira still considers the "In Review" status as unresolved.

This change affects the following issue types: Bug, Task, Suggestion, Sub-task, 
Technical task. If needed/desired it could be rolled out for Epic/User Story 
issues too but I don't want to go there until some feedback is received.

For the time being I enabled this for the QTBUG project and I would appreciate 
your feedback on it. 

--
Alex
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Santhosh Kumar Selvaraj for approver rights

[Alex Blasche via Development]

Congratulations. OG Approver status has been granted.

--
Alex




From: Development  on behalf of Jan-Arve 
Sæther via Development 
Sent: Tuesday, 20 June 2023 20:55
To: Jack Simcox via Development
Subject: [Development] Nominating Santhosh Kumar Selvaraj for approver rights

Hello all,

I would like to nominate Santhosh Kumar Selvaraj for approver rights in the Qt 
project.

Santhosh is a member of the UI Team, and has been working on improvement to our 
styles, dark mode support, palette handling both in qtbase and qtdeclarative.

You can see his merged changes here:
https://codereview.qt-project.org/q/owner:santhosh.kumar.selvaraj%2540qt.io+is:merged

and his reviews here:

https://codereview.qt-project.org/q/reviewer:santhosh.kumar.selvaraj%2540qt.io

cheers,
---
Jan Arve Sæther
Team Lead

The Qt Company
Sandakerveien 116
0484, Oslo, Norway
jan-arve.saet...@qt.io
http://qt.io
---


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Artem Dyomin as Approver

[Alex Blasche via Development]

Hi,

Congratulations to Artem. Approver rights have been granted.

--
Alex



From: Development  on behalf of Lars Knoll 

Sent: Saturday, 27 May 2023 17:41
To: Qt development mailing list
Subject: [Development] Nominating Artem Dyomin as Approver

Hi all,

I’d like to nominate Artem Dyomin for approver rights in Qt.

Artem has been working with Qt Multimedia since last summer, doing a very good 
job implementing new features, fixing bugs and refactoring code in the module.

You can see his merged changes here: 
https://codereview.qt-project.org/q/owner:artem.dyomin%2540qt.io+is:merged

And his reviews here: 
https://codereview.qt-project.org/q/reviewer:artem.dyomin%2540qt.io

Cheers,
Lars

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Tatiana Borisova as approver

[Alex Blasche via Development]

Congratulations to Tatiana, approver rights have been granted.

--
Alex

> -Original Message-
> From: Development  On Behalf Of
> Alexey Edelev via Development
> Sent: Tuesday, 23 May 2023 15:40
> To: Qt development mailing list 
> Subject: [Development] Nominating Tatiana Borisova as approver
> 
> Hello everyone,
> 
> 
> I would like to nominate Tatiana Borisova for approver rights in the Qt 
> project.
> 
> Tatiana has been contributing to the Qt Project as a TQtC employee since 2021,
> where most of her work went towards to our INTEGRITY support.
> 
> She recently joined the Qt Core team,
> and has been mainly working on QtGrpc among other contributions to qtbase,
> qtdeclarative, and other modules.
> 
> You can see her merged changes here:
> https://codereview.qt-
> project.org/q/owner:tatiana.borisova%2540qt.io+is:merged
> 
> and her reviews here:
> https://codereview.qt-project.org/q/reviewer:tatiana.borisova%2540qt.io
> 
> 
> 
> 
> 
> Alexey Edelev
> 
> Software Engineer
> 
> 
> 
> Qt Group
> Erich-Thilo-Str. 10 12489
> Berlin, Germany
> 
> alexey.ede...@qt.io
> 
> www.qt.io 
> 
> 
> 
> 
> 
> 
>  
>   
> 
> 
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Konrad Kujawa as approver

[Alex Blasche via Development]

Congratulations to Konrad. Approver rights have been granted.

--
Alex

> -Original Message-
> From: Development  On Behalf Of
> Alexey Edelev via Development
> Sent: Wednesday, 24 May 2023 12:31
> To: Qt development mailing list 
> Subject: [Development] Nominating Konrad Kujawa as approver
> 
> Hello everyone,
> 
> I would like to nominate Konrad Kujawa for approver rights in the Qt project.
> 
> 
> Konrad is a member of the Qt Core team, and has been mainly working on QtGrpc
> among other contributions to qtbase, qthttpserver, qtdeclarative and other 
> repos.
> 
> 
> You can see his merged changes here:
> 
> https://codereview.qt-project.org/q/owner:konrad.kujawa%2540qt.io+is:merged
> 
> 
> and his reviews here:
> 
> https://codereview.qt-project.org/q/reviewer:konrad.kujawa%2540qt.io
> 
> 
> 
> 
> 
> Alexey Edelev
> 
> Software Engineer
> 
> 
> 
> Qt Group
> Erich-Thilo-Str. 10 12489
> Berlin, Germany
> 
> alexey.ede...@qt.io
> 
> www.qt.io 
> 
> 
> 
> 
> 
> 
>  
>   
> 
> 
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Requesting Feature Freeze Exception for C++20 comparison

[Alex Blasche via Development]

>From: Development  on behalf of Volker 
>Hilsheimer 

>Lets continue with this for Qt 6.7.

>Even if we agree on the naming and can exclude binary compatibility issues, 
>rolling this out to all (or at least a substantial amount of) existing value 
>types across >submodules is still a larger effort that should then wait for 
>6.7 anyway.

I don't see it as necessary to roll this out throughout all submodules with 
such a tight 6.7 schedule. This won't happen for Qt 6.7 because most devs may 
see this adoption as somewhat optional or at least do it on their own timeline. 
The point of using date and time as example was to proof the concept. This is 
an API offer for other maintainers to adopt in their API offering. We have 
never made it a condition for features to be adopted by every single module. It 
has always been a multi release affair and by comparison is the same as API 
deprecation from an adoption perspective.

The patch series was up for review and there was a very active discussion 
including naming for weeks already. While I accept concerns I am very 
disappointed that such reviews come in 2 days before FF with immediate 
rejection for the upcoming release due to timing. This was not the first time. 
Since this diminish my confidence that this won't happen again I would like to 
see a measure in place that can avoid this. 

IMO the compat and naming issues can be worked out (FF extension is 
sufficient). I very much object to delaying because of submodule adoption. It 
was always out of scope for 6.6 and for 6.7 it is not achievable either. Hence 
it cannot be a reason for delaying comparisons.

--
Alex
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Jere Tuliniemi for approver

[Alex Blasche via Development]

Congratulations to Jere. Approver rights have been granted.
--
Alex



From: Development  on behalf of Tomi 
Korpipää via Development 
Sent: Friday, 12 May 2023 09:12
To: development@qt-project.org
Subject: [Development] Nominating Jere Tuliniemi for approver

Hi,


I'd like to nominate Jere Tuliniemi for approver status. He has been working 
with Qt for several years, contributing to Qt 3D Studio, ogl-runtime, 
QtQuick3D, Qt 3D, and QtGraphs to name a few. You can see his commits here: 
https://codereview.qt-project.org/q/owner:jere.tuliniemi%2540qt.io

Br,

Tomi Korpipää

Senior Manager, R

Qt Group
Tutkijantie 4C
FI-90590 Oulu
Finland

tomi.korpi...@qt.io

+358445312522

www.qt.io

[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/Qt-Group-logo-black.png]
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/facebook-x2-right_2023-03-01-095511_zhlr.png]
 
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/twitter-x2.png] 
 
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/linkedin-x2.png]
 
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/youtube-x2.png] 


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Jira/bugreports update on 31.5.2023

[Alex Blasche via Development]

Hi,

Though we had a hiccup on the update start time (was started too early), the 
upgrade seems to have run smoothly. Please let us know if you run into issues.

--
Alex

P.S. We have updated from Jira 8.x to 9.x. In some areas you'll have to retrain 
your muscle memory as the update brings a few UI changes.


From: Development  on behalf of Alex 
Blasche via Development 
Sent: Monday, 22 May 2023 09:31
To: development@qt-project.org
Subject: [Development] Jira/bugreports update on 31.5.2023

Hi,

bugreports.qt.io will be updated to Jira version 9.4. The upgrade will happen 
on 31. May 2023 at 08:00 GMT+2 (CEST) and is expected to last about 90 mins.

For any issues or concerns please contact jira-ad...@qt-project.org.
--
Alex
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Konrad Kujawa as approver

[Alex Blasche via Development]

+1

--
Alex



From: Development  on behalf of Alexey 
Edelev via Development 
Sent: Wednesday, 24 May 2023 12:30
To: Qt development mailing list
Subject: [Development] Nominating Konrad Kujawa as approver

Hello everyone,

I would like to nominate Konrad Kujawa for approver rights in the Qt project.

Konrad is a member of the Qt Core team, and has been mainly working on
QtGrpc among other contributions to qtbase, qthttpserver, qtdeclarative and
other repos.

You can see his merged changes here:
https://codereview.qt-project.org/q/owner:konrad.kujawa%2540qt.io+is:merged

and his reviews here:
https://codereview.qt-project.org/q/reviewer:konrad.kujawa%2540qt.io


Alexey Edelev

Software Engineer

Qt Group
Erich-Thilo-Str. 10 12489
Berlin, Germany

alexey.ede...@qt.io

www.qt.io

[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/Qt-Group-logo-black-1.png]
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/facebook-x2-right.png]

[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/twitter-x2.png] 
 
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/linkedin-x2.png]
 
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/youtube-x2.png] 

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Tatiana Borisova as approver

[Alex Blasche via Development]

>From: Development  on behalf of Alexey 
>Edelev via Development 
>I would like to nominate Tatiana Borisova for approver rights in the Qt 
>project.

+1

--
Alex
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Jira/bugreports update on 31.5.2023

[Alex Blasche via Development]

Hi,

bugreports.qt.io will be updated to Jira version 9.4. The upgrade will happen 
on 31. May 2023 at 08:00 GMT+2 (CEST) and is expected to last about 90 mins.

For any issues or concerns please contact jira-ad...@qt-project.org.
--
Alex
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Requesting a repository for Qt/.NET

[Alex Blasche via Development]

Hi Miguel,

please go ahead.

--
Alex



From: Development  on behalf of Miguel 
Costa via Development 
Sent: Tuesday, 9 May 2023 15:27
To: development@qt-project.org
Subject: [Development] Requesting a repository for Qt/.NET

Hi,

On behalf of the dev team working on the Qt and VS integration, I would like to 
request a new repository where we can base a .NET integration module that we've 
recently been working on.

Name of the repository: qt-labs/qtdotnet.git
Description: The Qt/.NET library enables the integration of Qt with .NET 
libraries and applications.
Responsible person: Miguel costa
Gerrit user/email: mecfc / miguel.co...@qt.io

Qt/.NET implements a custom .NET host (cf. 
https://learn.microsoft.com/en-us/dotnet/core/tutorials/netcore-hosting) which 
allows calling into managed code from native C++. The library also supports 
writing C++ wrapper classes for managed types, to encapsulate the details of 
using the .NET host. These wrapper classes can be based on QObject, allowing a 
tight integration of managed code with Qt features like signal-slot connections 
or the Qt property system.

For more details, see the README at: https://git.qt.io/micosta/qtdotnet
Relevant topics:
  * Calling .NET static methods
  * Handling .NET exceptions
  * Creating .NET objects
  * Calling instance methods
  * Writing C++ wrapper classes for .NET types
  * Emitting Qt signals from .NET events
  * Using .NET objects in QML
  * Using QML in a WPF application
  * Example application: QML UI for a .NET module
  * Example application: QML window embedded in WPF application

Thank you for your attention.
Please let me know if you have any questions or comments.

BR,
--Miguel Costa

--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Header review process: follow-up on comments

[Alex Blasche via Development]

Earlier this week I discussed https://bugreports.qt.io/browse/QTQAINFRA-4763 
with Eddy. He will look into it. At the very least it creates more but also 
more targetted review requests. Especially qtbase suffers from this. It should 
make the responsibility of the maintainers more obvious. Hopefully we can 
manage to get this for the 6.6 review round.

--
Alex



From: Development  on behalf of Fabian 
Kosmale via Development 
Sent: Tuesday, 2 May 2023 11:33
To: development@qt-project.org
Subject: Re: [Development] Header review process: follow-up on comments

Hi,

while gerrit _didn't_ have support for it, that changed in 3.7. It needs
to be manually enabled
(https://www.gerritcodereview.com/3.7.html#mention-user-support), but
maybe that would be a good way forward?

Fabian

On 02.05.23 11:00, Volker Hilsheimer via Development wrote:
> With Qt 6.5, it’s been a struggle to get people to respond and follow-up to 
> comments made during the header review process.
>
> Gerrit doesn’t really care about @user-style mentioning in comments, even 
> though is seems that some people assume that it does. Creating JIRA tickets 
> is the official way of doing it, but creating a ticket just to get someone’s 
> attention to input (which might or might not require a change) seems 
> heavy-handed. Ultimately, lots of people will be on cc or review of the 
> respective header-review gerrit change, so everything becomes everyone’s 
> problem.
>
> Maintainers have a special responsibility during header review, but esp with 
> qtbase that is also a lot of people.
>
> What can we do to make this a better process that doesn’t end up with changes 
> being made very late (with 6.5 we had some the day before the release 
> candidate, IIRC)?
>
> Volker
>

--
Fabian Kosmale
Manager R

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin
fabian.kosm...@qt.io
+49 1638686070
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Tinja Paavoseppä as an approver for the Qt Project

[Alex Blasche via Development]

Congratulations to Tinja. Approver rights have been set.

--
Alex



From: Development  on behalf of Nicholas 
Bennett via Development 
Sent: Tuesday, 21 March 2023 08:50
To: development@qt-project.org
Subject: [Development] Nominating Tinja Paavoseppä  as an approver for the Qt 
Project

Hi all,



I'd like to nominate Tinja Paavoseppä as an approver for the Qt Project.



Tinja is  a seasoned developer who has been a Qt user for many years.

Her work with coding, documenting and approving for the Qt for Android 
Automotive project has been exemplary.



I  trust she will bring the same diligence to reviewing the Qt Framework.


disclaimer: We work in the same team.

Cheers,
Nicholas Bennett
Senior Documentation Engineer
Qt Group
Tutkijantie 4C
FI-90590 Oulu
Finland
nicholas.benn...@qt.io
+358503231959
www.qt.io
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/Qt-Group-logo-black.png]
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/facebook-x2-right_2023-03-01-095511_zhlr.png]
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/twitter-x2.png]
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/linkedin-x2.png]
[https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/youtube-x2.png]

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Mats Honkamaa as an approver for the Qt Project

[Alex Blasche via Development]

Congratulations to Mats, approver rights have been granted.

--
Alex


From: Development  on behalf of Mahmoud Ali 
via Development 
Sent: Tuesday, 17 January 2023 16:56
To: development@qt-project.org
Cc: Mats Honkamaa
Subject: [Development] Nominating Mats Honkamaa as an approver for the Qt 
Project

Hi all,

I'd like to nominate Mats Honkamaa as an approver for the Qt Project.

Mats has been working on Qt Studio Design Studio documentation and has 
regularly contributed to Qt Design Studio documentation.

Qt Commits:
   https://codereview.qt-project.org/q/owner:mats.honkamaa%2540qt.io

disclaimer: We work in the same team.


I trust him to be a good reviewer.


Kind regards,
Mahmoud Badri
Manager, R
The Qt Company
Tutkijantie 4C
FI-90590 Oulu
Finland
mahmoud.ba...@qt.io
+358 50 512 9535
www.qt.io
[cid:image001.png@01D92A9D.065535E0]
[cid:image002.png@01D92A9D.065535E0]
[cid:image003.png@01D92A9D.065535E0]
[cid:image004.png@01D92A9D.065535E0]
[cid:image005.png@01D92A9D.065535E0]


-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Mikołaj Boć as approver

[Alex Blasche via Development]

Congratulations to Mikołaj, approver rights have been granted.

--
Alex


From: Development  on behalf of Morten 
Sørvig via Development 
Sent: Wednesday, 21 December 2022 15:21
To: development@qt-project.org
Subject: [Development] Nominating Mikołaj Boć as approver

Hi,


I’d like to nominate Mikołaj Boć as an approver for the Qt project.

Mikołaj joined the Qt Company earlier this year and hit the ground running. He 
has contributed features and many bug fixes for the Qt for WebAssembly platform 
integration, as well as bug fixes for other parts of Qt.

I trust him to be a good approver. Links to gerrit dashboards:

Patches: 
https://codereview.qt-project.org/q/owner:Mikolaj.Boc%2540qt.io
Reviews: 
https://codereview.qt-project.org/q/reviewer:Mikolaj.Boc%2540qt.io

(I’m a colleague of Mikołaj at the Qt Company where we are on the same team)

Regards,
Morten
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Jira update on 3rd Janaury 2023

[Alex Blasche via Development]

Hi André,

>___
>From: André Hartmann 

>it seems I now have gray "Edit" and "Delete" buttons below every Jira
>report comment. I think that was a pen at the right top of every comment
>in the old version.

>Was this change intentional?

I must assume this was intentional by Atlassian. I did a quick search for a UI 
option to revert it but could not find a way. It is indeed a bit too much in 
the face.

>Any chance to revert this to the old behavior (maybe a setting)?

There is no UI setting I know of but there is a permission mis-configuration 
here. IMO everybody should only be able to modify their own comments.  This 
permission should only go to a selected group. While the issue log tracks all 
changes it could lead to a situation where one user "puts words into the mouth 
of another". I rectified it by adjusting the permission scheme.

So yes, I reverted the behavior but maybe not in the sense you expected ;) 

--
Alex

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Jira update on 3rd Janaury 2023

[Alex Blasche via Development]

Hi,

The server has been back for a while but just to conclude here, the update is 
complete.

Testing will continue and please forward any issues to 
jira-ad...@qt-project.org. Thank you.

--
Alex


From: Development  on behalf of Alex 
Blasche via Development 
Sent: Wednesday, 21 December 2022 09:18
To: development@qt-project.org
Subject: [Development] Jira update on 3rd Janaury 2023

Hi,

We will update Jira on 3rd January 2023. The update will cause about two hours 
of service outage and starts at 6:00 am CET.

For those interested in details, we will update Jira from version 8.13 to 8.20. 
This upgrade will bring along many new features and security updates. If you 
want to know more, check out the release notes for the releases starting with 
8.14 up to 8.20. They can be found under

https://confluence.atlassian.com/jiracore/jira-core-release-notes-781386726.html

--
Alex
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Shyamnath Premnadh as approver

[Alex Blasche via Development]

Congratulations to Shyam. Approver rights have been granted.

--
Alex


From: Development  on behalf of Alex 
Blasche via Development 
Sent: Monday, 5 December 2022 16:46
To: development@qt-project.org
Subject: [Development] Nominating Shyamnath Premnadh as approver

Hi,


I’d like to nominate Shyamnath Premnadh as an approver for the Qt project.

Shyam has been working in The Qt Company since December 2021. His main area of 
contribution has been the Qt for Python project where he fixes bugs, provides 
documentation and ensures that all new Qt additions find a proper adoption in 
Python. His most recent contributions focus on the deployment support.

His gerrit dashboard links are:

Contributions: 
https://codereview.qt-project.org/q/owner:Shyamnath.Premnadh%2540qt.io
Reviews: 
https://codereview.qt-project.org/q/reviewer:Shyamnath.Premnadh%2540qt.io

Disclosure: I’m Shyam's indirect line manager at The Qt Company in Berlin.

--
Alex
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Axel Spoerl as approver

[Alex Blasche via Development]

Congratulations to Axel. Approver rights have been granted.

Happy New Year.
--
Alex


From: Development  on behalf of Volker 
Hilsheimer via Development 
Sent: Monday, 5 December 2022 10:57
To: development@qt-project.org
Subject: [Development] Nominating Axel Spoerl as approver

Hi,


I’d like to nominate Axel Spoerl as an approver for the Qt project.

Axel has been working in The Qt Company since January, writing tests, analysing 
and fixing bugs, participating in the port of Qt Speech to Qt 6, investigating 
and stabilising flaky tests across all platforms, and most recently 
implementing platform theme support for GTK3-based Linux desktop environments.

I trust him to be a good approver. Links to gerrit dashboards:

Patches: https://codereview.qt-project.org/q/owner:axel.spoerl%2540qt.io
Reviews: https://codereview.qt-project.org/q/reviewer:axel.spoerl%2540qt.io

Disclosure: I’m Axel’s indirect line manager at The Qt Company in Oslo.


Volker

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Jira update on 3rd Janaury 2023

[Alex Blasche via Development]

Hi,

We will update Jira on 3rd January 2023. The update will cause about two hours 
of service outage and starts at 6:00 am CET.

For those interested in details, we will update Jira from version 8.13 to 8.20. 
This upgrade will bring along many new features and security updates. If you 
want to know more, check out the release notes for the releases starting with 
8.14 up to 8.20. They can be found under

https://confluence.atlassian.com/jiracore/jira-core-release-notes-781386726.html

--
Alex
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Marcus Tillmanns as Approver

[Alex Blasche via Development]

Congratulations to Marcus. Approver rights have been granted.

--
Alex


From: Development  on behalf of A. Pönitz 

Sent: Tuesday, 22 November 2022 22:27
To: development@qt-project.org
Subject: [Development] Nominating Marcus Tillmanns as Approver



I'd like to nominate Marcus Tillmanns as an approver for the Qt project.

Marcus has been working on Qt Creator since April, mostly on Docker
support and remote file access/command execution, but also on LLDB
support and various other changes across the code base.

He made already several excellent contributions, most notably authored
the remote filesystem browsing capabilities in Creator 9.

I trust him to be a good approver.

Link to his gerrit dashboard:

Patches:
https://codereview.qt-project.org/q/owner:marcus.tillmanns%2540qt.io
Reviews:
https://codereview.qt-project.org/q/reviewer:marcus.tillmanns%2540qt.io

We are working in the same team, and share an office.

Andre'

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Nominating Shyamnath Premnadh as approver

[Alex Blasche via Development]

Hi,


I’d like to nominate Shyamnath Premnadh as an approver for the Qt project.

Shyam has been working in The Qt Company since December 2021. His main area of 
contribution has been the Qt for Python project where he fixes bugs, provides 
documentation and ensures that all new Qt additions find a proper adoption in 
Python. His most recent contributions focus on the deployment support.

His gerrit dashboard links are:

Contributions: 
https://codereview.qt-project.org/q/owner:Shyamnath.Premnadh%2540qt.io
Reviews: 
https://codereview.qt-project.org/q/reviewer:Shyamnath.Premnadh%2540qt.io

Disclosure: I’m Shyam's indirect line manager at The Qt Company in Berlin.

--
Alex
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Mårten Nordheim and Timur Pocheptsov as new co-maintainers of Qt WebSocket

[Alex Blasche via Development]

>From: Development  on behalf of Volker 
>Hilsheimer via Development >


>And I’d like to nominate Mårten Nordheim and Timur Pocheptsov as 
>co-maintainers. I’ve confirmed with them, and >they would be ok with extending 
>their existing co-maintainership of Qt Network to that module as well.

+1

--
Alex
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Sami Shalayel as approver

[Alex Blasche via Development]

OG Approver rights have been granted. Congratulations to Sami.

--
Alex


From: Development  on behalf of Fabian 
Kosmale via Development 
Sent: Friday, 4 November 2022 09:14
To: qt-dev
Subject: [Development] Nominating Sami Shalayel as approver

Hi,

I'd like to nominate Sami Shalayel as an approver for the Qt project.

Sami is employed by the Qt Company and has been working since May on Qt, mostly
on QtDeclarative, with a focus on qmltc.
He made several good contributions there, and also participates in the review
process of QML related patches.

I trust him to be a good approver. Link to his gerrit dashboard:

Patches:
https://codereview.qt-project.org/q/owner:sami.shalayel%2540qt.io
Reviews:
https://codereview.qt-project.org/q/reviewer:sami.shalayel%2540qt.io

Disclosure: I'm Sami's direct line manager at the Qt Company, and share
an office with him.

Fabian
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] How qAsConst and qExchange lead to qNN

[Alex Blasche via Development]

--
Alex

> -Original Message-
> From: Development  On Behalf Of
> Volker Hilsheimer via Development
> Sent: Monday, 7 November 2022 16:51
> To: Marc Mutz ; development@qt-project.org
> Subject: Re: [Development] How qAsConst and qExchange lead to qNN
> 
> > On 4 Nov 2022, at 16:00, Marc Mutz via Development  project.org> wrote:
> >
> > Hi,
> >
> > After getting my head washed by Volker, lemme provide background on
> > these two functions.
> 
> Thanks for the context, Marc!
> 
> > TL;DR: we created real maintenance and porting problems by not
> > removing stop-gap functionality in a timely fashion, qNN presented as
> > a way to ensure this won't happen again.
> >
> > Both qAsConst and qExchange are 1:1 reimplementations of std
> > functionality we couldn't rely on back then (as_const is C++17 and
> > exchange is C++14), so they're exactly equivalent to the std versions.
> > Or were, when they were added.
> >
> > Neither std::as_const nor qAsConst have changed, so the replacement is
> > easy: s/qAsConst/std::as_const/. It cannot not compile because
> > qAsConst comes from qglobal.h and that transitively includes
> > . This is what was intended from the get-go:
> 
> 
> The open question is whether and when we should deprecate such a stop-gap
> 1:1 reimplementations of std functionality. How to deprecate is now well
> documented, but the wiki starts with the process of doing so once we concluded
> that we shall. It doesn’t give us any guidance yet on how to come to that
> conclusion.

I had to ask Volker which wiki he refers to and maybe it is the same for 
somebody else too. The URL is 

https://wiki.qt.io/Deprecation

> When it’s time to phase out one of our own qNN implementations, then
> 
> 1) propose the change here first to raise awareness, and to give people time 
> to
> ask questions and/or raise objections
> 
> Even if the people doing the work all agree, a lot of maintainers and
> contributors will still be impacted (at least by the tool being removed). The
> proposal should come with some data about how prevalent the usage of the
> relevant construct is in Qt. It makes a difference whether we’d have to touch 
> a
> few dozen lines, or several hundred to remove all usage.
> 
> 2) If possible, add a warning to the sanity bot so that no new usage is added
> 
> This is trivial in some cases, not so trivial in others. Rationale: For 
> changes that
> impact a larger amount of code, there’ll be plenty of time between those
> changes getting merged, and the old Qt-implementation ultimately getting
> removed or fully deprecated (which we can’t/shouldn’t do while we still have
> usage in Qt itself). For example, we now have some qAsConst back in the qtbase
> code.

I support this. In particular, the open communication before the fact is the 
key here. Let's face it, Qt is large enough that it cannot be expected that 
everybody knows what's going on in all the modules and such changes may never 
hit a developer's radar until after the merge and its enforcement.

I propose we add the gist of Volker's proposal to the deprecation wiki 
mentioned above.

> Whether we then do a bulk replacement in Qt, or whether we just stop using old
> stuff in new code and phase it out over time as we touch code (until here’s
> perhaps little enough left to make a bulk change), depends on the discussion. 
> If
> we do make a bulk change, then making that change in stable branches to avoid
> cherry-picking conflicts would probably be ok as well (unless those branch 
> can’t
> use the new C++ version yet).

Though Volker kind of implies that his two rules might lead to cherry-picking 
back into older releases, I would like to see this as explicitly mentioned 
option wherever we document the rules.

> From: Development  On Behalf Of
> Marc Mutz via Development

>#define Q_FOREACH(decl, expr) \
>   for (const auto _q_foreach_c = expr; decl : _q_foreach_c)
> 
> And I'd probably approve it, because then that thing can actually just be 
> replaced
> with the expansion everywhere, and then, finally, be deleted.

Considering the above, this kind of change would have to be brought up to the 
mailing list and be discussed before any approval is given. 

--
Alex
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Szabolcs David as Approver

[Alex Blasche via Development]

 Congratulations. OG Approver rights have been set.

--
Alex


From: Development  on behalf of Allan 
Sandfeld Jensen 
Sent: Monday, 19 September 2022 16:51
To: development@qt-project.org
Subject: [Development] Nominating Szabolcs David as Approver

Hi,

I'd like to propose Szabolcs David as an Qt Project Approver.

Dashboard: https://codereview.qt-project.org/dashboard/1002939

Szabolcs has been working for us as an external contributor for at least 8
years now. With that many years of experience contributing to Qt WebEngine, I
think it is about time we grant him approver rights.

Best regards,
Allan Sandfeld Jensen




___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development