Re: [Development] Merging qtquickcontrols2 into qtdeclarative

[Thiago Macieira]

On Tuesday, 13 July 2021 01:43:58 PDT Oswald Buddenhagen wrote:
> but the point remains that the history that didn't exist along the
> merged mainline would live elsewhere (unless we'd import all branches
> and tags as well - we actually did that in qt creator, and it looks
> kinda weird and confusing).

Right, no branches or tags. Just the secondary history root.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel DPG Cloud Engineering



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

Re: [Development] Merging qtquickcontrols2 into qtdeclarative

[Michal Klocek]

Hi

Please note qtpdf repository was merged into qtwebengine, authors wanted to 
keep all the history so it was kept and git blame works nicely. However, 
qtwebengine git repo is anyway big in size so adding extra ~100 commits did not 
have much impact.

https://codereview.qt-project.org/c/qt/qtwebengine/+/270649

Br

Michal

From: Development  on behalf of Elvis 
Stansvik 
Sent: Tuesday, 13 July 2021 13:23
To: Qt development mailing list 
Subject: Re: [Development] Merging qtquickcontrols2 into qtdeclarative

Den tis 13 juli 2021 kl 10:45 skrev Oswald Buddenhagen
:
>
> >On 12 Jul 2021, at 21:19, Thiago Macieira 
> >wrote:
> >> So a full history import MAY have negligible marginal impact over a
> >> squashed import (.git is compressed).
> >
> that might be the case.
>
> but the point remains that the history that didn't exist along the
> merged mainline would live elsewhere (unless we'd import all branches
> and tags as well - we actually did that in qt creator, and it looks
> kinda weird and confusing).
>
> On Mon, Jul 12, 2021 at 11:22:54PM +0200, Elvis Stansvik wrote:
> >Personally I'm always frustrated when I hit a dead end during git
> >blame.
>
> >Even if the original repo will be kept around, it's an added
> >obstacle.
> >
> a rather small obstacle, given that we have a git-qt-grafts script that
> pretty much completely automates the process (it would actually need a
> bit of a revamp by now).

Yea, I just thought it a good idea to follow Thiago's suggestion to
see what the cost would be to do a full history import. But I may have
misunderstood what is even possible and not.

As an outsider doing a sort of drive-by git blame trying to find the
rationale for something, I may not know about special tooling that Qt
has.

But yes, you folks who work day to day on Qt should decide. Just
wanted to chime in with my opinion.

>
> >And at some point, I'm sure it will no longer be available.
> >
> we keep around all repos. the remote may just need an adjustment to
> point to {graveyard}/.

Alright, that's good. In the project I was digging through the other
week, the commit that added the code didn't even say where it came
from, just something like "Code moved from old repo", and after
extensive searching I concluded that "old repo" was no longer online.

Qt being a more serious project, I'm sure you guys will leave a better
commit message and won't start bulldozing over your {graveyard}/ :)

Elvis

>
> (speaking of which, it might be actually time to do that with qt.git,
> rather than only renaming it.)
> ___
> 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

Re: [Development] Merging qtquickcontrols2 into qtdeclarative

[Elvis Stansvik]

Den tis 13 juli 2021 kl 10:45 skrev Oswald Buddenhagen
:
>
> >On 12 Jul 2021, at 21:19, Thiago Macieira 
> >wrote:
> >> So a full history import MAY have negligible marginal impact over a
> >> squashed import (.git is compressed).
> >
> that might be the case.
>
> but the point remains that the history that didn't exist along the
> merged mainline would live elsewhere (unless we'd import all branches
> and tags as well - we actually did that in qt creator, and it looks
> kinda weird and confusing).
>
> On Mon, Jul 12, 2021 at 11:22:54PM +0200, Elvis Stansvik wrote:
> >Personally I'm always frustrated when I hit a dead end during git
> >blame.
>
> >Even if the original repo will be kept around, it's an added
> >obstacle.
> >
> a rather small obstacle, given that we have a git-qt-grafts script that
> pretty much completely automates the process (it would actually need a
> bit of a revamp by now).

Yea, I just thought it a good idea to follow Thiago's suggestion to
see what the cost would be to do a full history import. But I may have
misunderstood what is even possible and not.

As an outsider doing a sort of drive-by git blame trying to find the
rationale for something, I may not know about special tooling that Qt
has.

But yes, you folks who work day to day on Qt should decide. Just
wanted to chime in with my opinion.

>
> >And at some point, I'm sure it will no longer be available.
> >
> we keep around all repos. the remote may just need an adjustment to
> point to {graveyard}/.

Alright, that's good. In the project I was digging through the other
week, the commit that added the code didn't even say where it came
from, just something like "Code moved from old repo", and after
extensive searching I concluded that "old repo" was no longer online.

Qt being a more serious project, I'm sure you guys will leave a better
commit message and won't start bulldozing over your {graveyard}/ :)

Elvis

>
> (speaking of which, it might be actually time to do that with qt.git,
> rather than only renaming it.)
> ___
> 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

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

[Vladimir Minenko]

I also use Element (on MacOS) since the Qt CS times. Here are some hints from 
my experience. For the Qt CS, I created an account on 
matrix.org and added it to Element. This is a separate 
account, not your KDE account.

Chat channels are called “Rooms” in Element. Searching for Rooms is under Rooms 
-> “+” -> "Explore public rooms”, but the search doesn’t work so well or the 
indexing is not ready for the new mirrored IRC channels yet. I tried to search 
for “qt”, and only the one for Qt Created shows up.

I added channels directly by copy-n-paste from the list in the Cristians’s 
email into the"Explore rooms” field showing up under  "Explore public rooms” , 
e.g. #qt:kde.org . It cannot be found, but you can just hit the 
“join” button and you are done.

I hope this helps!

PS. As a yet another web app, Element eats another 700MB RAM, plus 1.4GB RAM 
for its “renderer" on my mac… 2GB per a web app?… Wow…

—
Vladimir

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

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

[Mitch Curtis]

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
___
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] Merging qtquickcontrols2 into qtdeclarative

[Oswald Buddenhagen]

On 12 Jul 2021, at 21:19, Thiago Macieira  
wrote:
So a full history import MAY have negligible marginal impact over a 
squashed import (.git is compressed).



that might be the case.

but the point remains that the history that didn't exist along the 
merged mainline would live elsewhere (unless we'd import all branches 
and tags as well - we actually did that in qt creator, and it looks 
kinda weird and confusing).


On Mon, Jul 12, 2021 at 11:22:54PM +0200, Elvis Stansvik wrote:

Personally I'm always frustrated when I hit a dead end during git
blame.



Even if the original repo will be kept around, it's an added
obstacle.

a rather small obstacle, given that we have a git-qt-grafts script that 
pretty much completely automates the process (it would actually need a 
bit of a revamp by now).



And at some point, I'm sure it will no longer be available.

we keep around all repos. the remote may just need an adjustment to 
point to {graveyard}/.


(speaking of which, it might be actually time to do that with qt.git, 
rather than only renaming it.)

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