Qt Project Guidelines

This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine. Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean.

The Qt Project is a meritocratic consensus-based community interested in Qt. Anyone who shares that interest can join the community, participate in its decision making processes, and contribute to Qt’s development.

This wiki holds guidelines and documentation regarding code contributions to Qt. For an overview over all different ways to contribute to the Qt Project, please take a look at our home page.

Contributions Things you generally need to know if you want to participate with code contributions. The Qt Governance Model Maintainers Qt Contribution Guidelines Contributing and Reviewing Code Commit Policy Qt Framework Submit Policies Release Management Qt Creator Submit Policies Releases, Roadmap, Branches Plugins QtWebKit		Coding Guidelines Things you need to know before you start writing Qt code. Qt Framework Coding Style and Coding Conventions Qt Creator Coding Style & Conventions API Design Principles Binary Compatibility Workarounds Branch Guidelines Qt Localization Qt in Namespace Transition from Qt 4.x to Qt5 Creating a new module or tool for Qt Project playground Naming guidelines Module repository structure
Tooling Things you need to know before you submit your code. Setting up Gerrit Gerrit Introduction Gerrit Caveats and Hints Early Warning System Tools to help development of your code. IDE debug helpers Quality Engineering Things you need to know to ensure good code quality. Writing Unit Tests Writing Good Tests Qt Quality Gate Criteria CI (Continous Integration): Overview Tested Configurations Reverse Dependency Testing New Unit Test Structure
Related Articles Git Installation Get the source Building Qt 5 from Git Developing and maintaining patches on top of Qt with Git		Community Marketing