[Development] QtQuick Call for Maintainer

[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 responsibilty will lessen the burden.

I'm looking forward to having more direction and vision for the development of 
the Qt Quick module as well as getting back to a big round of bug fixes which 
is due in the near future.

Cheers,
Frederik

PS: I briefly checked the rules (http://wiki.qt.io/The_Qt_Governance_Model) and 
found this bit:
"Once seconded, a new Maintainer is appointed unless a community member 
objects to the Chief Maintainer within 15 work days. If an objection is 
raised, the Chief Maintainer decides, usually within 15 work days."


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 fulfill the responsibilities of Qt Quick
> Maintainership and will have to pass the mantle onto someone new.
> 
> Accepting the unfortunate nature of reality means that I must resign
> from the QtQuick maintainership position. Accordingly I have removed
> my name from the maintainers wiki page. Everyone on gerrit knows I'm
> not getting to my reviews anymore, so I can no longer hold a module
> maintainer position.
> 
> It would be great if someone else could step up and take over, as I
> still believe QtQuick is a key component of the premier native GUI
> framework. Any volunteers?
> 
> --
> Alan Alpert
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development