Hi,
Just in case, the link to the survey is at the bottom of each page, just above
the footer.
You might miss it if you don’t scroll down enough.
Best regards
Samuel
> On 2 May 2024, at 14:58, Safiyyah Moosa via Development
> wrote:
>
> This email is from an unusual correspondent. Make
On lundi, 26 septembre 2022 09.11:23 h CEST Volker Hilsheimer wrote:
> Hi,
>
>
> I would like to nominate Christian and Andy as co-maintainers for Qt SQL.
>
> Mark Brand, who is currently listed as the maintainer of Qt SQL, hasn’t
> responded to any of my emails, including one from two weeks
> On 13 Jun 2022, at 09:19, Frederik Gladhorn wrote:
>
> Hello :)
>
> I've lately not had time to contribute to Qt (personal life keeping me busy).
> Since Volker and others did a great job porting Qt Speech to Qt 6, they know
> the code better than me by this time. I'd like to step down as
Hi,
+1
Best regards
Samuel
> On 18 May 2022, at 10:28, Lars Knoll wrote:
>
> Hi all,
>
> As I’ve said in my other email, I am resigning from my position at The Qt
> Company to join a small startup in Norway that is working with things
> unrelated to Qt.
>
> As such, I won’t have too much
Hi Lars,
Thank you for the ride !
The road has seen some bumps but your teams and you have managed to keep Qt
moving forward in interesting ways through all these years.
It has been a pleasure to work with you on some of my contributions.
All the best for your new journey !
Samuel
> On 18
> On 28 May 2021, at 11:31, Tor Arne Vestbø wrote:
>
>
> Cheers,
> Tor Arne
>
>> On 28 May 2021, at 10:54, Samuel Gaist via Development
>> wrote:
>>
>>>
>>> On 28 May 2021, at 10:37, Lars Knoll wrote:
>>>
>>>
> On 28 May 2021, at 10:37, Lars Knoll wrote:
>
>> On 28 May 2021, at 10:27, Samuel Gaist wrote:
>>
>>
>>> On 28 May 2021, at 10:09, Lars Knoll wrote:
>>>
On 28 May 2021, at 09:15, Alberto Mardegan
wrote:
Hi Lars,
On 26/05/21 15:09, Lars Knoll wrote:
>
> On 28 May 2021, at 10:09, Lars Knoll wrote:
>
>> On 28 May 2021, at 09:15, Alberto Mardegan
>> wrote:
>>
>> Hi Lars,
>>
>> On 26/05/21 15:09, Lars Knoll wrote:
>>> The hope is that we can change that for Qt 6. To make this possible, we
>>> have changed not only parts of the public API,
> On 27 May 2021, at 14:35, Lars Knoll wrote:
>
>> On 27 May 2021, at 14:25, Eike Hein wrote:
>>
>> May 27, 2021 8:14 AM, "Lars Knoll" wrote:
>>> The one thing I want to avoid is what we had in Qt 5, where you could force
>>> Qt MM to use a
>>> different/custom gstreamer pipeline based on
> On 18 Mar 2021, at 19:38, Cristián Maureira-Fredes
> wrote:
>
> Dear community,
>
> The Qt Project is a huge effort from many people, and for the same
> reason, it's quite interesting to (1) Learn how to contribute and be
> part of it, and (2) Analyze the interactions of the many
> Qt
>
> On 18 Feb 2021, at 07:30, Eskil Abrahamsen Blomfeldt
> wrote:
>
> Hi all!
>
> I would like to nominate Aleix Pol Gonzalez as an approver for the Qt Project.
>
> Aleix has been a contributor to KDE and Qt for many years, touching on many
> different areas of Qt, and has lately been
> On 17 Sep 2020, at 11:37, André Hartmann wrote:
>
> Hi all,
>
> I like to propose Alex Trotsenko as approver.
>
> Alex has been contributing to Qt since 2014, and has done *a lot*
> of low level optimization and fixes. He has a deep knowledge of
> QIODevice, Q*Socket, QProcess, and related
Hi,
> On 27 Aug 2020, at 19:07, Edward Welbourne wrote:
>
> Martin Koller (14 August 2020 17:06) wrote:
>
>> I found myself getting an empty list when using
>> QHelpEngineCore::documentsForIdentifier(id) but getting 1 element when
>> using the deprecated
Hi Aapo,
Thanks for the great work on our beloved CI.
And welcome on board Toni !
Samuel
> On 27 Mar 2020, at 08:35, Aapo Keskimölö wrote:
>
> Hi Qt Developers,
>
> I would like to let you know that I will be leaving development tasks at Qt
> for the time being to follow my other dream in
> On 6 Mar 2020, at 12:00, Alex Blasche wrote:
>
>> Thanks for the heads up. Whoever is maintaining those repos (?) need to turn
>> off issues:
>> >https://help.github.com/en/github/managing-your-work-on-github/disabling-issues
>
> I wish this could be done via the parent organization. But
Hi,
For once, something not strictly code related :-)
Some of the latest Qt modules that have been synced to GitHub still have
"issues" activated and for example:
https://github.com/qt/qtquick3d
has already several posted.
Also concerned:
https://github.com/qt/qtshadertools
16 matches
Mail list logo
