Alan has been very proactive and is probably the best person we have for the job right now. So a +1 from my side.
But the declarative repo is pretty big and very central to Qt moving forward. So I believe we will need to split up responsibilities further in the longer term. I would at the minimum like to split up on a per module basis, maybe even a bit more fine-grained. So one Maintainer for Qt QML, one for Qt Quick, etc. Finally, we also need to ask the person in question: Alan, are you willing to take that role, and will your responsibilities in you day job leave you with enough time to act as the maintainer? Cheers, Lars On Feb 4, 2013, at 3:10 AM, Lorn Potter <[email protected]> wrote: > +2 > > On 03/02/2013, at 1:45 PM, Martin Jones <[email protected]> wrote: > >> Since the Nokia Brisbane office was closed QML/QtQuick has effectively been >> maintainer-less. Recently Alan has been proactive in pushing QML forward >> and has been very active in the community. He also has a long history >> working in the QML Core team contributing to QML and QtQuick. >> >> Alan is for all intents and purposes acting as maintainer now, so I think we >> should make it official. >> >> Cheers, >> Martin. >> _______________________________________________ >> Development mailing list >> [email protected] >> http://lists.qt-project.org/mailman/listinfo/development > > Lorn Potter > Senior Software Engineer, QtSensors/QtSensorGestures > > > > > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
