+1 from me as well. Alan has an excellent overview on everything going on in this module and is still actively following every aspect of its development. I also agree with Lars that we eventually will need to break this beast into smaller more manageable parts as its scope will only continue to grow in the future.
Jens On Feb 5, 2013, at 9:02 AM, Sletta Gunnar <[email protected]> wrote: > +1 > > Alan has done a lot of good stuff for QML so far. Looking forward to more > good stuff coming :) > > cheers, > GUnnar > > On Feb 4, 2013, at 6:28 PM, Alan Alpert <[email protected]> wrote: > >> On Mon, Feb 4, 2013 at 6:19 AM, Knoll Lars <[email protected]> wrote: >>> 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. >> >> Agreed, QtQml and QtQuick are both separate modules that are full >> 'module' sized. As development ramps back up I hope we can find at >> least one maintainer per module (which is more important than >> maintainers 'per repository'). >> >>> 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? >> >> Yes, I'm willing to take that role. As you might have noticed, a >> significant part of my day job is working on QML already and my >> manager is supportive of my spending more time on it to fulfill the >> maintainer duties. >> >> -- >> Alan Alpert >> _______________________________________________ >> 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 _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
