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.
Rules and Constraints:
All rules and constraints of a Qt module like binary compatibility,
test coverage, high quality documentation, platform support etc
should also
apply to this module.
Scope and Content:
* New functionality that is out-of-scope for the other existing Qt
modules. Examples might be ORM, Reporting, Charting…
* New or extended functionality for Qt modules with maintenance
status “done”. For example anchor layout for widgets.
The following should not be part of this module:
* New or extended functionality for active Qt modules. It should
not contain code that was rejected by other Qt maintainers.
Opportunities
* Chance for the community to extend “done” Qt modules without
risking stability or taking over maintainership.
* Outreach to currently outside Qt extension communities (libqxt,
KDE, Qwt) to collaborate and get the code shipped with an official Qt
release.
* Possible “staging area” for new functionality before it’s
accepted as new official Qt module
* Possibility for community maintainers to show their skills and
dedication
Risks
* Dumping ground for unmaintained one-time-only contributions
* Focus point for community contribution. Possible neglect of the
other Qt modules.
Thanks for reading! Opinions? Flames?
Christian Loose
_______________________________________________
Opengov mailing list
Opengov@qt-labs.org
http://lists.qt-labs.org/listinfo/opengov
