On Tue, 7 Jun 2011 19:46:55 ext christian.lo...@hamburg.de wrote: > Stupid mail interface! This should have gone to the list. > > > ----- Ursprüngliche Nachricht ----- > Von: > christian.lo...@hamburg.de > > An: > "Alan Alpert" <alan.alp...@nokia.com> > Cc: > > Gesendet: > Tue, 07 Jun 2011 11:45:30 +0200 > Betreff: > Re: [Opengov] Idea: Qt Community Contributions Module > ----- Ursprüngliche Nachricht ----- > > >Von: > "Alan Alpert" .alp...@nokia.com> > > >On Tue, 7 Jun 2011 18:14:05 ext christian.lo...@hamburg.de<mailto:christian.lo...@hamburg.de> wrote: > >> Hi everybody, > >> > >> Sorry if the following idea was already brought up. I couldn’t find > >> anything about it in the archive. > >> > >> Proposal: > >> I like to propose the creation of a new Qt 5 module: Qt Community > >> Contributions (QtContribs). It should contain classes that are > >> maintained by the “non-Nokia” community and the barrier for new code > >> should be lower. > > > > There shouldn't be a distinction between the "Nokia" and "non-Nokia" > > parts of > > > >the community. That's the whole point of Open Governance IMHO - code is > >judged on merit, not on company affiliation. > > But where should code go that the community sees as valuable addition but > is rejected by the Qt maintainer based on the maintenance status of the > module? > > An example would be a QAnchorLayout class for the Qt Widget module: > http://lists.qt.nokia.com/pipermail/qt5-feedback/2011-June/000389.html
Why does it have to be shipped with Qt? I'd welcome seeing Qt extensions, like you're talking about, organized in one place for use with the shipped Qt. That place could have code with the lower barrier to entry you are talking about. And as long as people can easily find it, they'll be able to use the code (which is the main thing). Perhaps some 'Qt Extensions' section on dev net or gitorious, for projects that are built on Qt and share the same sort of governance but without the strict code quality restrictions (and without shipping with Qt, you'd come to get these if you want them). To apply this to the concrete example: I don't think QAnchorLayout should ship with Qt5 (widgets are *done*), but if someone wrote a good QAnchorLayout then it should be available and findable for the people who want to use it. If everyone uses it and we get community consensus that it should be merged into Qt, that should be easy too. -- Alan Alpert Senior Engineer Nokia, Qt Development Frameworks _______________________________________________ Opengov mailing list Opengov@qt-labs.org http://lists.qt-labs.org/listinfo/opengov
