Re: [Development] New survey roll-out on doc.qt.io

[Cristián Maureira-Fredes via Development]

On 02/05/2024 4:57 PM, Florian Bruhin wrote:

Hey,


Thanks for the information,

it took me a while to notice it was a banner,
so for anyone wondering, here's the direct link:
https://www.surveymonkey.com/r/M59K58P


Note the banner has the current page name as an URL parameter, which
presumably gets stored alongside with the survey responses.

Without that context, half of questions in there don't make sense:

- "Did you find the information you were looking for on this page?"
- "What information were you looking for on this page?"
- "How understandable did you find the content on this page?"

Florian


Hey Florian! :)

You are right!
then I guess I failed to get the real message of the original
announcement, which I presume it was:

"Each page under doc.qt.io will have a survey banner
at the bottom of the page. This will help us to gather feedback
and improve the weak pages/sections that we currently
have online.

If you believe one of the many pages you are visiting
is lacking context, or could be improved, feel free
to click on the banner at the bottom of the page
and share your thoughts."

Which in that case, the web parameter makes more sense,
otherwise, as you mentioned it, some questions will not
be useful.





Cheers

On 5/2/24 2:58 PM, Safiyyah Moosa via Development wrote:

Hi All

The Documentation team has launched a new survey on doc.qt.io. Help us
to improve our documentation by filling out the survey and letting us
know your thoughts!

Kind Regards,
Safiyyah Moosa


Kind Regards,

Safiyyah Moosa

Bsc Electronic Engineering

Documentation Engineer

Qt Group
Sandakerveien 116
0484 Oslo
Norway

_safiyyah.moosa@qt.io_

+47 47794451

_www.qt.io <https://www.qt.io>_

https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/Qt-Group-logo-black.png
 <https://www.qt.io/>
https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/facebook-x2-right_2023-03-01-095511_zhlr.png
 <https://www.facebook.com/qt/>
https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/twitter-x2.png 
<https://twitter.com/qtproject> 
https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/linkedin-x2.png 
<https://www.linkedin.com/company/qtgroup/>
https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/youtube-x2.png 
<https://www.youtube.com/QtStudios>




--
Dr. Cristian Maureira-Fredes
Senior R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development



--
Dr. Cristián Maureira-Fredes
Senior R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] New survey roll-out on doc.qt.io

[Cristián Maureira-Fredes via Development]

Thanks for the information,

it took me a while to notice it was a banner,
so for anyone wondering, here's the direct link:
https://www.surveymonkey.com/r/M59K58P

Cheers

On 5/2/24 2:58 PM, Safiyyah Moosa via Development wrote:

Hi All

The Documentation team has launched a new survey on doc.qt.io. Help us 
to improve our documentation by filling out the survey and letting us 
know your thoughts!


Kind Regards,
Safiyyah Moosa


Kind Regards,

Safiyyah Moosa

Bsc Electronic Engineering

Documentation Engineer

Qt Group
Sandakerveien 116
0484 Oslo
Norway

_safiyyah.moosa@qt.io_

+47 47794451

_www.qt.io _

https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/Qt-Group-logo-black.png
 
https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/facebook-x2-right_2023-03-01-095511_zhlr.png
 
https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/twitter-x2.png 
 
https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/linkedin-x2.png 

https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/youtube-x2.png 





--
Dr. Cristian Maureira-Fredes
Senior R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Adrian Herrmann as approver for the Qt project

[Cristián Maureira-Fredes via Development]

On 8/22/23 09:35, Shyamnath Premnadh via Development wrote:

Hi All,

I would like to nominate Adrian Herrmann for approver rights to the Qt 
project.


Adrian has been working on the Qt for Python project for more 
than a year now, and has made significant contributions to bug fixing, 
QtAsyncio (enables interoperability between Python's asyncio package and 
Qt) etc. I trust Adrian's judgment in review and approving changes.


Changes where he is the author: 
https://codereview.qt-project.org/q/owner:adrian.herrmann%2540qt.io 
<https://codereview.qt-project.org/q/owner:adrian.herrmann%2540qt.io>
Changes where he commented/voted on: 
https://codereview.qt-project.org/q/commentby:adrian.herrmann%2540qt.io 
<https://codereview.qt-project.org/q/commentby:adrian.herrmann%2540qt.io>


Regards,
Shyam



+1 from my side,
Adrian has been doing a really good work.

Disclaimer: I'm his line manager, and teammate.

Cheers

--
Dr. Cristián Maureira-Fredes
Senior R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Tatiana Borisova as approver

[Cristián Maureira-Fredes via Development]

+1

Tatiana has been doing a really good job,
helping even other areas that are not her
current main responsibilities :)

Disclaimer: I'm currently Tatiana's Manager.

On 5/23/23 15:39, Alexey Edelev via Development wrote:

Hello everyone,

I would like to nominate Tatiana Borisova for approver rights in the Qt 
project.


Tatiana has been contributing to the Qt Project as a TQtC employee
since 2021, where most of her work went towards to our INTEGRITY support.

She recently joined the Qt Core team,
and has been mainly working on QtGrpc among other contributions
to qtbase, qtdeclarative, and other modules.

You can see her merged changes here:
https://codereview.qt-project.org/q/owner:tatiana.borisova%2540qt.io+is:merged 
<https://codereview.qt-project.org/q/owner:tatiana.borisova%2540qt.io+is:merged>

and her reviews here:
https://codereview.qt-project.org/q/reviewer:tatiana.borisova%2540qt.io 
<https://codereview.qt-project.org/q/reviewer:tatiana.borisova%2540qt.io>


Alexey Edelev

Software Engineer

Qt Group
Erich-Thilo-Str. 10 12489
Berlin, Germany

alexey.ede...@qt.io

www.qt.io <https://www.qt.io>

https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/Qt-Group-logo-black-1.png
 <https://www.qt.io/>
https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/facebook-x2-right.png 
<https://www.facebook.com/qt/>   
https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/twitter-x2.png 
<https://twitter.com/qtproject> 
https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/linkedin-x2.png 
<https://www.linkedin.com/company/qtgroup/>
https://s3.eu-north-1.amazonaws.com/email-signature-tool-leroy/youtube-x2.png 
<https://www.youtube.com/QtStudios>




--
Dr. Cristián Maureira-Fredes
Senior R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Shyamnath Premnadh as approver

[Cristián Maureira-Fredes via Development]

+1 from my side.

Shyam has been helping a lot with the Qt for Python project :)

Cheers!

PS: I'm currently Shyam's teammate and manager.

On 12/5/22 16:46, Alex Blasche via Development wrote:

Hi,


I’d like to nominate Shyamnath Premnadh as an approver for the Qt project.

Shyam has been working in The Qt Company since December 2021. His main area of 
contribution has been the Qt for Python project where he fixes bugs, provides 
documentation and ensures that all new Qt additions find a proper adoption in 
Python. His most recent contributions focus on the deployment support.

His gerrit dashboard links are:

Contributions: 
https://codereview.qt-project.org/q/owner:Shyamnath.Premnadh%2540qt.io
Reviews: 
https://codereview.qt-project.org/q/reviewer:Shyamnath.Premnadh%2540qt.io

Disclosure: I’m Shyam's indirect line manager at The Qt Company in Berlin.

--
Alex
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


--
Dr. Cristián Maureira-Fredes
Senior R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Repository request: playground/qtscrypt

[Cristián Maureira-Fredes]

On 9/2/22 18:04, Oswald Buddenhagen wrote:

On Fri, Sep 02, 2022 at 02:15:15PM +, Volker Hilsheimer wrote:

+1 to go ahead with QtPythonScripting as the name and repository.

how about QtPyScript? that's not so long, and makes the parallel to 
QtScript very obvious.




Hey Ossi,

I'd like that name too, but in June this year
the 'PyScript' project was announced [1]
So it might be confusing for Python users thinking
it's a Qt wrapper or library to develop
Python applications in WebAssembly.

Cheers


[1] https://pyscript.net/

--
Dr. Cristián Maureira-Fredes
Senior R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Repository request: playground/qtscrypt

[Cristián Maureira-Fredes]

On 9/2/22 16:15, Volker Hilsheimer wrote:

On 31 Aug 2022, at 16:47, Cristián Maureira-Fredes 
 wrote:
[snip]


+1 to go ahead with QtPythonScripting as the name and repository.


Work for me as well,
Thanks



Volker



Cheers

--
Dr. Cristián Maureira-Fredes
Senior R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] [EXTERNAL EMAIL] Re: Repository request: playground/qtscrypt

[Cristián Maureira-Fredes]

On 9/1/22 17:37, Mark De Wit wrote:

This sounds like QPyBind11 to me?


Hey Mark,

Not really,
pybind11 is a binding generation system
like the one used for the Qt for Python
project, Shiboken.

The idea of PyBind11 (and Shiboken)
is to expose C++ API to Python users,
meaning that you end up writing a Python script
using modules that originate in C++.

The idea of this project,
as stated in the previous messages,
is to have Python code (as a string)
within your C++ code.

No binding is generated, no wrapper,
is just a usage of the Python interpreter
C-API within C++.


Mark


[snip]


Cheers!

--
Dr. Cristián Maureira-Fredes
Senior R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Repository request: playground/qtscrypt

[Cristián Maureira-Fredes]

On 8/31/22 21:33, Konrad Rosenbaum wrote:

Hi,

On 31/08/2022 20:57, Cristián Maureira-Fredes wrote:



On 8/31/22 19:19, Aleix Pol wrote:

On Wed, Aug 31, 2022 at 4:47 PM Cristián Maureira-Fredes
 wrote:


Hey there,

I would like to request a new repository on codereview.qt-project.org

Name and description: qtscrypt - Script C++ with Python
Responsible person: Cristián Maureira-Fredes
(cristian.maureira-fre...@qt.io)
Desired repository name: playground/qtscrypt
URL of existing code: https://git.qt.io/crmaurei/qtscrypt

Thanks


Won't this be confusing? We have had QtScript for the longest time and
it looks like a typo.


thanks for the comments.

I was under the impression that changing the 'i' for a 'y'
from P'y'thon was not confusing, because it was already
mentioned in a couple of talks and nobody mentioned
anything against it.


Even more fun: scrypt is the name of a password encryption algorithm and 
the corresponding library.




I wanted to avoid qtscript-python because it's not really qtscript,
it's just the main idea from it.

Do you have any other name suggestion?
(I really struggled with finding a name)


QtPython


Hey Konrad,
too close to 'Qt for Python' IMHO



QtPythonScripting


Could be! even if it's a longer name, it's more descriptive.


QtPythonAPI


Not really a Python API,


 > QtYetAnotherPythonBinding


Jokes aside, I think there is a project
called "PyAnotherSide" :)



QtNowForSomethingCompletelyDifferent

QtBrightSide


Probable copyright issues with the band "The Killers"



QtHesTheMessiah

(SCNR)


Sorry for having completely missed the ball here, but what makes this 
new Python binding worthwhile when there's already PyQt, Qt-for-Python 
and PySide?



This idea, as you can see in the code
is to run Python code within C++ code,
quite different from the bindings, but hey,
maybe an example is more clear.

With QtScrypt (Following the idea of the old QtScript module)

You can have C++ code, and at some point that evaluates Python
code and get some result back, say:

QScryptEngine e;
qDebug() << "something, something" << e.evaluate("[i for i in range(10)]");

and you can get a QVariantList with the numerical values,
same idea with a Python function, like:

# your_file.py
def power_of_two(x):
return x**2

you can call it from C++ like

QScryptModule mod("your_file.py")
QScryptFunction f("power_of_two", );
qDebug() << "power_of_two(4): " << f.call(4);
// you get 16 as a QVariant


So now,
PyQt and PySide
provide bindings Python for the Qt API,
like having:

button = QPushButton("press me!")
button.clicked.connect(some_slot)

on Python files.





Hopefully it's not a QtDeadParrot, I'd prefer a QtHolyGrail... :-P


[I'll see myself out now and do something useful instead, sorry.]


No worries, it's useful to ask things are are unknown to ourselves :)

So, as the original email states, this is for a 'playground' repository,
because I was literally playing with this idea on a Hackathon,
and after presenting it in some talks in Qt conferences/workshops,
some folks thought it was something interesting to play with.



     Konrad



Cheers

--
Dr. Cristián Maureira-Fredes
Senior R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Repository request: playground/qtscrypt

[Cristián Maureira-Fredes]

On 8/31/22 19:19, Aleix Pol wrote:

On Wed, Aug 31, 2022 at 4:47 PM Cristián Maureira-Fredes
 wrote:


Hey there,

I would like to request a new repository on codereview.qt-project.org

Name and description: qtscrypt - Script C++ with Python
Responsible person: Cristián Maureira-Fredes
(cristian.maureira-fre...@qt.io)
Desired repository name: playground/qtscrypt
URL of existing code: https://git.qt.io/crmaurei/qtscrypt

Thanks


Won't this be confusing? We have had QtScript for the longest time and
it looks like a typo.


Hey Aleix,

thanks for the comments.

I was under the impression that changing the 'i' for a 'y'
from P'y'thon was not confusing, because it was already
mentioned in a couple of talks and nobody mentioned
anything against it.

I wanted to avoid qtscript-python because it's not really qtscript,
it's just the main idea from it.

Do you have any other name suggestion?
(I really struggled with finding a name)


"Script C++ with Python" < should this be "Use Python scripts from
C++"? Or is it indeed C++ being scripted?


Sure,
it could also be 'Use Python scripts from C++',
(or "Use Python code from C++")
I just wanted to write something simple
like the fact that is adding some 'scripting flavor'
on top of C++ code, that's why "Script C++ with Python".

Following the Qt documentation, and the wikipedia page
from QtScript, some other options are:

"The QtScrypt module provides classes for making Qt applications 
scriptable with Python"


or

"QtScrypt is a scripting engine that aims to be be part of the Qt 
cross-platform application framework."


I'm open to new suggestions :)


Aleix


In any case, If the name and description are too problematic,
I can continue the development outside the Qt Project,
until the project (and the name/description) are mature
enough that I can request a new repository. Just wanted
to make the code public and accept new contributions
from people that showed a positive response after
the last Qt Contributor Summit [1]

Cheers

[1] https://wiki.qt.io/Qt_Contributors_Summit_2022_-_Program/QtScrypt

--
Dr. Cristián Maureira-Fredes
Senior R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Repository request: playground/qtscrypt

[Cristián Maureira-Fredes]

Hey there,

I would like to request a new repository on codereview.qt-project.org

Name and description: qtscrypt - Script C++ with Python
Responsible person: Cristián Maureira-Fredes 
(cristian.maureira-fre...@qt.io)

Desired repository name: playground/qtscrypt
URL of existing code: https://git.qt.io/crmaurei/qtscrypt

Thanks


--
Dr. Cristian Maureira-Fredes
Senior R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QtCS2022 - Sessions and Timeslots

[Cristián Maureira-Fredes]

On 5/24/22 18:20, Aleix Pol wrote:

Hi Pedro,
I added a session in the wiki (about Qt and Wayland) and I got a message 
that it was in moderation and I still don't see it in there.


Do you know what is happening? Has this happened to others?

Aleix

On Thu, May 19, 2022 at 6:43 PM Pedro Bessa <mailto:pedro.be...@qt.io>> wrote:




Hey Aleix,

seems like there was a conflict,
I fixed it and added it manually,
in case something's not correct,
feel free to edit it ;)

Cheers

--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Sona Kurazyan as maintainer of qt5compat

[Cristián Maureira-Fredes]

Hello,

Forgot to wrap up this discussion :P
but thanks for your comments,
and congratulations Sona for being the
new maintainer of Qt5Compat.

Cheers

On 1/18/22 15:10, Cristián Maureira-Fredes wrote:

Hello,

I would like to nominate Sona as maintainer [1]
for the qt5compat module, which at the moment doesn't
have one. Even if it's a special module we have around
only for Qt6, we need a responsible person in charge of it.

She has been working mainly in qtbase in the last years
and took care of many tasks when the module was created [2].

Due to her contributions in qtbase and other modules [3],
I firmly believe she will manage to maintain it.

Cheers


[1] https://wiki.qt.io/Maintainers#Qt_Maintainers
[2] 
https://codereview.qt-project.org/q/owner:sona.kurazyan%2540qt.io+repo:qt/qt5compat+status:merged 

[3] 
https://codereview.qt-project.org/q/owner:sona.kurazyan%2540qt.io+status:merged 





--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Nominating Sona Kurazyan as maintainer of qt5compat

[Cristián Maureira-Fredes]

Hello,

I would like to nominate Sona as maintainer [1]
for the qt5compat module, which at the moment doesn't
have one. Even if it's a special module we have around
only for Qt6, we need a responsible person in charge of it.

She has been working mainly in qtbase in the last years
and took care of many tasks when the module was created [2].

Due to her contributions in qtbase and other modules [3],
I firmly believe she will manage to maintain it.

Cheers


[1] https://wiki.qt.io/Maintainers#Qt_Maintainers
[2] 
https://codereview.qt-project.org/q/owner:sona.kurazyan%2540qt.io+repo:qt/qt5compat+status:merged
[3] 
https://codereview.qt-project.org/q/owner:sona.kurazyan%2540qt.io+status:merged


--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Hacktoberfest 2021 (Spanish Speaking Event)

[Cristián Maureira-Fredes]

Dear Community,

October is around the corner and with that there is a popular event
called Hacktoberfest [1] that has been around for a couple of years.
In a nutshell, this event is aimed mainly to newcomers, to encourage
them to jump into an Open Source project and perform their first 
contributions.


In the past this event has been linked to Github repositories only,
and this year they are enabling Gitlab, but no Gerrit.
Last year, there was some controversy since many repositories got lots
of spam of people modifying 1 character, only for achieving the goal
(3 pull requests), which was tackled by an extra step for maintainers
to accept a pull request (without merging it) to be a valid change
to achieve the event's goal.


Being close to Spanish speaking tech communities, I will be
participating into a small event which aims to encourage Spanish
speaking newcomers to participate in OSS projects [2], my goal will be
to at least teach the interested people to setup a Qt Account, Gerrit,
and everything else to enable them to get future contributions.

Maybe now you are wondering,
if there is no Gerrit compatibility, what do you want to do about it?

Because we have github mirrors[3],
I would like to personally guide them and help them submit a change
into github, put a label on those changes to "accept them",
but drop a message encourage them to submit the same patch to Gerrit.
This will have no effect in our repositories/code, since the labels live
only at a github level, and also doesn't not imply extra work for
Maintainers nor active developers for the Qt repositories.

Please note that this is no attempt to start a migration to Github,
it's mainly to try to find new contributors into Qt.

Note that Pull Requests cannot be disabled on github repositories
so even if we don't accept contributions through github, we still get
changes time to time, check [4].


Last but not least, if you speak Spanish,
and would like to give me a hand guiding people to "at least"
get started with setting up Gerrit, I will be really grateful.

In previous in-person events when I was participating with PySide,
I managed to get only a couple of people on board, so this year I don't
expect many people participating, but you never know ¯\_ (ツ)_/¯
and if we manage to get at least a couple of new people into submitting
a contribution to Gerrit, I will be satisfied and consider this a victory.

Cheers

[1] https://hacktoberfest.digitalocean.com/
[2] https://hacktoberfestes.dev
[3] https://github.com/qt/
[4] https://github.com/qt/qtbase/pulls

--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Mirror IRC channels on KDE's Matrix Instance

[Cristián Maureira-Fredes]

Hey Mitch,

forgot to add that info! sorry :P

Here is a well documented step-by-step process:
https://community.kde.org/Matrix

In a nutshell it's mainly going to
https://webchat.kde.org/
create an account and then you add that account
to your client.

I also use element on the browser,
and since I had already some servers,
what I did was to select the 'Explore Rooms'
option on the top-left corner (it has a compass icon)
Then you can select the server on the right of the popup
window, where you can 'Add new server'
using your new KDE credentials.

I hope it helps

Cheers!

On 7/13/21 11:57 AM, Mitch Curtis wrote:

Hi Cristián, thanks for setting it up.

I've never used Matrix before - how do I sign in using my KDE identity (I'm 
using the Element client if it makes a difference)? I'm guessing I need to set 
the homeserver to some KDE server?

Cheers.


-Original Message-
From: Development  On Behalf Of
Cristián Maureira-Fredes
Sent: Tuesday, 13 July 2021 10:59 AM
To: development@qt-project.org
Subject: Re: [Development] Mirror IRC channels on KDE's Matrix Instance

Hello,

Just to finalize this thread,
as https://phabricator.kde.org/T14673 states, the following channels are now
bridged:


#qt:kde.org
#qt-cmake:kde.org
#qt-creator:kde.org
#qt-cs:kde.org
#qt-labs:kde.org
#qt-pyside:kde.org
#qt-quick:kde.org
#qt-releases:kde.org
#qt-webengine:kde.org (irc: #qtwebengine)


To share the links to the channels
you can use the following:

https://go.kde.org/matrix/#/#qt-pyside:kde.org

changing 'qt-pyside' for the channel you want to share ;)

A big thanks to the KDE folks that help the process!

Cheers


On 7/6/21 12:37 PM, Cristián Maureira-Fredes wrote:

Hello,

Since nobody refused to this decision, will contact the folks at KDE
to start the process of mirroring the IRC channels into KDE's Matrix
instance.

Thanks everyone!

Cheers

On 6/28/21 12:51 PM, Cristián Maureira-Fredes wrote:

Hello everyone,

Context
---

After the "Improve the contributor experience" session at the past Qt
Contributors Summit, many ideas came out related to an overall
improvement to the contribution experience, mainly focused on new
people joining the Qt Project.

One of the topics was Communication,
from which we (qt project people) discussed together with some KDE
folks and agreed that bringing the Qt and KDE communities closer was
a good idea, mainly based on the good experience KDE has currently on
the platform.

We have a good opportunity to do this via a bridge from our newly
created Libera.chat IRC channels, to KDE's Matrix Instance.

During the QtCS,
we tried this out, and mirrored the #qt-cs IRC channel to Matrix:
https://go.kde.org/matrix/#/#qt-cs:kde.org
and according to the people that participated in the session the
experience was nice, and it might be worth to bridge all the other
#qt-* channels on IRC.

Read more about Matrix: https://matrix.org/ Read more about KDE's
Matrix Instance: https://community.kde.org/Matrix


Implications


If you prefer IRC, it's totally fine, this change would only imply
that you will get more people on IRC to interact with.

If you want to move to Matrix completely, this change will enable you
to stay in touch with folks on the IRC channels.

Permissions work different on Matrix than IRC, but with the current
list of moderators in the #qt- domain we can easily assign
permissions to people on the Matrix channels accordingly.

Let's keep the discussion of other communication platforms outside
this thread, while they might be valid, it's out of the scope of this
proposal.

Question


I would like to ask the Qt Project if you agree or disagree with the
proposal to mirror all the #qt-* channels from Libera.chat to KDE's
Matrix Instance.

If we don't have unresolved disagreements, I'd say we can proceed
with the mirroring Monday next week, but if there are concerns, I
would prefer to address them first.

Cheers







--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Mirror IRC channels on KDE's Matrix Instance

[Cristián Maureira-Fredes]

Hello,

Just to finalize this thread,
as https://phabricator.kde.org/T14673 states,
the following channels are now bridged:


#qt:kde.org
#qt-cmake:kde.org
#qt-creator:kde.org
#qt-cs:kde.org
#qt-labs:kde.org
#qt-pyside:kde.org
#qt-quick:kde.org
#qt-releases:kde.org
#qt-webengine:kde.org (irc: #qtwebengine)


To share the links to the channels
you can use the following:

https://go.kde.org/matrix/#/#qt-pyside:kde.org

changing 'qt-pyside' for the channel you want to share ;)

A big thanks to the KDE folks that help the process!

Cheers


On 7/6/21 12:37 PM, Cristián Maureira-Fredes wrote:

Hello,

Since nobody refused to this decision,
will contact the folks at KDE
to start the process of mirroring
the IRC channels into KDE's Matrix instance.

Thanks everyone!

Cheers

On 6/28/21 12:51 PM, Cristián Maureira-Fredes wrote:

Hello everyone,

Context
---

After the "Improve the contributor experience" session at the past Qt
Contributors Summit, many ideas came out related to an overall
improvement to the contribution experience, mainly focused on new
people joining the Qt Project.

One of the topics was Communication,
from which we (qt project people) discussed together with some KDE folks
and agreed that bringing the Qt and KDE communities closer was a good
idea, mainly based on the good experience KDE has currently on the
platform.

We have a good opportunity to do this via a bridge from our newly
created Libera.chat IRC channels, to KDE's Matrix Instance.

During the QtCS,
we tried this out, and mirrored the #qt-cs IRC channel
to Matrix: https://go.kde.org/matrix/#/#qt-cs:kde.org
and according to the people that participated in the session the
experience was nice, and it might be worth to bridge all the other
#qt-* channels on IRC.

Read more about Matrix: https://matrix.org/
Read more about KDE's Matrix Instance: https://community.kde.org/Matrix


Implications


If you prefer IRC, it's totally fine,
this change would only imply that you will get more people
on IRC to interact with.

If you want to move to Matrix completely, this change will enable
you to stay in touch with folks on the IRC channels.

Permissions work different on Matrix than IRC,
but with the current list of moderators in the #qt- domain
we can easily assign permissions to people on the Matrix
channels accordingly.

Let's keep the discussion of other communication platforms
outside this thread, while they might be valid, it's
out of the scope of this proposal.

Question


I would like to ask the Qt Project if you agree or disagree
with the proposal to mirror all the #qt-* channels from Libera.chat
to KDE's Matrix Instance.

If we don't have unresolved disagreements, I'd say we can
proceed with the mirroring Monday next week, but if there are
concerns, I would prefer to address them first.

Cheers







--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Mirror IRC channels on KDE's Matrix Instance

[Cristián Maureira-Fredes]

Hello,

Since nobody refused to this decision,
will contact the folks at KDE
to start the process of mirroring
the IRC channels into KDE's Matrix instance.

Thanks everyone!

Cheers

On 6/28/21 12:51 PM, Cristián Maureira-Fredes wrote:

Hello everyone,

Context
---

After the "Improve the contributor experience" session at the past Qt
Contributors Summit, many ideas came out related to an overall
improvement to the contribution experience, mainly focused on new
people joining the Qt Project.

One of the topics was Communication,
from which we (qt project people) discussed together with some KDE folks
and agreed that bringing the Qt and KDE communities closer was a good
idea, mainly based on the good experience KDE has currently on the
platform.

We have a good opportunity to do this via a bridge from our newly
created Libera.chat IRC channels, to KDE's Matrix Instance.

During the QtCS,
we tried this out, and mirrored the #qt-cs IRC channel
to Matrix: https://go.kde.org/matrix/#/#qt-cs:kde.org
and according to the people that participated in the session the
experience was nice, and it might be worth to bridge all the other
#qt-* channels on IRC.

Read more about Matrix: https://matrix.org/
Read more about KDE's Matrix Instance: https://community.kde.org/Matrix


Implications


If you prefer IRC, it's totally fine,
this change would only imply that you will get more people
on IRC to interact with.

If you want to move to Matrix completely, this change will enable
you to stay in touch with folks on the IRC channels.

Permissions work different on Matrix than IRC,
but with the current list of moderators in the #qt- domain
we can easily assign permissions to people on the Matrix
channels accordingly.

Let's keep the discussion of other communication platforms
outside this thread, while they might be valid, it's
out of the scope of this proposal.

Question


I would like to ask the Qt Project if you agree or disagree
with the proposal to mirror all the #qt-* channels from Libera.chat
to KDE's Matrix Instance.

If we don't have unresolved disagreements, I'd say we can
proceed with the mirroring Monday next week, but if there are
concerns, I would prefer to address them first.

Cheers





--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Mirror IRC channels on KDE's Matrix Instance

[Cristián Maureira-Fredes]

Hello everyone,

Context
---

After the "Improve the contributor experience" session at the past Qt
Contributors Summit, many ideas came out related to an overall
improvement to the contribution experience, mainly focused on new
people joining the Qt Project.

One of the topics was Communication,
from which we (qt project people) discussed together with some KDE folks
and agreed that bringing the Qt and KDE communities closer was a good
idea, mainly based on the good experience KDE has currently on the
platform.

We have a good opportunity to do this via a bridge from our newly
created Libera.chat IRC channels, to KDE's Matrix Instance.

During the QtCS,
we tried this out, and mirrored the #qt-cs IRC channel
to Matrix: https://go.kde.org/matrix/#/#qt-cs:kde.org
and according to the people that participated in the session the
experience was nice, and it might be worth to bridge all the other
#qt-* channels on IRC.

Read more about Matrix: https://matrix.org/
Read more about KDE's Matrix Instance: https://community.kde.org/Matrix


Implications


If you prefer IRC, it's totally fine,
this change would only imply that you will get more people
on IRC to interact with.

If you want to move to Matrix completely, this change will enable
you to stay in touch with folks on the IRC channels.

Permissions work different on Matrix than IRC,
but with the current list of moderators in the #qt- domain
we can easily assign permissions to people on the Matrix
channels accordingly.

Let's keep the discussion of other communication platforms
outside this thread, while they might be valid, it's
out of the scope of this proposal.

Question


I would like to ask the Qt Project if you agree or disagree
with the proposal to mirror all the #qt-* channels from Libera.chat
to KDE's Matrix Instance.

If we don't have unresolved disagreements, I'd say we can
proceed with the mirroring Monday next week, but if there are
concerns, I would prefer to address them first.

Cheers



--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Ivan Solovev as approver

[Cristián Maureira-Fredes]

+1

I think Ivan has been doing a really good job,
it would be nice to have him as an approver!

Cheers

On 6/15/21 1:17 PM, Alex Blasche wrote:

Hi,

I'd like to nominate Ivan Solovev as an approver for the Qt Project.

Ivan has been working on various parts of the Qt6 port and has regularly 
contributed to QtBase  modules, QtPositioning, QtNfc & other modules. 
Personally, I am particularly thankful for his help in furthering the Qt Bindings 
support in QtPositioning and his review of countless other patches in the same 
domain.

He has authored the following patches:
https://codereview.qt-project.org/q/owner:ivan.solovev%2540qt.io,100
and reviewed the following:
https://codereview.qt-project.org/q/reviewer:ivan.solovev%2540qt.io,100

Since  both our office rooms share one wall I am also thankful for many 
technical discussions who broke the enforced solitude of the corona days :)

--
Alex


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



--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Moving IRC from Freenode to Libera.Chat, voting thread

[Cristián Maureira-Fredes]

On 5/22/21 3:06 AM, Giuseppe D'Angelo via Development wrote:

Hi,

[snip]


+1

--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Changes to Freenode's IRC

[Cristián Maureira-Fredes]

On 5/20/21 8:46 PM, Carl Schwan wrote:

Le jeudi, mai 20, 2021 2:18 PM, Giuseppe D'Angelo via Development 
 a écrit :


[snip]
 Lacking some formal voting infrastructure, how do we take this vote?
 I'd say, KISS: please reply to this email and express your preference.


I believe the best course of action would be to wait a bit until KDE moves
its freenode presence to libera (should happen soon). And then Qt can move
its freenode channels to libera and add Matrix bridging to the new channels
with the KDE-Matrix instance.

People who prefer IRC will still be able to use IRC, people who would like
to use a more modern chat protocol can use Matrix and both will be able to
communicate together using the Matrix bridge.

Currently, there are already some unofficial matrix channels bridged to the Qt
IRC channels (e.g. #_freenode_#qt-labs:kde.org) but making them official,
grouping them into a Matrix Space[1] and encouraging people to join them could
help to make Qt a friendlier project to join.

Cheers,
Carl

[1]: https://matrix.org/blog/2021/05/17/the-matrix-space-beta



Hello,

I completely agree with this argument,
moving Libera seems to be
the first solution to the initial problem,
then we could connect those channels with Matrix
counterparts on the KDE infra.

Why Matrix?
KDE is already using it, and I trust
they also had long lasting discussions to "what do we use next".
If someone don't like it then the person can stay on the IRC channel.

After this, time will tell, if we notice an increase of users
on the matrix, or IRC side, and we can have another discussion.
but at least I feel it's a good plan to follow.

Is there any argument against this plan?
Bridges will be harmless enough to at least give us the option
to try something different, without losing discussions from IRC.

@Giuseppe regarding the consensus, should we do a thread for voting
the movement to libera only? or you think we could agree differently
of doing the move.


--
Story time: The PySide situation

As you can see here: https://wiki.qt.io/Qt_for_Python#Community
the project has many platforms, and some of them are connected,
giving me at least the feeling everyone is happy in their system.

IRC has some activity, but it's connected with a bridge
to Matrix (the default server), and also to Gitter
(if you don't know what's about, it's mainly a web-based chat
system related to github projects, it has been connected to
the old github mirror of the pyside-setup repo).

With the configuration:
Gitter <-> IRC <-> Matrix
most people are happy enough.

We complementary had open a Telegram channel,
that became the most active platform (citation needed, it's my impression.).

We opened a PySide channel on Keybase,
but after all the crypto-stuff, it died out.

--


--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Andreas Buhr as approver

[Cristián Maureira-Fredes]

+1 from my side too,
Andreas has been quite helpful in many areas,
and it would be really beneficial for us to give approval rights.

Disclaimer: we are on the same team.

On 4/29/21 8:20 AM, Paul Wicking wrote:

Hi all,


I’d like to nominate Andreas Buhr as approver for the Qt Project.

Andreas has been working with Qt since he joined the Qt Company as a full-time 
employee in Germany about a year ago. I believe his patches [0] spesk for 
themselves. He has also participated actively in reviewing others’ work [1]. My 
impression is that Andreas holds quality in high regard in production code, 
tests, and in documentation, and that he tirelessly works to further our 
quality in all these areas.

I trust he'll use the approver rights responsibly.

[0] - https://codereview.qt-project.org/q/owner:andreas.buhr%2540qt.io
[1] - https://codereview.qt-project.org/q/reviewer:andreas.buhr%2540qt.io

//! Paul
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development



--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] A face for the Qt Project

[Cristián Maureira-Fredes]

Hello everyone,

Finally the repository is ready:
https://code.qt.io/cgit/www/qtproject.git/

and the redirect is in place,
so now when you visit qt-project.org you will
get to the new page.

More information on:
https://www.qt.io/blog/a-new-face-for-the-qt-project

Thanks for all your comments,
people sent me direct emails with ideas and issues
of the page, so I will try my best to fix them!

Cheers

On 3/18/21 7:38 PM, Cristián Maureira-Fredes wrote:

Dear community,

The Qt Project is a huge effort from many people, and for the same
reason, it's quite interesting to (1) Learn how to contribute and be
part of it, and (2) Analyze the interactions of the many
Qt modules.

For people new to the project, contributing to Qt might be challenging,
but I'm certain we all agree that being clear, and provide all the
information in one place is crucial to at least enable them to do
the first step.

On the other hand, if you have been around for a while,
you know that Thiago's blog has a good set of statistics [1]
that helps a lot to get an overview of the current state of the project.

With these two ideas in mind, it makes sense to use qt-project.org
as the face of the Qt Project, highlighting the two previous points
I described.

I would like to ask the community, if we are in favor of using
the proposal from [2] as qt-project.org.

The goal will be to have this repository under our open governance,
so anyone will be able to suggest changes, as we do in Qt.

The idea will be not to duplicate content from https://qt.io,
but focus on aspects related to contributing to the project.


# About the implementation

The page you can see on [2] was generated with Dash,
a Python module based on Plotly [3], and the data comes from the
meta qt5.git repository, including also the qt-creator and pyside-setup
ones.

The text you see on the left-side cards, comes from local Markdown
files, so also it would be straightforward to edit them.

I will upload the code if the community agrees to go forward,
so then we could be able to create a public repository to keep
this code.

Cheers


[1] https://www.macieira.org/blog/qt-stats/
[2] https://qt-project-org.herokuapp.com
[3] https://dash.plotly.com/



--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] A face for the Qt Project - Repository Request

[Cristián Maureira-Fredes]

On 3/26/21 10:05 AM, Cristián Maureira-Fredes wrote:

Hello,

I haven't get any critical comment regarding
this being a bad idea, so I would like to take your +1s
and continue with the next steps.

I would like to request a new repository:

Name: Qt Project Web
Description: Repository for the qt-project.org website
Responsible persons: Cristián Maureira-Fredes
Repository name: qt/qtproject-web


[snip]


Hello,

Forgot the JIRA task:
https://bugreports.qt.io/browse/QTQAINFRA-4381

Cheers

--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] A face for the Qt Project - Repository Request

[Cristián Maureira-Fredes]

Hello,

I haven't get any critical comment regarding
this being a bad idea, so I would like to take your +1s
and continue with the next steps.

I would like to request a new repository:

Name: Qt Project Web
Description: Repository for the qt-project.org website
Responsible persons: Cristián Maureira-Fredes
Repository name: qt/qtproject-web


Once I can push the code there,
we could solve the deployment and usage of https://qt-project.org

Additionally,
some of you have been highlighting many improvements and
issues with the page, so in case you have more ideas or
found more issues, let's use the QTWEBSITE project on JIRA:

https://bugreports.qt.io/projects/QTWEBSITE

Specially the component called "qt-project.org"

https://bugreports.qt.io/issues/?jql=project%20%3D%20QTWEBSITE%20AND%20component%20%3D%20qt-project.org

In the meantime, I will try to fix some of the issues
you raised, and write down the others on JIRA, so we don't forget.

Thanks for your comments :)

Cheers!


On 3/18/21 7:38 PM, Cristián Maureira-Fredes wrote:

Dear community,

The Qt Project is a huge effort from many people, and for the same
reason, it's quite interesting to (1) Learn how to contribute and be
part of it, and (2) Analyze the interactions of the many
Qt modules.

For people new to the project, contributing to Qt might be challenging,
but I'm certain we all agree that being clear, and provide all the
information in one place is crucial to at least enable them to do
the first step.

On the other hand, if you have been around for a while,
you know that Thiago's blog has a good set of statistics [1]
that helps a lot to get an overview of the current state of the project.

With these two ideas in mind, it makes sense to use qt-project.org
as the face of the Qt Project, highlighting the two previous points
I described.

I would like to ask the community, if we are in favor of using
the proposal from [2] as qt-project.org.

The goal will be to have this repository under our open governance,
so anyone will be able to suggest changes, as we do in Qt.

The idea will be not to duplicate content from https://qt.io,
but focus on aspects related to contributing to the project.


# About the implementation

The page you can see on [2] was generated with Dash,
a Python module based on Plotly [3], and the data comes from the
meta qt5.git repository, including also the qt-creator and pyside-setup
ones.

The text you see on the left-side cards, comes from local Markdown
files, so also it would be straightforward to edit them.

I will upload the code if the community agrees to go forward,
so then we could be able to create a public repository to keep
this code.

Cheers


[1] https://www.macieira.org/blog/qt-stats/
[2] https://qt-project-org.herokuapp.com
[3] https://dash.plotly.com/



--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] A face for the Qt Project

[Cristián Maureira-Fredes]

Dear community,

The Qt Project is a huge effort from many people, and for the same
reason, it's quite interesting to (1) Learn how to contribute and be
part of it, and (2) Analyze the interactions of the many
Qt modules.

For people new to the project, contributing to Qt might be challenging,
but I'm certain we all agree that being clear, and provide all the
information in one place is crucial to at least enable them to do
the first step.

On the other hand, if you have been around for a while,
you know that Thiago's blog has a good set of statistics [1]
that helps a lot to get an overview of the current state of the project.

With these two ideas in mind, it makes sense to use qt-project.org
as the face of the Qt Project, highlighting the two previous points
I described.

I would like to ask the community, if we are in favor of using
the proposal from [2] as qt-project.org.

The goal will be to have this repository under our open governance,
so anyone will be able to suggest changes, as we do in Qt.

The idea will be not to duplicate content from https://qt.io,
but focus on aspects related to contributing to the project.


# About the implementation

The page you can see on [2] was generated with Dash,
a Python module based on Plotly [3], and the data comes from the
meta qt5.git repository, including also the qt-creator and pyside-setup
ones.

The text you see on the left-side cards, comes from local Markdown
files, so also it would be straightforward to edit them.

I will upload the code if the community agrees to go forward,
so then we could be able to create a public repository to keep
this code.

Cheers


[1] https://www.macieira.org/blog/qt-stats/
[2] https://qt-project-org.herokuapp.com
[3] https://dash.plotly.com/

--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Aleix Pol Gonzalez for approver status

[Cristián Maureira-Fredes]

On 2/18/21 7:30 AM, Eskil Abrahamsen Blomfeldt wrote:

Hi all!

I would like to nominate Aleix Pol Gonzalez as an approver for the Qt 
Project.


Aleix has been a contributor to KDE and Qt for many years, touching on 
many different areas of Qt, and has lately been actively involved in Qt 
Wayland to help improve its position on the Linux desktop: 
https://codereview.qt-project.org/q/owner:aleixpol%2540kde.org 
<https://codereview.qt-project.org/q/owner:aleixpol%2540kde.org>




+1



--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Max Goldstein as an approver

[Cristián Maureira-Fredes]

+1

Additionally:
Max managed to solve many issues on the Python+QML integration for Qt6.

Cheers

On 12/14/20 9:13 AM, Ulf Hermann wrote:

Hi,

I would like to nominate Max Goldstein as an approver for the Qt Project.

Max has been contributing to the Qt project for a while now. He wrote 
the qmlformat tool, implemented the JavaScript URL object for QML, and 
contributed to pyside.


Here is the list of his changes on gerrit: 
https://codereview.qt-project.org/q/owner:max.goldstein%2540qt.io


Disclaimer: I'm working in the same area and if we weren't working from 
home we'd share an office.


best regards,
Ulf
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


--
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Qt Contributors Summit 2020

[Cristián Maureira-Fredes]

Hello everyone!

With the current global situation, it will be impossible
to organize a physical event for QtCS2020, so we thought
that having the Contributors Summit online this year
would be a good idea :)

To decide the structure of the event,
we would like to ask for your help by answering the following:

* Which topics will you be interested to *hear* about?
* Which topics will you be interested to *talk* about?

We have setup a wiki page to add this information,
so feel free to jump into it, so we can all gather information
related the main topics for this years' QtCS:

https://wiki.qt.io/Qt_Contributors_Summit_2020

Once we have gather some topics and opinions,  we will roll
a registration form, to setup the event and send invites to join
the talks, and discussions.

Since we need to focus on the discussion due to the fact
that it's an online event, we will be using a special channel
on KDE's Matrix instance, called #qtcs2020
you can find a link to join on the same wiki page.

As always, this event will be free of cost, and focused on development 
aspects of Qt.


Stay tuned for more information,
in the meantime, let's gather some nice topics for our event :D

Cheers


--
Dr. Cristian Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] GitHub Pull requests

[Cristián Maureira-Fredes]

Hello,

On 3/10/20 3:48 PM, Konstantin Tokarev wrote:

I think, lowering barrier of entry at expense of reviewers' convenience should
have its limits


Totally agree,
so we should plan to accept patches from platform and systems
made for code development, like Github :)

, otherwise we may end up accepting contributions from Twitter:)

If Twitter becomes on a code development platform
with pull-requests, reviews, and so on...sure :P


Cheers

--
Dr. Cristian Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] GitHub Pull requests

[Cristián Maureira-Fredes]

Hello Cristian,

On 3/10/20 3:40 PM, Cristian Adam wrote:

What stops us from accepting the contributions via GitHub?

Is it:

 1. The CLA
 2. Qt Account

For the CLA one can simply add an instance of:

https://github.com/cla-assistant/cla-assistant


I think that's a good idea,
in the past I was told that even a written consent accepting
the CLA was enough (please correct me if I'm wrong),
so if we can also include it on the Github
mirror, that will allow us to get more contributions.

The only thing I wonder is CI,
what do you think could be a good workflow?

1)
Pull request accepted, then Patch on Gerrit with the reviewer
as owner and a line crediting the author from Github,
so we can integrate it using COIN?

2) Pull request accepted, run a custom CI on Github
and then merge back into gerrit?

3) others?

Cheers


--
Dr. Cristian Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

[Cristián Maureira-Fredes]

On 2/15/20 3:23 PM, Marc Mutz via Development wrote:
> Hi,
> 
> C++20 will contain new classes with emit() member functions 
> (wg21.link/P0053). 
> 

Hello,

I know this discussion is about C++,
but I just wanted to mention that Signals
in Python are objects, and we rely on the emit method
to emit signals (duh!).


As a C++ programmer,
renaming the emit macro for something else doesn't affect
me, even if we decide to remove it, because I think we can
do fine, so I have no strong feelings.

As a Python programmer,
removing the macro will cause headaches when trying to figure
out how to make Signals work, since looking at some random
Qt/C++ code I will not know what's the proper way of emitting one.
(In case I'm not aware of these conventions)

As a PySide developer,
if we agree to change the name, we can just rename the function
we expose, to qEmit or whatever, but in case the macro gets
removed, we will need to keep the emit() method,
and explain to users that in C++ land this doesn't exists,
which will maybe cause some headaches.

My 3 cents,

Cheers

PS:
More info about signals and slots in PySide:
https://wiki.qt.io/Qt_for_Python_Signals_and_Slots


-- 
Dr. Cristian Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Changes to Qt offering

[Cristián Maureira-Fredes]

On 1/29/20 2:27 PM, Kyle Edwards via Development wrote:
> On Wed, 2020-01-29 at 08:20 +0100, Elvis Stansvik wrote:
>> Just want to add here: Even if CMake is probably the Kitware project
>> with the largest number of users if counting developers, I don't
>> think
>> it's their flagship product. That would be the VTK framework (2500
>> classes, 1 MLoC) and associated libraries/applications (ParaView,
>> CTK,
>> ...). I think Kitware makes most of its money doing
>> consulting/projects using those libraries for
>> medical/defense/research/HPC. CMake just sort of fell out from their
>> development process. So CMake is not the central part to their
>> business strategy I think. I think they also employ quite a big of
>> domain experts in the fields where they consult (i.e. it's not just
>> consulting as "VTK experts").
>>
>> If there's a Kitwarer here please correct me if I'm wrong.
> 
> Kitwarer here. All of our products are BSD-or-similar licensed and free
> to use anonymously if they fit your needs out of the box - no paywalls
> or registration for VTK or CMake downloads. And you are of course free
> to extend/modify them yourself and contribute them (or not) back to
> upstream.
> 
> The money we make is by selling support - if our projects don't quite
> do what you want, or if you don't want to modify them yourself, you can
> pay us to do the work for you. Any of the work that we do on core
> frameworks (like VTK) then gets integrated into the mainline project
> for everyone else to use (assuming the contract is not under NDA or
> other confidentiality requirements.) And yes, we do have domain experts
> who work on complex visualization algorithms for VTK.
> 
> It is true that CMake started as a means to an end to build and ship
> ITK. However, it has since grown into a product of its own, with
> numerous customers buying CMake support from us... including TQtC
> itself as of recent. I would say that VTK is still Kitware's primary
> flagship product, but with ITK, ParaView, and CMake additionally
> serving as secondary flagship products.
> 
> Kyle

Hey Kyle,

thanks for your answer,
out of curiosity, are there some past business models
that failed inside Kitware? or it has been support only since
the beginning?

What I'm trying to find out is that if maybe some aspects of what
you tried, could be similar of what TQtC is trying now,
so we have more information regarding the positive and negative
aspects of such decisions.

Best


-- 
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
https://qt.io
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Changes to Qt offering

[Cristián Maureira-Fredes]

On 1/29/20 2:01 PM, Andras Mantia via Development wrote:
> Hi,
> 
> On Wednesday, January 29, 2020 2:25:40 PM EET Cristián Maureira-Fredes wrote:
>> This is nothing new Giuseppe,
>> people actively using Qt will have Qt accounts because they either
>> use our JIRA, and also Gerrit, son for those people, this should not
>> make such impact on the usage of the Qt account.
> 
> I think Mathias' point was that for *new* developers you will raise the
> barrier. If someone wants to try Qt a mandatory registration is something that
> can scare them away.  People starting to get fed up with such registrations
> everywhere, especially before they can realize if they need that tool or not.
>   Existing users probably have an account anyway, for them it is just extra
> annoyance to remember the password (which is not the case for jira, gerrit,
> etc. as the browsers do that) and *might* cause problems for CI systems.
> 
> Andras
> 
> PS: This is my private opinion, not the opinion of my employer.
> 

Hello Andras,

thanks for clarifying, it might be the case,
but since he also mentioned expert developers,
I answered to that reference.

In any case,
new Qt developers will be able to get the Qt that
their OS provide, for Linux is straightforward,
but for Windows/macOS this might have three solutions (maybe more):
- Using package managers that provide Qt,
- Download and compile Qt by themselves,
- Create an account and use the installer.


Good thing that you replied in any case,
because I really think we should separate the different use cases:

- For people already using Qt, with Qt accounts,
that's not a problem.
- For new users, I listed the options before.

Do you have extra types of users that will be affected by this decision?
I really want to gather this input, so we can really analyse the pros
and cons exposed on this discussion.

Cheers

PS: Yeah, I guess everyone here is expressing their personal opinion,
and not the employer one.



-- 
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
https://qt.io
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Changes to Qt offering

[Cristián Maureira-Fredes]

On 1/29/20 10:36 AM, Giuseppe D'Angelo via Development wrote:
> Il 29/01/20 09:52, Cristián Maureira-Fredes ha scritto:
>>
>> Currently, you can create a Qt Account with your email
>> and a password, when you received the email, you confirm by clicking on
>> the link, and then you can optionally enter your information.
>> First Name and Last Name are required, but then you can enter
>> any information on these fields. (I didn't check the checkbox
>> to receive information).
> 
> Using a fake identity is a violation of the terms of service, and I 
> wouldn't be surprised that it could be seen as a crime in the EU or in 
> the US. Are you seriously suggesting that?

I'm sorry if you got that impression, I was not.
I was just saying that are the same fields as the mailing list.
The phrase was just referring to the fact that the twitter video that 
was shared, was asking for even birthday as a mandatory field.

> 
>> Doing that, now I have access
>> to the future installer, I can manage my Qt downloads, install the
>> binaries, remove components if I will not use and everything else.
>>
>> How different is this process
>> from registering to this mailing list for example?
> 
> This is a logical fallacy. "Name and email is also what you use to 
> register to file your tax returns, why are you so concerned?"
> 
> I'd wager that the ratio of Qt users reading (if not writing) on these 
> mailing lists vs the total of Qt users is somewhere in the 10^-4 order 
> of magnitude. And, the irony is, we're not even using the Qt Account for 
> managing the subscriptions to this very mailing list!

This is nothing new Giuseppe,
people actively using Qt will have Qt accounts because they either
use our JIRA, and also Gerrit, son for those people, this should not 
make such impact on the usage of the Qt account.

> 
>> IIRC I entered my email, my name, and a password, then I got an email,
>> clicked on the link, verified my name again, and then I was welcomed
>> to the mailing list.
>>
>> But sure, the mailing list is not software, but a service
>> to communicate with others.
>> Since the installer is a service that TQtC provides,
>> for me is really not difficult to understand that I will require
>> an account, after all TQtC is responsible of having a working CI
>> that can generate those binaries for your convenience.
>> Sure, this was not there before, but is it really so strange? and rude?
> 
> It is in a world of software-as-a-commodity (and especially UI toolkits 
> as a commodity), as well as in a world which is (finally) more privacy 
> sensitive. People don't want companies to collect their personal data 
> any more "just for the sake of it", but especially, any wall you raise 
> that prevents the installation of your software to be a series of clicks 
> on "next next next finish" simply makes your software much less attractive.
> 
> (Not to mention that, as already pointed out, this could be also solved 
> by allowing some OpenID providers to authenticate an user)

I really think we are having this discussion with different sets of 
people in mind.

> 
> 
>> Regarding the LTS decision, you can take it from another point
>> of view:
>> 5.15 will only have 2 or 3 bug fixing releases, and so will all
>> the LTS versions in the future.
>> Since TQtC has commercial costumers, we will internally fork
>> the latest bug fix release, and will start adding patches on
>> top of that on request of the costumers, but hey! all those
>> patches will be on Gerrit, so if they are important for your work,
>> you can just cherry pick them to your local Qt and re-build.
> 
> Ok, finally some answers here.
> 
> I don't understand this model at all: if in the long run 5.15 is going 
> to be maintained as a private fork, but all the patches to it are going 
> to be public on gerrit, it's going to take approximately 20 minutes for 
> someone to
> * set up a gerrit stream
> * get all the merged patches targeting this "5.15-private" branch
> * cherry pick them on 5.15.x
> * publish the result (5.15.oss-latest) on github or KDE or so
> 
> The net result will be that 5.15 will be forked twice (TQC will have an 
> internal commercial fork, the OSS community a public fork), and that Qt 
> will have lost all 3rd party contributions to 5.15 (cf. Thiago's email).
> 
> Isn't this a lose/lose?
> 
> My 2 c,



-- 
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
https://qt.io
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Changes to Qt offering

[Cristián Maureira-Fredes]

On 1/29/20 9:25 AM, Filippo Cucchetto wrote:
> Qt should find a good balance between licensing costs and investors.
> Taking JetBrains as an example of similar (profitable) company you can 
> see that for a single developer all their tools suite costs 600 euros yearly
> decreasing to 400 after 3 years. I think that's a fair price even for a 
> framework like Qt. Furthermore i think that current LGPL users could be more
> willing to buy a commercial company once a good price for them is 
> available (at that point i would simply turn Qt dual licensing GPL or 
> Commerical period).
> Another point is that a great framework like Qt need some big investors 
> that are willing to use Qt for their ecosystem. We don't have big 
> informations onthis
> area but maybe the partnership with LG or with one or more company in 
> the automotive field can give a stable flow of cash.
> In conclusion a 400 euro per developer/year is a nice spot for 
> converting most LGPL users to Commercial.
> 
> F.
> [snip]

Hey Filippo,

I think that's a really good idea,
Personally I have looked into the JetBrains model before,
just to bring new ways of getting more commercial users
into the Qt ecosystem.

I really want to believe that the new startup price is the beginning
of having ad-hoc pricing for everyone, and hopefully in the future
we can also see "medium-size company prices" or
"freelancer developer licenses", but such decisions cannot be made
at the same time.

Once the new startup pricing is out, the company will analyze if it was
a good move, and evaluate special future offerings, or at least
that's what I would do.

Regarding partnerships, I'm really not an expert, but do you have some
material regarding "pros and cons" of such deals?
Maybe you can point out some examples on this topic?

Best

-- 
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
https://qt.io
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Changes to Qt offering

[Cristián Maureira-Fredes]

On 1/29/20 8:29 AM, Mathias Hasselmann wrote:
> Am 27.01.2020 um 15:34 schrieb Lars Knoll:
>> Hi all,
>> [snip]
>> The second change is that a Qt Account will be in the future required 
>> for binary packages. Source code will continue to be available as 
>> currently. This will simplify distribution and integration with the 
>> Marketplace. In addition, we want open source users to contribute to 
>> Qt or the Qt ecosystem. Doing so is only possible with a valid Qt 
>> Account (Jira, code review and the forums all require a Qt Account).
> 
> Are you really sure that it is a good idea to raise the entry barrier 
> for trying Qt that much? Personally I only register for software that I 
> am conviced I'll keep using. If it requires such registration directly 
> at download or during installation already it doesn't even get 
> downloaded or installed. Such attitude might seem strange in the times 
> of Android, iOS, Windows 10 S, but keep in mind that your customers 
> aren't the typicial computer illiterated that simply accept any nonsense 
> you do to their privacy, you are targeting computer experts.
> 
> BBC Wales just sketched pretty well the rude attitude you are embracing 
> with that change: https://twitter.com/Uehmche/status/1217004373970161664
> 
> Besides both that barrier combined with that change to LTS releases will 
> just teach more people to build and patch Qt from source. Being used to 
> that process, having established that process just largely reduces 
> motivation to pay for Qt.
> 
> Ciao
> Mathias

Hello Mathias,

I understand the video is an exaggeration,
but in any case, there is something I really need to understand:

Currently, you can create a Qt Account with your email
and a password, when you received the email, you confirm by clicking on
the link, and then you can optionally enter your information.
First Name and Last Name are required, but then you can enter
any information on these fields. (I didn't check the checkbox
to receive information).

Doing that, now I have access
to the future installer, I can manage my Qt downloads, install the 
binaries, remove components if I will not use and everything else.

How different is this process
from registering to this mailing list for example?
IIRC I entered my email, my name, and a password, then I got an email,
clicked on the link, verified my name again, and then I was welcomed
to the mailing list.

But sure, the mailing list is not software, but a service
to communicate with others.
Since the installer is a service that TQtC provides,
for me is really not difficult to understand that I will require
an account, after all TQtC is responsible of having a working CI
that can generate those binaries for your convenience.
Sure, this was not there before, but is it really so strange? and rude?



Regarding the LTS decision, you can take it from another point
of view:
5.15 will only have 2 or 3 bug fixing releases, and so will all
the LTS versions in the future.
Since TQtC has commercial costumers, we will internally fork
the latest bug fix release, and will start adding patches on
top of that on request of the costumers, but hey! all those
patches will be on Gerrit, so if they are important for your work,
you can just cherry pick them to your local Qt and re-build.

I think nobody at Qt will be so irresponsible of not notifying
security patches, and I'm certain we will work around this issue,
to maybe distributed in a better way for Open Source users.



I really, really, don't want for some large company to buy Qt,
and start losing the momentum we currently have and more importantly
to lost the opportunity to have full time engineers improving Qt.

Please don't take me wrong,
I was technologically raised in Open Sources communities,
and I have been helping for Open Source initiatives since I
started to code, and I'm pretty sure you also have bast experience
with that, and certainly know how challenging is to survive in the
middle of other commercial-only companies, or how as a company
one need to be responsible for shareholders and being profitable.

Best


-- 
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
https://qt.io
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Changes to Qt offering

[Cristián Maureira-Fredes]

Hello David,

On 1/27/20 11:00 PM, David Edmundson wrote:
>> All security fixes are made available to everyone, for all Qt versions that
>> they affect, provided it's still a supported Qt version (or it was easy to
>> make the fix).
>>
> If we could have that explicitly in writing from TQC, that would mean a lot.

The blog post states:

"We are changing our process in R to push all bug fixes to the main 
development branch first, and then backport selected bug fixes back into 
stable release branches. This process ensures that the latest version of 
Qt will always contain all bug fixes. This process change was discussed 
during the last Qt Contributor Summit – we communicate the exact process 
details when Qt 5.15 will be released. Otherwise, development processes 
and the governance model will not change."

This means that you still have access to all the fixes for 5.15
that happen after 5.15.2-3, since they will be on the dev branch.


> I can easily envision a situation that affects only Qt5.15, but not
> Qt6.0 at which point it's not covered by what has been suggested
> officially so far as there would be nothing to cherry-pick.
> 
> David

If there is a bug on 5.15 and not on 6.0,
a fix will be pushed to the dev branch, then cherry pick to the 
commercial LTS version, but the patch will still be there, so you
can just added to your local Qt version.

The Qt Contributors Summit discussion can be found here too:
https://wiki.qt.io/Qt_Contributors_Summit_2019_-_Branch_Policy


Cheers

-- 
Dr. Cristián Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
https://qt.io
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QtCS2019 Notes: Qt for Python and beyond

[Cristián Maureira-Fredes]

Hello,

As a follow-up,
you can find the notes from the Qt for Python Documentation notes here:

https://wiki.qt.io/Qt_Contributors_Summit_2019_Program/Qt_for_Python_Documentation

Cheers

On 11/21/19 3:06 PM, Maurice Kalinowski wrote:
> Hi,
> 
> Following the notes from the Qt for Python session
> 
>   (snip)
>   

-- 
Dr. Cristian Maureira-Fredes
R Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Technical vision for Qt for Python

[Cristián Maureira-Fredes]

Hello Jason,

I will comment inline.

On 8/19/19 3:52 PM, Jason H wrote:
> I tried PySide 2, and was extremely disappointed that not all the classes are 
> supported. What's worse it PyQt supports the classes that are not supported. 
> Having that kind of errata is devastating to the confidence in a project. 
> Qt6/PySide6 must have parity from day 1.

This is true, we still have missing bindings,
but you skipped the good part of the issue you had:

- You reported a couple of missing classes,
- We verify that's specific case, and we discover it was due to Private 
destructor not supported by our binding generator.
- This led to start fixing this issues on the Qt Multimedia module,
that ended app on PYSIDE-1041 being related to QTBUG-74422 which was
merged on dev

So we are truly addressing all the concerns by our users.


Concerning the missing bindings, we have been publicly listing them
all, and even comparing them with PyQt5:
https://wiki.qt.io/Qt_for_Python_Missing_Bindings

There are many things that make little sense in Python land,
and other classes from which we don't have a use-case, or we are not
aware of how critical for a project could be.

That's why we need your feedback.

> Next, the biggest flaw is lack of Python 3 native event loop integration. A 
> lot of people have codebases Python 3 event loops now, PySide should be 
> seamless from day 1.

It would be really nice to have a proper integration,
but this is a difficult implementation, and not even PyQt5 has it 
natively, that's why at the moment we have an open task from which
you can find two external plugins so interact with the Python event 
loop, asyncqt, and quamash: https://bugreports.qt.io/browse/PYSIDE-769


> I also have to point out that there was a statement made by Lars to make QML 
> [more] strongly typed. I had expected that from the beginning, that Python 
> would be the scripting language of QML, not Javascript[0], just for this 
> reason. Instead, V4 was developed... I would probably execute Qt6 QML as 
> Python code, not Javascript. I've repeatedly called for QML to be a web 
> framework, and I've routinely had that idea shot down. So why involve a web 
> language at all[1][2]? Coincidentally, you will also get that AI stuff Lars 
> also talked about, for free (on the Python side anyway)

I tend to think that technologies should coexist better,
rather than choosing one or another, and since there are so many
things being improve in the QML side, I would expect to see the
goodies from Qt6 first to analyze how we could improve the experience
using Python.
We are always open to people trying new things,
maybe somehow has some ideas of adding Python to the scene,
or even improve the current PySide2/QML interaction.

> Jupiter concerns me. I'm wondering how well we can get Qt to integrate with 
> Jupiter notebooks? Can we get interactive Qt in the notebook? (WASM?)
I got contacted by Jupyter developers, because there is a lot of 
interest to better integrate Qt in their notebooks, but of course,
this is not a straightforward task.
We would love to see how things can change in future releases.

> Finally, I've used PyQt off and on since Qt 3.3 days. I really like Python as 
> a language to use Qt in a rapid prototype development way, but the 
> limitations stated above prevent it from being my default environment.

Since both statements have workarounds and future solutions,
we are looking forward to hear what else is missing and stopping you
to use the module.

Thanks for your comments,
Cheers

> (snip)

> 
> 
> 
>> Sent: Monday, August 19, 2019 at 8:39 AM
>> From: "Cristián Maureira-Fredes" 
>> To: "development@qt-project.org" 
>> Subject: [Development] Technical vision for Qt for Python
> ...
>> It will be really nice to know what do you think,
>> because at the moment we have been mostly community driven,
>> and many aspects from the C++ expertise on this mailing list
>> will help us improving Qt for Python.
>>
>> https://blog.qt.io/blog/2019/08/19/technical-vision-qt-python/
>>
> 

-- 
Dr. Cristian Maureira-Fredes
Software Engineer

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

[Development] Technical vision for Qt for Python

[Cristián Maureira-Fredes]

Hello,

After the general discussion of the vision for Qt6,
we wanted to say a few things regarding Qt for Python.


Even though we are talking about a Python module,
the whole development is C and C++ related, and due to
Python's popularity, we have been getting a lot of attention
on Shiboken, the binding generator that we use to expose
our beloved C++ framework to Python.
That's why I felt motivated to write to the main qt mailing list.

A couple of people here has provided us with really nice feedback
regarding the module, and even related to the integration with
QtCreator. We are really thankful for that.


Since the beginning of the project we have seen it as a
complementary project, and never as a competition to the long-standing
performant C++ counterpart, but most importantly as a really nice way
to extend the Qt project community with a whole new set of users.

As you will read on the blog post, there are a couple of aspects from
the C++ point of view that are really useful, like fast prototyping,
exposing existing C++ projects to Python, or even
extend Qt/C++ application with Python.

It will be really nice to know what do you think,
because at the moment we have been mostly community driven,
and many aspects from the C++ expertise on this mailing list
will help us improving Qt for Python.

https://blog.qt.io/blog/2019/08/19/technical-vision-qt-python/

Cheers

-- 
Dr. Cristian Maureira-Fredes
Software Engineer

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Sona Kurazyan as approver

[Cristián Maureira-Fredes]

+1

On 8/9/19 12:42 PM, Alex Blasche wrote:
> Hi all,
> 
> I'd like to nominate Sona Kurazyan as approver for the Qt Project. Sona 
> ensured the release of QtCoap by bringing it to a releasable state and 
> lately, she has been all over Qt doing major cleanups related to deprecated 
> Qt APIs and Qt 6.
> 
> Here is his list of contributions:
> https://codereview.qt-project.org/q/owner:sona.kurazyan%2540qt.io
> And reviews:
> https://codereview.qt-project.org/q/reviewer:sona.kurazyan%2540qt.io
> 
> Cheers,
> --
> Alex
> ___
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
> 

-- 
Dr. Cristián Maureira-Fredes
Software Engineer

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
https://qt.io
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] Switching from create_changelog.pl to createchangelog for change log generation

[Cristián Maureira-Fredes]

Hello Mitch,

On 4/2/19 11:40 AM, Mitch Curtis wrote:
> Currently change files are generated using create_changelog.pl from qtsdk.git 
> [1]. This works OK, but misses a lot of bug fixes. For example, the 5.12.3 
> release of Qt Quick Controls 2 has a bunch of fixes, but create_changelog.pl 
> still results in the "This release contains only minor code improvements" 
> message:
> 
> https://codereview.qt-project.org/#/c/257810/1//ALL

Totally agree, that perl tool needs a bit of love, and it doesn't fit
all the needs from the different project we have in Qt.

> Simon wrote createchangelog [2], which includes any changes with a Jira task 
> number. To quote what the tool does:
> 
> commit 66f33fecc3b4a2896a4f33a3a7f06fb5cdd36dc8
> Author: Simon Hausmann 
> Date:   Thu Feb 25 16:54:02 2016 +0100
> 
>  Added little helper tool to create an initial changelog template for a 
> module
>  
>  Simply run the binary in the module directory with the correct branch 
> checked
>  out.  The tool will peek at .qmake.conf to figure out the current 
> version and
>  run git tag -l to see what the previous version is.
>  
>  The resulting change log requires manual editing, but it is a start.
>  
>  Change-Id: I975c0d7a74fee8cab2ae6f400972c5dbc73ff367
>  Reviewed-by: Robin Burchell 

I found that we had two tools to achieve the same
a couple of weeks ago, and I again agree that it's better than the perl
option.

> 
> And the README:
> 
>  This little tool faciliates the creation of change log files for Qt 
> modules. It is written in golang and
>  can be built by running
> 
>  go build
> 
>  With the binary in place, you can use it like this:
> 
>  1. Change into a directory that contains a git clone of the module 
> you'd like to create a change log for.
>  2. Make sure you have the release branch checked out that you'd like 
> to create the file for.
>  3. Run the createchangelog tool from there.
>  4. The tool will parse .qmake.conf to determine the version of the 
> upcoming release and it will use "git tag -l" to
> determine the previous release, in order to look through the git 
> commits between the previous release and HEAD.
>  5. The proposed template output of the new change log file is 
> printed to standard output, from which you can redirect
> it to a file and edit it accordingly.
> 
> To show examples of what the tool generates, I've attached its output when 
> run on the 5.12.3 and dev branches of qtquickcontrols2.git.
> 
> So, the end result of switching to this is that it becomes clearer that we 
> are actually fixing (non-trivial) bugs, contrary to what the "only minor code 
> improvements" message says. Yes, it does mean that you will have to edit more 
> stuff, but it's mostly just removing commit message bodies, which are 
> included (if I understand correctly) in order to give more context than would 
> otherwise be available had it just included the commit summary.
> 
> If no one has any serious objections, I'd like for us to start using this to 
> create the draft change file commits as soon as possible.

Here is where I have a couple of issues.

Even though the code is not so complicated or long,
the build process is just a couple of seconds,
but having to build it on the first place is kind of "meh".

It's true that I can just build it once, and then forget about
it and just continue using it, but I'm under the impression the tool
also could evolve a bit more.

Moving around the script to generate changelogs is also something
that needs to be improve, since a command line option is the natural 
solution.

The project parses the .qmake.conf so any project that doesn't have one
will be unable to use it, e.g.: PySide.

I know it's a feature of Go, but this also assumes that
the repositories:
go: finding github.com/eidolon/wordwrap v0.0.0-20161011182207-
go: finding github.com/hashicorp/go-version v1.1.0
go: finding github.com/andygrunwald/go-jira v1.6.0
go: finding github.com/trivago/tgo/tcontainer latest
go: finding github.com/google/go-querystring/query latest
go: finding github.com/fatih/structs v1.1.0
go: finding github.com/pkg/errors v0.8.1
go: finding github.com/google/go-querystring v1.0.0
go: finding github.com/trivago/tgo v1.0.6

will not change their names, or that the users will not remove
their accounts, otherwise we will need to find our workarounds
by not using those modules.

Maybe someone with more "Go knowledge" than my limited
"hello world"-level can see if we can rely purely on the go
standard library?


Since I mentioned that I faced the problem of looking for a
"create change logs" tool, I wrote a simple /kind-of/ equivalent
script in Python to use it on the PySide project:
https://codereview.qt-project.org/#/c/252162/

At the moment does not have the option to specify another repository
because it was an ad-hoc solution for the PySide project,
but my point 

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

[Cristián Maureira-Fredes]

Hello,

so, we agree the Go one (qtqa) is the recommended one?

Time ago, I was directed to this one: 
http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/create_changelog.pl
and ended up suggesting this one as a replacement for the Qt for Python 
project: https://codereview.qt-project.org/#/c/252162/

I understand it is better to focus on one script and improve it so that's why I 
would like to know
which is the preferred option.

Cheers


From: Development  on behalf of Mitch 
Curtis 
Sent: 21 February 2019 11:46
To: Jani Heikkinen; development@qt-project.org
Subject: Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes 
files

> -Original Message-
> From: Jani Heikkinen
> Sent: Thursday, 21 February 2019 11:06 AM
> To: Mitch Curtis ; development@qt-project.org
> Subject: RE: [Development] Maintainers, your action needed: Qt 5.12.2
> changes files
>
> > -Original Message-
> > From: Mitch Curtis 
> > Sent: torstai 21. helmikuuta 2019 11.21
> > To: Mitch Curtis ; Jani Heikkinen
> > ; development@qt-project.org
> > Subject: RE: [Development] Maintainers, your action needed: Qt 5.12.2
> > changes files
> >
> >
> >
> > > -Original Message-
> > > From: Development  On Behalf
> > Of
> > > Mitch Curtis
> > > Sent: Thursday, 21 February 2019 9:33 AM
> > > To: Jani Heikkinen ;
> > > development@qt-project.org
> > > Subject: Re: [Development] Maintainers, your action needed: Qt
> > > 5.12.2 changes files
> > >
> > > > -Original Message-
> > > > From: Development  On
> Behalf
> > > Of
> > > > Jani Heikkinen
> > > > Sent: Thursday, 21 February 2019 9:19 AM
> > > > To: development@qt-project.org
> > > > Subject: [Development] Maintainers, your action needed: Qt 5.12.2
> > > > changes files
> > > >
> > > > Hi,
> > > > Initial ones here: https://codereview.qt-
> > > > project.org/#/q/message:%22Add+changes+file+for+Qt+5.12.2%22,n,z
> > > >
> > > > Please take it over, do needed modifications and get '+2' during
> > > > this
> > week.
> > >
> > > Do we have a script that generates the change logs? I see that
> > > qtbase has entries for bug fixes with the task number:
> > >
> > > http://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.12.1/?h=v5.
> > > 12
> > > .1
> > >
> > > I'd like to get the same for the modules that I maintain. I'm
> > > guessing that one was done manually, but I'd like to try to automate
> > > it (even if it still requires some manual editing afterwards).
> > >
> > > I checked qtrepotools.git but didn't find anything. Simon created
> > > one, but says that it's not the same one in use by the release team:
> > >
> > > http://code.qt.io/cgit/qt/qtqa.git/tree/src/createchangelog
> >
> > Replying to myself to say that this tool works really well, and is
> > very easy to use (especially with
> > https://codereview.qt-project.org/#/c/253973/). Can the initial change logs
> be created with it?
>
> We will test this and use it in coming releases if it works better that 
> current
> one

For what it's worth, the only negative difference I saw was that it 
(createchangelog) generates this:

Qt 5.12.2 is a bug-fix release. It maintains both forward and backward
compatibility (source and binary) with Qt 5.12.1.

whereas the current one generates this:

Qt 5.12.2 is a bug-fix release. It maintains both forward and backward
compatibility (source and binary) with Qt 5.12.0 through 5.12.1.

Doesn't seem that important though?

> br,
> Jani
>
> >
> > > > br,
> > > > Jani Heikkinen
> > > > Release Manager
> > > > ___
> > > > Development mailing list
> > > > Development@qt-project.org
> > > > https://lists.qt-project.org/listinfo/development
> > > ___
> > > Development mailing list
> > > Development@qt-project.org
> > > https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development