Open Governance

Clarifications to Qt Trademark Fair Use Policy

Published Tuesday March 18th, 2014 | by

The use of Qt is on an upward spiral and a great deal of activity is visible with hundreds of Qt-powered products on the market today, scores of Qt learning books and various global Qt activities taking place on a constant basis. We are grateful for the support with pushing Qt forward. In that respect, in order to make sure that the Qt brand is represented consistently and within the terms of the Qt fair use policy and the Qt Trademark policy, I would like to remind you of a few guidelines that need to be followed and clarify a few items to make sure your use of the Qt name and the logo is used correctly.

The use of Qt trademarks is governed by trademark policy, brand guidelines, and trademark license. These are created in order to keep the Qt brand consistent and protect it from misuse. We have recently noticed that in some cases people are not well aware what is allowed and what is prohibited by the trademark policy. We, therefore, would like to clarify the fair use policy a bit.
Read more …


Posted in Community, Licensing, Open Governance, Qt under Open Governance

Published Thursday April 18th, 2013 | by

Right before Qt Developer Days in Berlin, November 2012, we began discussing with the moderators how to bring rest of the Qt Project into Open Governance. This includes the content management system, forums, wikis and so on – everything run as a real community-driven project, as the Qt development itself has been run since October 2011.

Open Governance structure

This figure shows the different roles in the Open Governance structure. A detailed explanation is found on the Web Open Governance page[1].

To make a proper plan, we’ve been running a series of structured IRC meetings, open for all, starting in December last year, continuing through February this year. As the meeting summaries show[2], we started the planning sessions with a discussion on the purpose of the Qt Project Web. Then we continued with discussion and investigation on how maintenance can be done, including co-development of the web content management system. Technical issues, such as improvement with single sign-on and improvements to the wiki-system were discussed. Privacy, internationalization and license issues have also been looked at.

Here are some key topics and actions crystallizing out of these meetings:

  • Single sign-on and a wiki which handles merges (not losing work) Enabling system rights for developing, testing and rolling out new features, including maintenance has to be established.
  • From a roles perspective: several new roles with extended rights are needed, especially giving more access to different admin rights as group management and access to specific web pages.
  • From a process perspective: lazy approval, task prioritization and a conflict resolution board, if needed, in case of (hopefully very few) unresolved conflicts.
  • Also the licensing issue was raised, making the Qt Project Web user agreement clearer, also including licensing to maintain privacy when doing system administration, testing, and development tasks on the site.

Next steps

We are now working on four parallel activities to make Open Governance happen.

  • For CMS development, we are on our way to implement a three-stage infrastructure with a development server and a staging server before production. Today, this is a two-stage setup. We want three stages, which allows the OS to be more flexible in doing the development.
  • We are working at implementing a new access-rights model to allow access to different parts of the CMS.
  • We have identified the need for a “system admin” agreement which is needed before granting extended group admin rights and giving access to fully developed new features, including editing web pages on the site. This agreement is designed to respect privacy laws and simplify the implementation of the planned staged development setup.
  • It seems like the biggest obstacle in the current system is the wiki lacking support for merges when co-writing. Also the single sign on has been identified as one of the key features requested. Given our limited resources, it might be best if these features were to be actively co-developed with Digia together with the community.

There are a couple of other things currently being worked on, such as cleaning up the CSS, simplifying the site navigation, removing old links, and a walk through of the old bugs in the bug-tracker. This work is currently under way.

Since these processes are being run in parallel with the upkeep and maintenance of site from day to day, it’s a little difficult to give an exact time span on when each step will be implemented. We will give progress updates on the Qt Project malinglist[3].

Please have a look at the references below for more information. We welcome your feedback.



Posted in Background, Community, Contributors, cross-platform, Open Governance

First Ten Mirrors Active for Qt Project Downloads

Published Friday April 5th, 2013 | by

I am very pleased that we have already ten mirrors from three continents active for the new download service of the Qt Project, and more are on their way. With the new MirrorBrain based setup is it very easy to become a mirror for Qt – and even more importantly it is seamless for the user to benefit from the nearby mirrors.

We plan to use the new service starting from next week for the upcoming releases of Qt 5.0.2, Qt 5.1 Alpha and others. The old CDN service will be available as backup. When a release is made you can see it appear to page, so everything stays quite similar as before.

If needed, it is easy to see if the file you are planning to download has already been mirrored by viewing the details in conjunction of each file. The mirrors synchronize content with different schedule, so it takes a while for file to become available in all mirrors after it has been released. We are also looking into leveraging torrents as an additional way of downloading files.

For the commercial Qt licensees there are no changes, as the Customer Portal and distribution systems are separate from the open-source downloads.

I hope we continue to receive more mirrors for Qt Project in the coming weeks. If you are interested in mirroring Qt, see instructions how to become a mirror from the Qt Project wiki. Also, feel free to ask you local mirror providers to start mirroring Qt.



Posted in Community, Open Governance, Releases

Qt Project Needs Mirrors for the New Download Service

Published Thursday March 28th, 2013 | by

The Qt Project is currently using a content delivery network based solution for distribution of releases. We have been working to improve distribution of Qt open-source packages and now have the setup available for mirroring. Now we need to get more mirrors before going to production.

The idea is to switch to MirrorBrain based system and away from the current content delivery network based service. The work was started a while ago by Daniel Molkentin and now we have the setup available for mirroring. It is very much similar to what KDE is already using, so for many it is quite familiar. At this point I would like to thank Danimo and others from KDE for all the help provided to enable this.

The system is not yet taken into production use, we need to first have enough mirrors in place. Downloads from the new service work, but the system is not yet up to handle the needed load. Currently we have two mirrors in place, and need more before the new download service can be taken into production use.

The new service is for open-source content only. All the commercial Qt licensees are using a separate system. So it is completely ok for non-profit organizations to become a mirror for Qt Project.

If your organization is willing to become a mirror, please follow the steps in the wiki. Or if you know some organization who already provides mirrors, please ask them to become a mirror for the Qt Project.

We are keenly waiting to get the new download service active as it allows much more flexibility than the current setup. Getting the new system into production is also a prerequisite for providing the new online SDK for the Qt Project.


Posted in Announcements, Community, KDE, Open Governance, Releases

Call for Sponsors | 2013 Qt Contributors Summit

Published Wednesday March 13th, 2013 | by

Qt Contributors' Summit. Photo: Alexandra Leisse

This is the 3rd annual Qt Contributors Summit and it will be the biggest summit to date due to our joined forces with the KDE Akademy conference. More than 500 contributors are expected and it’s solely dependent on sponsorship to succeed.

This will foster interaction, knowledge transfer and technical progress in a highly-productive atmosphere where new and veteran contributors can meet to influence the future direction of Qt. The key benefits of sponsoring the joint Qt CS and KDE Akademy conference are:

  • Meeting key Qt and KDE contributors. There will be 500 upstream and downstream developers and key maintainers, making Qt the top-ranked cross platform framework in developer satisfaction[1].
  • Influence how Qt will be developed in the future. Besides the Qt community, there will be many other free software projects and businesses participating in the joint Qt Contributor Summit and KDE Akademy conference.
  • Be visible. A sponsorship gives you valuable promotional possibilities such as visible advertising, prominent talks and international press coverage.

Digia is a confirmed top platinum sponsor of this year’s combined event and we need even more sponsors to make sure that this year’s event is successful.

Sponsorship Options

This year’s event is providing individuals and companies two ways to sponsor – both which come with many valuable promo benefits:

  1. Single sponsorship: Qt Contributors Summit, 15-16 July
  2. Joint event sponsorship: Qt Contributors Summit and KDE Akademy, 13-19 July

For the Qt Contributor Summit, the sponsorship packages range from Small to XL where sponsors are able to showcase their Qt commitment in front of a knowledgeable, enthusiastic and motivated ecosystem via a variety of sponsor benefits solidifying their stance as active contributors and advocates of the Qt technology.

  1. The single Qt CS sponsorship packages and the combined Qt CS and KDE Akademy sponsorship packages in detail

Practical information

Please contact Knut Yrvin at Digia, Qt or Claudia Rauch at KDE, if you would like to receive more information on sponsorship of the Qt Contributors Summit and/or the KDE Akademy conference. Please contact us by this e-mail form.

1. The report: Cross Platform Tools 2012 by VisionMobile surveying 2,400 developers.

Comments Off

Posted in Community, Contributors, Customers, growth, KDE, Open Governance

Qt Contributors’ Summit Joins Forces with KDE Akademy – July 2013

Published Thursday February 14th, 2013 | by

Just after Digia acquired Qt from Nokia, the KDE community suggested to run the Qt Contributors’ Summit together (Qt CS) with the KDE Akademy conference in Bilbao July 15-16 this summer. The conference will be at the Engineering School of Euskal Herriko Unibertsitatea (EHU; The University of the Basque Country) in Bilbao.

Picture Wall from Qt Contrubutors Day in San Francisco

Lars Knoll, the Qt Chief Maintainer & Digia, Qt  CTO says: “I’m really pleased that we can co-organize Qt Contributors’ Summit with the annual KDE Akademy conference this year in Bilbao, Spain. By close co-operation we are combining community and professionals forces to make both Qt and KDE even better”

More than 500 upstream and downstream developers will participate in this combined event which starts July 13 for both KDE and Qt contributors, and ends July 19. This includes key maintainers of both Qt and KDE projects, and top contributors. It will cover many areas of computing, ranging from core library functionality in Qt and KDE to popular user applications used by hundreds of millions of users, integrated with cloud services. All this in a highly productive atmosphere where we combine forces, exchange knowledge, and meet new contributors.

By co-hosting, KDE and the Qt Project will increase their existing Open Governance collaboration even further. Holding their annual conferences at the same time and the same place will foster interaction, knowledge transfer and technical progress. This in Bilbao, which is the beautiful capital of the province of Biscay in the Basque Country, Spain. The Engineering School and the Bilbao city are putting their forces together helping us in the community to be a great conference and contributors summit in 2013.

The entire budget of this event is funded by sponsors. Even if many are doing a lot of voluntary work, sponsrship are what makes Qt CS and the KDE conference happen. There will be sponsorship packages of all sizes. Info and update on this will be provided soon.

You’ll be invited to this conference by a Qt contributor where also registration details will be provided. Registration of session(s) and other practicalities regarding the Qt CS 2013, is found at the Qt Project Web wiki: Qt Contributors’ Summit 2013. Please don’t hesitate to contact us on the email-list: marketing (at)

Comments Off

Posted in Announcements, Contributors, KDE, Open Governance, Qt

Cross compiling Qt for the masses

Published Friday April 13th, 2012 | by

Cross compiling Qt for particular devices/BSPs can be frustrating when operating from first principles and we are trying to improve the existing configure/qmake build infrastructure in Qt 5, as well as the associated documentation, in order to ease this burden. We are approaching the problem from 2 angles:

  • General cross compilation support
  • Direct target support

The general cross compilation support is being improved by:

  • Reworking the pkg-config logic
  • Introducing the -device flag to configure
  • Introducing the -sysroot flag to configure

The supported targets are documented here:

and as you can see in the Raspberry Pi documentation, we have reduced compilation for this target down to:

./configure -prefix <your prefix> -release
  -device linux-rasp-pi-g++ -make libs
  -device-option CROSS_COMPILE=<your toolchain path>/bin/arm-none-linux-gnueabi-
  -sysroot <your sysroot path>

The resulting build has full (single process) OpenGL ES 2 support and keyboard support for the Raspberry Pi.

There is no need to patch any files as all the relevant changes have been upstreamed into Qt 5 where they can be adequately reviewed and QAed like any other Qt contribution. Needless to say this drastically increases the quality of the code finding its way on to these devices and should drastically improve the user experience when dealing with this kind of hardware for prototyping/productization/recreation. Sunlight is the best disinfectant, and we delight in consuming this dog food.

We heartily invite any (all!) chipset vendors/chipset customers/BSP vendors or interested parties to upstream relevant mkspecs and the associated code changes to Qt, in order to extend the breadth of Qt 5’s out-of-the-box device support. The move to Open Governance has made extending this support increasingly achievable, feasible and convenient and we are very excited about both Qt 5 as a whole and the current rate of development towards embedded (read constrained) Linux platforms.


Posted in Contributors, Embedded, Open Governance, Qt

Launch of the Qt Project imminent…but not on Monday

Published Friday October 14th, 2011 | by

Followers of the Qt Project will know we announced October 17 as our target launch date for the project.

Unfortunately this date is no longer achievable, and we will be delayed by what we expect will be three to four days. A huge amount of hard work has been done, and we are down to a few very important final steps that we are taking a great deal of care with.

In addition, the administrative processes surrounding the creation of the Qt Project hosting entity are very near completion, which we’re glad about :)

We appreciate everyone’s support and patience, and look forward to announcing the official start of the Qt Project very soon.



Posted in Contributors, News, Open Governance

Qt Project

Published Monday September 12th, 2011 | by

Over the past year we have been working with many of you to sort out how we make development of Qt even more inclusive and open. After exploring various options, we are now almost ready to go live with the new solution.

It’s taken a little longer than expected, but we are now very close to move hosting of Qt to a new domain: The domain will be owned by a non-profit foundation whose only purpose is to host the infrastructure for the Qt project. We spent a lot of time collecting feedback from stakeholders who have an interest in the development of Qt, including both companies and open source projects. We wanted to make sure these parties would be happy with the final setup, and of course, willing to participate. While we couldn’t give everybody everything they wanted, we believe we can deliver a good solution.


At launch time, we will have a web site, a wiki, a mailman server, the repositories, and our infrastructure to review and merge changes into Qt ready. The merging infrastructure is based on gerrit, an open source code review system on top of git. We have invested some time and resources to integrate gerrit with the continuous integration system we at Nokia run for Qt. The CI system gives us automated regression testing of changes on our major platforms. As we move forward the goal is to enable any new Qt ports to hook themselves in there.

We will continue to use the current Jira as our bugtracking tool. The Jira server will get transferred to the non-profit foundation, but this will most likely happen a bit after the public launch. In practice this means that will get transferred to We will also establish a number of Qt development related mailing lists at for topics related to Qt development.

Decision making and role of the foundation

I want to make it very clear that the foundation will not steer the project in any way. The foundation is in place only to cover the costs of hosting and run the infrastructure. All technical decisions, as well as decisions about the project direction, will be taken by the community of Contributors, Approvers and Maintainers. For example this means that people in Nokia working on Qt will start working with Qt as an upstream project. Everyone will be using the same infrastructure, including mailing lists and IRC.

The governance model we will use for the Qt project has already been described in detail by Thiago in an earlier blog. Based on feedback we have fine-tuned the model, but it is pretty much the same as described earlier. We are currently finalizing the list of Approvers and Maintainers based on the current de-facto situation in the project. This means naturally that most of them come from Nokia, but it may surprise you that that around 15% of the initial Maintainers do not work for Nokia. We also have quite a few Approvers from companies and the community. While I know that Nokia will continue to invest heavily into Qt for bringing apps to the next billion Nokia users I do hope that more and more people will join the project to broaden the base of Approvers and Maintainers.

As a last point I wanted to talk about one thing that is fixed for the project and not going to go away. To contribute to Qt, you will have to sign a Contribution License Agreement with Nokia. We have put a lot of effort keeping the Qt codebase legally clear and clean, and this attention to detail will continue under the Qt Project. We have been over the last months reviewed the CLA extensively with many stakeholders and believe we have a solution that is as inclusive as possible for all companies and individuals that want to contribute to Qt. The CLA also enables the commercial ecosystem around Qt to continue to thrive and contribute to the project. Further, there are a number of legal obligations from Trolltech and Nokia that have to be taken into account.

Openness continued…

I am excited that we’re now taking another step in a journey that started many years ago. When I joined Trolltech in 2000, Qt was available under the QPL on X11. The same year we changed the license of Qt/X11 to GPL v2. In 2003, we made the Mac port available under GPL as well. Then in 2005, with the release of Qt 4.0, we started releasing all our versions under the GPL. Later the GPL v3 was added as an option. Then in 2009, now under Nokia, we made all of Qt available under the LGPL 2.1.

Opening up development more, as we announced in Jul 2010, was the next logical step and this one is now coming to conclusion. As a person who comes from the open source community, and experienced valuable contributions from the commercial Qt community as well, this is something I’m very happy to see and something I’ve been striving for during all the years I worked at Trolltech and Nokia.

So I’m really looking forward to open governance going live and to work together with all of you on future Qt versions. It’s been quite a journey getting here, but I personally believe that this is only just the start.

We believe the Qt Project will be one of the more transparent and meritocratic open governance models on the market. We are looking forward to the launch in time for Qt Developer days, but no later than October 17th.

You can read some supplementing info in Daniel’s blog


Posted in Contributors, Open Governance, Qt

Qt Contributors' Summit – Last Minute Updates

Published Monday June 13th, 2011 | by

We are neck deep in the final preparations for the Qt Contributors’ Summit and we have a few points to share with you:

First off, thanks to everyone who has listed their topics for our event. It is looking like we are going to get a lot of really great discussions going and we can’t wait to see the sparks fly. A full list can be found on the Qt Developer Network.

Point two: we are full. Really full. I will start off by saying thank you to all who registered before the deadline closed so that we could adequately plan rooms, seating, food, etc. But knowing you folks well enough there would be a number of people we would have to let in after registration has closed due to some arm twisting and eyelash fluttering, etc.

However even with a healthy level of padding, we have been overwhelmed with last-minute requests and are now at the very limit of our capacity.

Why am I saying this? Because we suspect that there might be a few of you who show up on our door with puppy dog eyes looking to slip in at the last minute. I am deeply sorry to say that even the sweetest “puleeese?” won’t help. For the sake of the others attending, we simply can’t let any more people in at this stage.


Also, to make sure there are no sad, disappointed faces at the show: As hard as we tried — and trust us, we tried darned hard — to actually launch open governance at the summit and open the repositories, we have to hang our heads and say we just weren’t able to do it.

Its a complex thing to do, and we want to make sure we do this properly so that we don’t have any painful repercussions down the road. In short, we aren’t going open governance at the show, however we remain completely committed to it and we hope to solve this shortly.

For those that have a special stash of awesome code squirreled away that was going to be unleashed upon us at the summit, fear not! Our existing contribution system is still up and running and we have dedicated the resources necessary to ensure these contributions are quickly reviewed and incorporated into Qt, per the usual process.

Ok, I think thats it. Looking forward to seeing you all in Berlin. Lets make this a great summit!


Posted in News, Open Governance

  1. Pages:
  2. 1
  3. 2