Improve the Qt Contribution Process
Development of Qt has changed significantly in recent years. From mainly being developed in-house, it’s now a full fledge open source project with open governance. When doing such major changes it’s impossible to do everything well. To keep on making Qt with excellent quality and usability, the Qt contribution process should be improved. This page summarize suggestions for contribution process improvements.
- Better documentation on porting Qt to a new platform. Using Qt Lighthouse porting is easier, but it’s still an expert challenge to adapt to a new operating system or platform. Having a migration overview, an architectural guidance, some experiences, would be really appreciated. The notes from the round table on porting challenges between Qt4 and Qt5 [wiki.qt-project.org] explains it.
- A Qt module activity overview inspired by Canonicals Launchpad [launchpad.net] will address the need for an overview of the Qt Project. New contributors might have to be an detective getting an overview of different activeties, status, blogs and contributors. Aggregating module data from Qt commits, e-mail lists and relevant blog posts on a status page will help new and more experience contributors to save time and effort. Knut Yrvin has suggested this, rallying for support.
- Managing Qt add-ons. Cornelius Schumacher have suggested a repository automation for Qt add-ons, making it really easy to use complementary libraries. Schumacker labelled this as “CPAN for Qt”: a website listing available Qt-based libraries, making it easier for developers to find useful libs and for library developers to promote their work. It’s a really interesting project which can help fostering an ecosystem of Qt add-ons. Cornelius is rallying for support. There is already a first start as inqlude.org [inqlude.org].