On 05/04/16 22:56, "Development on behalf of Giuseppe D'Angelo"
wrote:
>Il 10/03/2016 08:37, Knoll Lars ha scritto:
>>> >
>>> >Individually or together, +1 from me.
>> Fully agree with what Alan is saying, so another +1 from me.
>
>I guess it's time to do the honours then? :)
Indeed. I've edit
Il 10/03/2016 08:37, Knoll Lars ha scritto:
>
>Individually or together, +1 from me.
Fully agree with what Alan is saying, so another +1 from me.
I guess it's time to do the honours then? :)
Cheers,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (UK) Ltd., a
+1 from me too.
www.qinetic.com.au - Qt And QML User Experience Specialists
On Thu, Mar 10, 2016 at 7:43 PM, Eskil Abrahamsen Blomfeldt <
eskil.abrahamsen-blomfe...@theqtcompany.com> wrote:
>
>
> Den 09.03.2016 10:56, skrev Frederik Gladhorn:
>
>> We are in the luxury position of having two grea
+alot :)
Simon
From: Development
on behalf
of Eskil Abrahamsen Blomfeldt
Sent: Thursday, March 10, 2016 10:43
To: development@qt-project.org
Subject: Re: [Development] QtQuick Call for Maintainer
Den 09.03.2016 10:56, skrev Frederik Gladhorn:
>
Den 09.03.2016 10:56, skrev Frederik Gladhorn:
We are in the luxury position of having two great candidates.
I briefly talked to both Robin and Shawn yesterday and one option would be to
have a shared maintainership. This seems to have worked nicely for Qt
Networking and dividing the responsibi
On 10/03/16 08:18, "Development on behalf of Alan Alpert"
wrote:
>On Wed, Mar 9, 2016 at 1:56 AM, Frederik Gladhorn
> wrote:
>> We are in the luxury position of having two great candidates.
>> I briefly talked to both Robin and Shawn yesterday and one option would be to
>> have a shared maintai
On Wed, Mar 9, 2016 at 1:56 AM, Frederik Gladhorn
wrote:
> We are in the luxury position of having two great candidates.
> I briefly talked to both Robin and Shawn yesterday and one option would be to
> have a shared maintainership. This seems to have worked nicely for Qt
> Networking and dividing
We are in the luxury position of having two great candidates.
I briefly talked to both Robin and Shawn yesterday and one option would be to
have a shared maintainership. This seems to have worked nicely for Qt
Networking and dividing the responsibilty will lessen the burden.
I'm looking forward
On 08/03/16 09:04, Nurmi J-P wrote:
On 07 Mar 2016, at 20:45, Gunnar Sletta wrote:
I would like to suggest Robin Burchell for the role of future Qt
Quick maintainer.
He is a long time Qt contributor and has repeatedly shown insight
and dedication to the project. From various work he has solid
> On 07 Mar 2016, at 20:45, Gunnar Sletta wrote:
>
> I would like to suggest Robin Burchell for the role of future Qt Quick
> maintainer.
>
> He is a long time Qt contributor and has repeatedly shown insight and
> dedication to the project. From various work he has solid experience building
>
I'm sorry to see you step down, Alan. Thanks for all the good work!
I would like to suggest Robin Burchell for the role of future Qt Quick
maintainer.
He is a long time Qt contributor and has repeatedly shown insight and
dedication to the project. From various work he has solid experience build
On 08/03/16 01:13, Frederik Gladhorn wrote:
I'd like to propose Shawn Rutledge as maintainer for Qt Quick.
+1
--
Software Engineer
Hardware Enablement
Canonical Ltd
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/
Hello Alan,
thanks a lot for all the work you've done!
On Saturday, March 05, 2016 11:40:56 PM Alan Alpert wrote:
> Hi all,
>
> I have been drawn away from Qt Quick at work the past several months,
> for even I do not write back-end services with Qt Quick. Consequently
> I have not had time to f
Hi Alan,
Thanks a lot for your work on Qt Quick over the years.
Let's see who can take over this role, let me/us know if you have an interest
and feel qualified.
Cheers,
Lars
On 06/03/16 08:40, "Development on behalf of Alan Alpert"
wrote:
>Hi all,
>
>I have been drawn away from Qt Qui
Hi all,
I have been drawn away from Qt Quick at work the past several months,
for even I do not write back-end services with Qt Quick. Consequently
I have not had time to fulfill the responsibilities of Qt Quick
Maintainership and will have to pass the mantle onto someone new.
Accepting the unfor
15 matches
Mail list logo
