Re: [Development] Contributing to the Qt Project behind a hefty firewall and proxy server

On Jul 16, 2012, at 19:16 , ext marius.storm-ol...@nokia.com wrote: On 13/07/2012 10:04, ext marius.storm-ol...@nokia.com wrote: So, I think we'll go ahead and get a port forward setup. It has been done. You can now poin

Re: [Development] Contributing to the Qt Project behind a hefty firewall and proxy server

. Regards, Daniel -Original Message- From: development-bounces+daniel.molkentin=nokia@qt-project.org [mailto:development-bounces+daniel.molkentin=nokia@qt-project.org] On Behalf Of ext Sven Anderson Sent: Monday, July 16, 2012 3:51 PM To: development@qt-project.org Subject: Re: [D

Re: [Development] More CI people?

On Jun 13, 2012, at 22:20 , ext Thiago Macieira wrote: > tst_QDnsLookup was failing again due to changes to gitorious.org's public DNS. We can add a bogus qt-project.org sub-zone for testing purposes that we can fully control if that helps. Daniel ___

Re: [Development] Becoming a Tier 1 platform and the CI System

> It means that the current CI infrastructure is operated by Nokia and > can't have build nodes plugged in from outside of Nokia premises. So, > if you need to manage your own build nodes, there is currently no way to > integrate with the Qt Project CI system. Fixing this is a significant > proj

[Development] QtCS: Calling all Qt/Qt SDK maintainers

Hi, on QtCS, we will have a session on Qt and Qt SDK packaging. The exact details are can be found at http://qt-project.org/groups/qt-contributors-summit-2012/wiki/Packaging-Qt. If you want to attend or have any addition to the program, feel free to amend the wiki page. If you have questions. a

Re: [Development] Choosing a new MinGW for Qt/Qt Creator/Qt SDK

On Apr 21, 2012, at 01:07 , ext André Pönitz wrote: > This is > >https://bugreports.qt-project.org/browse/QTCREATORBUG-5200 > > > There had been rumours that this was solved in (really) recent gdb > builds like the ones that are intended to be shipped with Creator 2.5. > > In theory, these

[Development] Choosing a new MinGW for Qt/Qt Creator/Qt SDK

Hi Everyone, After several complains from the community that GCC 4.4 shipped with both Creator and the Qt SDK is fairly outdated (and not C++11 compliant), we are going to ship a mingw.org-based GCC 4.6.2 with the next Qt Creator release. Even though we verified that this works with the MinGW 4

Re: [Development] Nominating Girish Ramakrishnan for Approver status

Seconded. On Mar 6, 2012, at 10:06 , ext lars.kn...@nokia.com wrote: > Hi, > > I'd like to nominate Girish for Approver status. He's been around Qt for a > pretty long time, working for Trolltech a couple of years ago, then having > his own consultancy company doing Qt related work and he's now

Re: [Development] [Marketing] GSoC 2012

Hi Guiseppe, (moving to development and CCing marketing, please continue this thread on development) from a Marketing POV, that's a clear yes. We are an Open Source Project, and joining GSOC gives that fact visibility. However, the more important questions are best discussed on the development

Re: [Development] Qt Commercial 4.7.5 is out - how shall we contribute is the best?

On Jan 19, 2012, at 21:58 , ext Thiago Macieira wrote: > By the way, considering what Ossi said in the other email ("4.7 is closed as > far as the qt project is concerned [...] [because] fixes are not being > applied > to 4.7 first"), the Qt project needs to make a decision: > > - reopen the 4

Re: [Development] Qt Commercial 4.7.5 is out - how shall we contribute is the best?

> the thing is that 4.7 is closed as far as the qt project is concerned. > we have cemented this decision (made by qt nokia RM) by creating facts - > fixes are not being applied to 4.7 first, and given the strong > forward-merge-only preference, this cannot be revised without creating > ugliness. >

[Development] wiki login issues fixed

Hi, I just wanted to inform you that we now run the wiki on the native mediawiki crowd authenticator for single sign logon. This fixes QTWEBSITE-326. The following issues are fixed: - https links require logins - impossible to log out from the wiki - different beha