Re: [Development] Solutions for ensuring that changes in upstream modules are tested with downstream modules before merging

2021-06-15 Thread Shawn Rutledge

On 2021 Jun 7, at 15:30, Mitch Curtis 
mailto:mitch.cur...@qt.io>> wrote:

Some I can think of:

- Slower git operations.
- Slower build times for qtdeclarative devs. You can use e.g. ninja targets, 
but you would have to do this every time you build. Ideally we’d add a 
configure option for this, like -no-gui in qtbase, so that they don’t need to 
build qtquickcontrols2.

FWIW, I’m routinely building all of Qt together (the modules that I have 
anyway) with cmake and ninja.  (It’s around 15k steps, building all autotests 
but not examples.  A Zen3 processor and ccache make it bearable.  Before that, 
I was using icecc.)  So the cases where I have broken something in controls by 
making a change in qtdeclarative are usually only test failures (behavior 
changes), not build failures, right?  (Or at least not build failures that I 
didn’t know about.)  I never run all autotests in all modules locally, because 
it takes too long.  Even running all tests in qtdeclarative takes too long, 
except when the change is so invasive that I know I really need to.  If I’m 
worried about a specific change breaking controls, I run those tests.  (The 
script to run tests in xephyr is handy, so I can keep using the computer while 
they are running.)

- Creator would probably be quite a bit slower to work with having both of 
these in one project.

Qtdeclarative is already a rather big module.  And Creator is slow, for sure.  
It’s been a couple of years since I could use it at all on my older laptops 
without enough memory.

This why I like the idea of just running qtquickcontrols2 tests for each 
qtdeclarative change: it doesn’t waste developer time (and again, CI 
integrations don’t count since they shouldn’t be wasting developer time).

Hopefully that will work, yeah.

Though then you do lose the ability to use controls in examples, which does 
seem like a huge loss.

It depends whether we care about being able to automatically test examples 
without building controls first, right?  Otherwise I thought the existing 
advice lately is to go ahead and use controls in examples?

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


Re: [Development] Nominating Ivan Solovev as approver

2021-06-15 Thread Assam Boudjelthia
Ivan's reviews are very helpful.

+1

--
Assam Boudjelthia
Senior Software Engineer

The Qt Company
--

From: Development  on behalf of Alex 
Blasche 
Sent: Tuesday, June 15, 2021 2:17 PM
To: development@qt-project.org 
Subject: [Development] Nominating Ivan Solovev as approver

Hi,

I'd like to nominate Ivan Solovev as an approver for the Qt Project.

Ivan has been working on various parts of the Qt6 port and has regularly 
contributed to QtBase  modules, QtPositioning, QtNfc & other modules. 
Personally, I am particularly thankful for his help in furthering the Qt 
Bindings support in QtPositioning and his review of countless other patches in 
the same domain.

He has authored the following patches:
https://codereview.qt-project.org/q/owner:ivan.solovev%2540qt.io,100
and reviewed the following:
https://codereview.qt-project.org/q/reviewer:ivan.solovev%2540qt.io,100

Since  both our office rooms share one wall I am also thankful for many 
technical discussions who broke the enforced solitude of the corona days :)

--
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 Ivan Solovev as approver

2021-06-15 Thread Vladimir Minenko
+1

Yeah! I had a pleasure to follow some of his works as a new colleague.

--
Vladimir


On 15. Jun 2021, at 13:36, Cristián Maureira-Fredes 
mailto:cristian.maureira-fre...@qt.io>> wrote:

+1

I think Ivan has been doing a really good job,
it would be nice to have him as an approver!

Cheers

On 6/15/21 1:17 PM, Alex Blasche wrote:
Hi,
I'd like to nominate Ivan Solovev as an approver for the Qt Project.
Ivan has been working on various parts of the Qt6 port and has regularly 
contributed to QtBase  modules, QtPositioning, QtNfc & other modules. 
Personally, I am particularly thankful for his help in furthering the Qt 
Bindings support in QtPositioning and his review of countless other patches in 
the same domain.
He has authored the following patches:
https://codereview.qt-project.org/q/owner:ivan.solovev%2540qt.io,100
and reviewed the following:
https://codereview.qt-project.org/q/reviewer:ivan.solovev%2540qt.io,100
Since  both our office rooms share one wall I am also thankful for many 
technical discussions who broke the enforced solitude of the corona days :)
--
Alex
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

--
Dr. Cristián Maureira-Fredes
R&D Manager

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

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
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 Ivan Solovev as approver

2021-06-15 Thread Cristián Maureira-Fredes

+1

I think Ivan has been doing a really good job,
it would be nice to have him as an approver!

Cheers

On 6/15/21 1:17 PM, Alex Blasche wrote:

Hi,

I'd like to nominate Ivan Solovev as an approver for the Qt Project.

Ivan has been working on various parts of the Qt6 port and has regularly 
contributed to QtBase  modules, QtPositioning, QtNfc & other modules. 
Personally, I am particularly thankful for his help in furthering the Qt Bindings 
support in QtPositioning and his review of countless other patches in the same 
domain.

He has authored the following patches:
https://codereview.qt-project.org/q/owner:ivan.solovev%2540qt.io,100
and reviewed the following:
https://codereview.qt-project.org/q/reviewer:ivan.solovev%2540qt.io,100

Since  both our office rooms share one wall I am also thankful for many 
technical discussions who broke the enforced solitude of the corona days :)

--
Alex


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



--
Dr. Cristián Maureira-Fredes
R&D Manager

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

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


Re: [Development] Nominating Ivan Solovev as approver

2021-06-15 Thread Sona Kurazyan
+1!

Disclaimer: we work in the same team.

> -Original Message-
> From: Development  On Behalf Of
> Alex Blasche
> Sent: Tuesday, June 15, 2021 1:18 PM
> To: development@qt-project.org
> Subject: [Development] Nominating Ivan Solovev as approver
> 
> Hi,
> 
> I'd like to nominate Ivan Solovev as an approver for the Qt Project.
> 
> Ivan has been working on various parts of the Qt6 port and has regularly
> contributed to QtBase  modules, QtPositioning, QtNfc & other modules.
> Personally, I am particularly thankful for his help in furthering the Qt 
> Bindings
> support in QtPositioning and his review of countless other patches in the
> same domain.
> 
> He has authored the following patches:
> https://codereview.qt-project.org/q/owner:ivan.solovev%2540qt.io,100
> and reviewed the following:
> https://codereview.qt-project.org/q/reviewer:ivan.solovev%2540qt.io,100
> 
> Since  both our office rooms share one wall I am also thankful for many
> technical discussions who broke the enforced solitude of the corona days :)
> 
> --
> 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 Ivan Solovev as approver

2021-06-15 Thread Fabian Kosmale
+1

--
Fabian Kosmale
Software Engineer

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin
fabian.kosm...@qt.io
+49 1638686070
http://qt.io


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

--


Von: Development  im Auftrag von Alex 
Blasche 
Gesendet: Dienstag, 15. Juni 2021 13:17
An: development@qt-project.org
Betreff: [Development] Nominating Ivan Solovev as approver

Hi,

I'd like to nominate Ivan Solovev as an approver for the Qt Project.

Ivan has been working on various parts of the Qt6 port and has regularly 
contributed to QtBase  modules, QtPositioning, QtNfc & other modules. 
Personally, I am particularly thankful for his help in furthering the Qt 
Bindings support in QtPositioning and his review of countless other patches in 
the same domain.

He has authored the following patches:
https://codereview.qt-project.org/q/owner:ivan.solovev%2540qt.io,100
and reviewed the following:
https://codereview.qt-project.org/q/reviewer:ivan.solovev%2540qt.io,100

Since  both our office rooms share one wall I am also thankful for many 
technical discussions who broke the enforced solitude of the corona days :)

--
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] Nominating Ivan Solovev as approver

2021-06-15 Thread Alex Blasche
Hi,

I'd like to nominate Ivan Solovev as an approver for the Qt Project.

Ivan has been working on various parts of the Qt6 port and has regularly 
contributed to QtBase  modules, QtPositioning, QtNfc & other modules. 
Personally, I am particularly thankful for his help in furthering the Qt 
Bindings support in QtPositioning and his review of countless other patches in 
the same domain. 

He has authored the following patches:
https://codereview.qt-project.org/q/owner:ivan.solovev%2540qt.io,100
and reviewed the following:
https://codereview.qt-project.org/q/reviewer:ivan.solovev%2540qt.io,100

Since  both our office rooms share one wall I am also thankful for many 
technical discussions who broke the enforced solitude of the corona days :)

--
Alex


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


Re: [Development] Windows maintainer change

2021-06-15 Thread Giuseppe D'Angelo via Development

On 15/06/2021 09:27, Oliver Wolff wrote:

Thanks again to Friedemann for all the work he put into the maintenance
of Qt. You have been doing a great job and I hope that we can ask for
some guidance now and then ;)


Indeed, thank you so much for all the help on Windows. I second the 
nominations.


Cheers,
--
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



smime.p7s
Description: S/MIME Cryptographic Signature
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


Re: [Development] Windows maintainer change

2021-06-15 Thread Ville Voutilainen
On Tue, 15 Jun 2021 at 12:24, Christian Kandeler
 wrote:
>
> +1

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


Re: [Development] Windows maintainer change

2021-06-15 Thread Christian Kandeler

+1

On 6/15/21 9:27 AM, Oliver Wolff wrote:

Hi all,

I would like to propose a change in Qt's Windows maintainership. I 
think that everybody knows, that Friedemann has been doing a great job 
maintaining the Windows platform specifics in Qt's code base. He wants 
to focus on Qt for Python now so we have been looking for an 
alternative way of maintenance.


I propose a shared maintenance between Andre de la Rocha and me for 
Windows. Andre has been involved in Qt's Windows development for 
almost 4 years now. He is responsible for our accessibility backend on 
Windows and rewrote mouse/touch/pen handling for that platform. He 
also wrote the "win32" bluetooth backend and fixed bugs in various 
areas of Qt.


I have been part of the winrt maintainership and wrote and maintain 
the "winrt" backend for Bluetooth (which is also used in Qt6 as the 
backend also works for "desktop" applications on Windows 10).


Thanks again to Friedemann for all the work he put into the 
maintenance of Qt. You have been doing a great job and I hope that we 
can ask for some guidance now and then ;)


Best regards,
Olli
___
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] Windows maintainer change

2021-06-15 Thread Tor Arne Vestbø
Hear hear! +1

> On 15 Jun 2021, at 11:05, Shawn Rutledge  wrote:
> 
> +1
> 
> Thanks for the work that all 3 of you have put into it over the years.
> 
>> On 15 Jun 2021, at 09:27, Oliver Wolff  wrote:
>> 
>> Hi all,
>> 
>> I would like to propose a change in Qt's Windows maintainership. I think 
>> that everybody knows, that Friedemann has been doing a great job maintaining 
>> the Windows platform specifics in Qt's code base. He wants to focus on Qt 
>> for Python now so we have been looking for an alternative way of maintenance.
>> 
>> I propose a shared maintenance between Andre de la Rocha and me for Windows. 
>> Andre has been involved in Qt's Windows development for almost 4 years now. 
>> He is responsible for our accessibility backend on Windows and rewrote 
>> mouse/touch/pen handling for that platform. He also wrote the "win32" 
>> bluetooth backend and fixed bugs in various areas of Qt.
>> 
>> I have been part of the winrt maintainership and wrote and maintain the 
>> "winrt" backend for Bluetooth (which is also used in Qt6 as the backend also 
>> works for "desktop" applications on Windows 10).
>> 
>> Thanks again to Friedemann for all the work he put into the maintenance of 
>> Qt. You have been doing a great job and I hope that we can ask for some 
>> guidance now and then ;)
> 
> ___
> 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] Windows maintainer change

2021-06-15 Thread Robert Löhning

+1

Thank you guys for the work you have done, are doing and will do.

For transparency's sake: Olli is my manager and Andre is on the same team.

Cheers,
Robert

Am 15.06.21 um 09:27 schrieb Oliver Wolff:

Hi all,

I would like to propose a change in Qt's Windows maintainership. I think 
that everybody knows, that Friedemann has been doing a great job 
maintaining the Windows platform specifics in Qt's code base. He wants 
to focus on Qt for Python now so we have been looking for an alternative 
way of maintenance.


I propose a shared maintenance between Andre de la Rocha and me for 
Windows. Andre has been involved in Qt's Windows development for almost 
4 years now. He is responsible for our accessibility backend on Windows 
and rewrote mouse/touch/pen handling for that platform. He also wrote 
the "win32" bluetooth backend and fixed bugs in various areas of Qt.


I have been part of the winrt maintainership and wrote and maintain the 
"winrt" backend for Bluetooth (which is also used in Qt6 as the backend 
also works for "desktop" applications on Windows 10).


Thanks again to Friedemann for all the work he put into the maintenance 
of Qt. You have been doing a great job and I hope that we can ask for 
some guidance now and then ;)


Best regards,
Olli
___
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] Windows maintainer change

2021-06-15 Thread Shawn Rutledge
+1

Thanks for the work that all 3 of you have put into it over the years.

> On 15 Jun 2021, at 09:27, Oliver Wolff  wrote:
> 
> Hi all,
> 
> I would like to propose a change in Qt's Windows maintainership. I think that 
> everybody knows, that Friedemann has been doing a great job maintaining the 
> Windows platform specifics in Qt's code base. He wants to focus on Qt for 
> Python now so we have been looking for an alternative way of maintenance.
> 
> I propose a shared maintenance between Andre de la Rocha and me for Windows. 
> Andre has been involved in Qt's Windows development for almost 4 years now. 
> He is responsible for our accessibility backend on Windows and rewrote 
> mouse/touch/pen handling for that platform. He also wrote the "win32" 
> bluetooth backend and fixed bugs in various areas of Qt.
> 
> I have been part of the winrt maintainership and wrote and maintain the 
> "winrt" backend for Bluetooth (which is also used in Qt6 as the backend also 
> works for "desktop" applications on Windows 10).
> 
> Thanks again to Friedemann for all the work he put into the maintenance of 
> Qt. You have been doing a great job and I hope that we can ask for some 
> guidance now and then ;)

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


Re: [Development] Qt CS 2021 colocated with Akademy, June 22+23 - Akademy CFP ending May 2nd

2021-06-15 Thread Volker Hilsheimer
> On 14 Jun 2021, at 21:16, Robert Löhning  wrote:
> 
> Am 14.06.21 um 14:37 schrieb Alexandru Croitor:
>> On 14. Jun 2021, at 14:11, Volker Hilsheimer  wrote:
>>> 
>>> Hi,
>>> 
>>> 
>>> We will start drafting a schedule for the Qt Contributors Summit this week, 
>>> if there are any topics that you’d like to put on the list, please do so by 
>>> end of Wednesday, June 16th.
>>> 
>>> https://wiki.qt.io/Qt_Contributors_Summit_2021_-_Program
>>> 
>>> 
>>> As a rough outline, we’ll start on Tuesday morning with a few common 
>>> sessions before breaking out into tracks, and we plan to end Wednesday with 
>>> a series of sessions where we hear about the visions and plans for the 
>>> different modules from the maintainers. So as a special request to 
>>> maintainers: perhaps you want to have a session with some relevant people.
>>> 
>>> We have one main room, and 4 breakout rooms, the room URLs are already 
>>> available at
>>> 
>>> https://wiki.qt.io/Qt_Contributors_Summit_2021
>>> 
>>> Looking forward to seeing many of you next week!
>>> 
>>> 
>>> Cheers,
>>> Volker
>> Not sure if this is the right place to ask.
>> Will we have a final session where we go through a list of short 
>> 'conclusions' / 'outcomes' for each held session?
>> I think we had that at the previous QtCon.


Yes, that’s a good thing to have, and it’ll be part of the wrap-up sessions.


> I have a similar question: Will we be able to fill free slots of the 
> timetable ad hoc as we used to do at offline QtCSs?


In principle, yes.

In practice, I’d imagine that having an ad-hoc discussions with a few people in 
a quiet physical spot doesn’t quite translate into a virtual setup where we 
have a fixed room setup. There’ll be chat, but for the video rooms we'll have 
to prioritise, and putting your topic up rather sooner than later helps with 
that. Then we’ll see how many free slots are left in the virtual space-time 
continuum.

Of course, nobody stops anyone from meeting in a parallel virtual Universe, be 
it on matrix or libera or whatever system people can agree on.

Volker


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


[Development] Windows maintainer change

2021-06-15 Thread Oliver Wolff

Hi all,

I would like to propose a change in Qt's Windows maintainership. I think 
that everybody knows, that Friedemann has been doing a great job 
maintaining the Windows platform specifics in Qt's code base. He wants 
to focus on Qt for Python now so we have been looking for an alternative 
way of maintenance.


I propose a shared maintenance between Andre de la Rocha and me for 
Windows. Andre has been involved in Qt's Windows development for almost 
4 years now. He is responsible for our accessibility backend on Windows 
and rewrote mouse/touch/pen handling for that platform. He also wrote 
the "win32" bluetooth backend and fixed bugs in various areas of Qt.


I have been part of the winrt maintainership and wrote and maintain the 
"winrt" backend for Bluetooth (which is also used in Qt6 as the backend 
also works for "desktop" applications on Windows 10).


Thanks again to Friedemann for all the work he put into the maintenance 
of Qt. You have been doing a great job and I hope that we can ask for 
some guidance now and then ;)


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