Resent, to fix the cc to the Development mailing list.

> Am 19.06.2024 um 10:17 schrieb Eike Ziller via Qt-creator 
> <qt-creator@qt-project.org>:
> 
> Hi,
> 
> I nominate André Hartmann as the new maintainer of Version Control in Qt 
> Creator. His contribution history in Qt Creator goes back to 2011 as well, 
> and he regularly worked on improving our version control support (as well as 
> contributing to Qt and maintaining qtserialbus/CANBus). 
> https://codereview.qt-project.org/q/owner:aha_1...@gmx.de
> Jarek is already maintainer under the Qt Governance Model (parts of Qt 
> Creator and QtHelp) and can certainly act as a backup.
> 
> Br, Eike
> 
>> Am 14.06.2024 um 14:31 schrieb Orgad Shaneh <org...@gmail.com>:
>> 
>> Hi,
>> 
>> I've been using Qt Creator since its first version and began contributing to 
>> it in 2011 (with Gitorious :p). When I joined AudioCodes, I introduced Qt 
>> Creator there, and for many years, most of the C++ developers in my team 
>> have been using it daily.
>> 
>> Over the years, I've made numerous contributions to the project, reporting 
>> 952 bugs and submitting 3,370 commits to Qt Creator. However, in recent 
>> years, I've been working on a different project which isn't written in C++. 
>> As a result, I use Qt Creator less frequently and have much less time to 
>> maintain it.
>> 
>> I still use and love Qt Creator, and it remains my first choice for C++, but 
>> I can no longer continue maintaining it. I propose André Hartmann or Jarek 
>> Kobus as my successors.
>> 
>> I'll likely stay around and be available for reviews ;)
>> 
>> Thank you all for this great product!
>> - Orgad
> 

-- 
Eike Ziller
Principal Software Engineer

The Qt Company GmbH
Erich-Thilo-Str. 10
12489 Berlin, Germany
eike.zil...@qt.io
https://qt.io

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


-- 
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

Reply via email to