Re: [Development] Nominating Ville Voutilainen as approver

[Lars Knoll]

Another +1 :)

Cheers,
Lars

> On 27 Feb 2018, at 11:26, Samuel Gaist  wrote:
> 
> +1
> 
> Best regards
> 
> Samuel
> 
>> On 27 Feb 2018, at 10:36, Simon Hausmann  wrote:
>> 
>> Hi,
>> 
>> I would like to nominate Ville as approver. Due to his work in the GCC 
>> project he is certainly experienced with strict code reviews. Based on my 
>> interaction with him I'm convinced that he has successfully demonstrated the 
>> same skill set during code reviews in Qt.
>> 
>> 
>> 
>> Simon
>> ___
>> Development mailing list
>> Development@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
> 
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Fwd: qrandom.cpp build problem: please advise

[Thiago Macieira]

On terça-feira, 27 de fevereiro de 2018 01:11:36 PST Edward Welbourne wrote:
> Apparently it comes from  - at least, that's
> what the test seems to expect and its man-page claims.
> 
> The author of this code may suggest some better solution, once
> his USAish time-zone reaches its daytime,

Originally qrandom.cpp used getrandom(), which is in sys/random.h. Apparently 
I forgot to remove the dependency when I switched to getentropy().

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center



___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Coin maintenance notification

[Konstantin Tokarev]

27.02.2018, 16:42, "Aapo Keskimölö" :
> Coin production was restarted today because it was failing connections to 
> Opennebula after it was restarted.
>
> Changelog:
>
> https://codereview.qt-project.org/#/c/221521/

This is not a public page which everyone here can open, so at least commit 
title should be added to this changelog :)

>
> Ystävällisin terveisin / Kind regards,
>
> Aapo Keskimölö | Software Engineer
>
> aapo.keskim...@qt.io | +358 44 559 2378
>
> ,
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development


-- 
Regards,
Konstantin
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] QHash, QSharedPointer, QScopedPointer, etc absence

[Alexei Fedotov]

Hello guys,

There is a number of C++-style headers which AFAIU just include the
C-style header. I wonder why they do not appear in my workspace. Is
there some magic invocation of the build script which creates them
automatically?

--
Carry a towel
http://dataved.ru/
+7 916 562 8095

[1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
[2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
[3] Start using Apache Openmeetings today, http://openmeetings.apache.org/
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Coin maintenance notification

[Aapo Keskimölö]

Coin production was restarted today because it was failing connections to 
Opennebula after it was restarted.

Changelog:
https://codereview.qt-project.org/#/c/221521/


Ystävällisin terveisin / Kind regards,

Aapo Keskimölö | Software Engineer
aapo.keskim...@qt.io | +358 44 559 
2378


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Fwd: qrandom.cpp build problem: please advise

[Alexei Fedotov]

Hi Edward,
thanks for a quick solution!

The patch worked for me (with  -recheck-all). I defensively used long
 include instead of a short "random.h".
--
Carry a towel
http://dataved.ru/
+7 916 562 8095

[1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
[2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
[3] Start using Apache Openmeetings today, http://openmeetings.apache.org/


On Tue, Feb 27, 2018 at 12:11 PM, Edward Welbourne
 wrote:
> Alexei Fedotov (27 February 2018 09:45)
>> ./configure sets getentropy in qtbase/src/corelib/qtcore-config_p.h to 1,
>
> So the config.tests/unix/getentropy/ test passed.
>
>> but I have no sys/random.h
>
> which that test neglects to #include, so this lack doesn't keep it from 
> failing.
> See if
> https://codereview.qt-project.org/221462
> helps.  (It's not ideal; it should make the test fail for you, though,
> so you'll have the feature turned off, despite being available, so
> you won't hit your compilation problem.)
>
>> Maybe getentropy comes from a modern compiler, not from system headers
>
> Apparently it comes from  - at least, that's
> what the test seems to expect and its man-page claims.
>
> The author of this code may suggest some better solution, once
> his USAish time-zone reaches its daytime,
>
> Eddy.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

[Marco Bubke]

I was ask to provide more info about the crash dump server. It is called 
Socorro:

https://github.com/mozilla-services/socorro




Like you can see it was developed originally for Firefox:

https://crash-stats.mozilla.com/topcrashers/?product=Firefox=58.0.2



There are many statistics about crashes and the stack trace which is very 
helpful

for the developer to prioritize bug reports and fix crashes. We already have 
client support for

that in Qt Creator but we need a server instance where we can send the crash 
dumps.



From: Development  on 
behalf of Marco Bubke 
Sent: Monday, February 26, 2018 6:29:22 PM
To: Edward Welbourne; Robert Loehning; André Pönitz
Cc: development@qt-project.org; Ryein Goddard; qt-crea...@qt-project.org
Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
plugin in Qt Creator

Edward Welbourne:

> When you look into the feature that no-one uses much, you may find that most 
> users
> that do use it have a crash report following close on the heels of their
> use of it; you can make an educated guess at why they don't use it after that.


We have already a crash reporter, which would provide us with that information.

I am pushing this since some time but we need a server installation. Sorry, 
with my

current experience I don't think that we need something much more complicated 
and

fuzzy if we don't get something simple like a crash handler working. And I only

speak about a customization of an already existing server and setting up the VM.

I have that done very long ago but nobody stepped in to productise it.


So I don't believe that we can fly to the stars if we cannot fly to the moon,

but it is much easier to dream about the stars than to go to the moon. 


From: Development  on 
behalf of Edward Welbourne 
Sent: Monday, February 26, 2018 6:06:08 PM
To: Robert Loehning; André Pönitz
Cc: development@qt-project.org; qt-crea...@qt-project.org; Ryein Goddard
Subject: Re: [Development] [Qt-creator] Requesting repository for telemetry 
plugin in Qt Creator

Am 23.02.2018 um 11:54 schrieb Edward Welbourne:
>> The proposed system provides anonymised and presumably aggregated
>> data; so you won't be given, much less asked to evaluate, information
>> about a specific user A doing things at a specific time B; your
>> objection is a straw man.  You'd be getting data on what proportion
>> of users spend what proportions of their time doing which things.  In
>> particular, knowing which bugs bite most users most often might not
>> be entirely useless when it comes to prioritising which bug to fix
>> first.

Robert Loehning (23 February 2018 15:59)
> If many users spend much time doing a "thing", does that mean that
> this is most important to them? Or that it is most fun to do? Or does
> it just mean that the design is so bad that they lose lots of time
> there and can't use it efficiently?

You don't necessarily know - but you do at least know it sees a lot of
use, as distinct from the things that no-one uses.  That, in turn, might
be because the thing doesn't work, or is too confusing; or it might mean
it does a thing no-one feels any need to do.  However, you have now
separated two classes of feature from one another: you won't waste time
asking users why they never use the heavily-used feature; and you won't
assume that users know how to use the feature you know none of them use.

You'll have more information along with just "what proportion use which
features what proportions of the time"; some of this may help you to
distinguish between the various possible explanations.  When you look
into the feature that no-one uses much, you may find that most users
that do use it have a crash report following close on the heels of their
use of it; you can make an educated guess at why they don't use it after
that.  For another feature, users may methodically work their way
through the steps your tutoral for the feature outlined and never touch
it again; it's probagly useless.

You won't be throwing away your other ways of getting information from
users; you can ask them, in all the usual ways, what they like best and
what ticks them off about each feature.  That's quite likely to
distinguish, among the ones that are commonly used, the ones that are
fun from the ones that are time-consuming pain points.

Data on how your users use your product can contribute to your
understanding of what questions to ask your users and what work to
prioritise.  Like all data, of course, you have to use it intelligently
to get actionable information out of it; the possibility that you might
misunderstand it doesn't mean it's worthless; it *supplements* the other
sources of 

Re: [Development] Nominating Ville Voutilainen as approver

[Samuel Gaist]

+1

Best regards

Samuel

> On 27 Feb 2018, at 10:36, Simon Hausmann  wrote:
> 
> Hi,
> 
> I would like to nominate Ville as approver. Due to his work in the GCC 
> project he is certainly experienced with strict code reviews. Based on my 
> interaction with him I'm convinced that he has successfully demonstrated the 
> same skill set during code reviews in Qt.
> 
> 
> 
> Simon
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development



signature.asc
Description: Message signed with OpenPGP
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Ville Voutilainen as approver

[Sean Harmer]

+1

Cheers,

Sean

On 27/02/2018 09:36, Simon Hausmann wrote:

Hi,


I would like to nominate Ville as approver. Due to his work in the GCC 
project he is certainly experienced with strict code reviews. Based on 
my interaction with him I'm convinced that he has successfully 
demonstrated the same skill set during code reviews in Qt.





Simon



___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development



--
Dr Sean Harmer | sean.har...@kdab.com | Managing Director UK
KDAB (UK) Ltd, a KDAB Group company
Tel. +44 (0)1625 809908; Sweden (HQ) +46-563-540090
Mobile: +44 (0)7545 140604
KDAB - Qt Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Ville Voutilainen as approver

[Martins , Sérgio]

+1

On 2018-02-27 09:36, Simon Hausmann wrote:

Hi,


I would like to nominate Ville as approver. Due to his work in the GCC
project he is certainly experienced with strict code reviews. Based on
my interaction with him I'm convinced that he has successfully
demonstrated the same skill set during code reviews in Qt.




Simon

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


--
Sérgio Martins | sergio.mart...@kdab.com | Senior Software Engineer
Klarälvdalens Datakonsult AB, a KDAB Group company
Tel: Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
KDAB - The Qt, C++ and OpenGL Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Ville Voutilainen as approver

[Shawn Rutledge]

+1

> On 27 Feb 2018, at 10:36, Simon Hausmann  wrote:
> 
> Hi,
> 
> I would like to nominate Ville as approver. Due to his work in the GCC 
> project he is certainly experienced with strict code reviews. Based on my 
> interaction with him I'm convinced that he has successfully demonstrated the 
> same skill set during code reviews in Qt.
> 
> 
> 
> Simon
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Ville Voutilainen as approver

[Frederik Gladhorn]

+1 he's also getting his hands dirty with flaky tests and making things work in 
general :-)

Cheers,
Frederik



From: Simon Hausmann
Sent: Tuesday, February 27, 10:36
Subject: [Development] Nominating Ville Voutilainen as approver
To: development@qt-project.org


Hi,

I would like to nominate Ville as approver. Due to his work in the GCC project 
he is certainly experienced with strict code reviews. Based on my interaction 
with him I'm convinced that he has successfully demonstrated the same skill set 
during code reviews in Qt.



Simon


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Nominating Ville Voutilainen as approver

[Edward Welbourne]

Simon Hausmann (27 February 2018 10:36)
> I would like to nominate Ville as approver.

+1 (full disclosure: the three of us all work for TQtC)

Eddy.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Nominating Ville Voutilainen as approver

[Simon Hausmann]

Hi,


I would like to nominate Ville as approver. Due to his work in the GCC project 
he is certainly experienced with strict code reviews. Based on my interaction 
with him I'm convinced that he has successfully demonstrated the same skill set 
during code reviews in Qt.




Simon
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Fwd: qrandom.cpp build problem: please advise

[Edward Welbourne]

Alexei Fedotov (27 February 2018 09:45)
> ./configure sets getentropy in qtbase/src/corelib/qtcore-config_p.h to 1,

So the config.tests/unix/getentropy/ test passed.

> but I have no sys/random.h

which that test neglects to #include, so this lack doesn't keep it from failing.
See if
https://codereview.qt-project.org/221462
helps.  (It's not ideal; it should make the test fail for you, though,
so you'll have the feature turned off, despite being available, so
you won't hit your compilation problem.)

> Maybe getentropy comes from a modern compiler, not from system headers

Apparently it comes from  - at least, that's
what the test seems to expect and its man-page claims.

The author of this code may suggest some better solution, once
his USAish time-zone reaches its daytime,

Eddy.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Fwd: qrandom.cpp build problem: please advise

[Alexei Fedotov]

Hi folks,

qtbase/src/corelib/global/qrandom.cpp has the following code

#if QT_CONFIG(getentropy)
#  include 
#elif !defined(Q_OS_BSD4) && !defined(Q_OS_WIN)
#  include "qdeadlinetimer.h"
#  include "qhashfunctions.h"

#  if QT_CONFIG(getauxval)
#include 
#  endif
#endif // !QT_CONFIG(getentropy)

./configure sets getentropy in qtbase/src/corelib/qtcore-config_p.h to
1, but I have no sys/random.h
Maybe getentropy comes from a modern compiler, not from system headers
So the build fails. I wonder if this is a bug.

--
Carry a towel
http://dataved.ru/
+7 916 562 8095

[1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/
[2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings
[3] Start using Apache Openmeetings today, http://openmeetings.apache.org/
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development