Re: [Development] Repository Request: qt/licensing

[Stottlemyer, Brett (B.S.)]

On Wednesday, May 23, 2018 9:43 AM Thiago Macieira wrote:
> On Wednesday, 23 May 2018 10:31:17 -03 Kai Koehne wrote:
> > Well, the whole point of the exercise is to allow customers to 
> > configure Qt under commercial terms from git, so any non-shared git module 
> > doesn't help.
>
> You can then make it public, so long as it's clear it's Qt Company, not Qt 
> Project. I object to it showing up anywhere in github.com/qt and > qt- 
> project.org, but other places in qt.io could be acceptable.

Can .pro files test for commercial vs. oss licenses?  If so, and you create a 
non-Qt project repo, couldn't some .pro in qtbase retrieve licheck, like 
QtCreator does here: 
http://code.qt.io/cgit/qt-creator/qt-creator.git/tree/qtcreator.pro#n123?

Is that an acceptable solution?  Seems like it would work here, although I 
think the time stamp generation and commercial licenses would need to be added 
to qtbase (I think).

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

Re: [Development] Repository Request: qt/licensing

[Thiago Macieira]

On Wednesday, 23 May 2018 10:31:17 -03 Kai Koehne wrote:
> > In your internal infra, use a different repository branched off from the
> > public one, containing the licence checker binary and anything else you
> > may need. This repository should never be shared.
> 
> Well, the whole point of the exercise is to allow customers to configure Qt
> under commercial terms from git, so any non-shared git module doesn't help.

You can then make it public, so long as it's clear it's Qt Company, not Qt 
Project. I object to it showing up anywhere in github.com/qt and qt-
project.org, but other places in qt.io could be acceptable.

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



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

Re: [Development] Repository Request: qt/licensing

[Simon Hausmann]

On Mittwoch, 23. Mai 2018 15:31:17 CEST Kai Koehne wrote:
> > -Original Message-
> > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> > project.org] On Behalf Of Thiago Macieira
> > Sent: Tuesday, May 22, 2018 10:21 PM
> > To: development@qt-project.org
> > Subject: Re: [Development] Repository Request: qt/licensing
> > 
> > On Friday, 18 May 2018 18:18:02 -03 Thiago Macieira wrote:
> > > > Just for clarification: The official source packages contain the
> > > > licheck executables already. My aim is that a git checkout and the
> > > > source packages we provide contain the very same content.
> > > 
> > > I understand, but I'm asking you not to.
> > 
> > Here's something that would be acceptable:
> > 
> > Do create the qt/licensing repo but make it empty, or just a README file
> > or
> > whatever is necessary. This repository can live in qt-project.org and be
> > mirrored under github.com/qtproject.
> > 
> > In your internal infra, use a different repository branched off from the
> > public one, containing the licence checker binary and anything else you
> > may need. This repository should never be shared.
> 
> Well, the whole point of the exercise is to allow customers to configure Qt
> under commercial terms from git, so any non-shared git module doesn't help.
> 
> We can also ship licheck binaries independently of the git modules, and ask
> then customers to pass their location e.g. via a configure argument:
> 
>  configure -commercial -licheck /path/to/licheck  ...

Would it perhaps be possible for configure to just look in "well known" 
locations in the system where the online installer can place them (or place a 
file that contains the path to licheck) ?
 
> then all we have to add to qtbase is the .release-timestamp file to mark the
> date of a release.

Can you determine the time of the release from the release tag perhaps? git 
describe can be used to find the "nearest" tag and the tag has a date.
 

Simon


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

Re: [Development] Changing maintainership for Qt Creator modules

[Eike Ziller]

+1.
Both are the de-facto maintainers of that code nowadays :)

> On 23. May 2018, at 15:23, Kai Koehne  wrote:
> 
> Hi,
> 
> I haven't actively worked on Qt Creator since a while, and would therefore 
> like to step down as the maintainer for the Qt Creator modules I'm still 
> listed for in https://wiki.qt.io/Maintainers:
> 
> 
> Debugging & Profiling / QML 
> 
> I propose Ulf Hermann  as replacement.
> 
> 
> Project Management & Targets / QML 
> 
> I propose Thomas Hartmann  as replacement.
> 
> 
> Regards
> 
> Kai
> 
> --
> Kai Koehne, Senior Manager R | The Qt Company
> 
> The Qt Company GmbH, Rudower Chaussee 13, 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
> http://lists.qt-project.org/mailman/listinfo/development

-- 
Eike Ziller
Principal Software Engineer

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
eike.zil...@qt.io
http://qt.io
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
http://lists.qt-project.org/mailman/listinfo/development

[Development] Changing maintainership for Qt Creator modules

[Kai Koehne]

Hi,

I haven't actively worked on Qt Creator since a while, and would therefore like 
to step down as the maintainer for the Qt Creator modules I'm still listed for 
in https://wiki.qt.io/Maintainers:


Debugging & Profiling / QML 

I propose Ulf Hermann  as replacement.


Project Management & Targets / QML 

I propose Thomas Hartmann  as replacement.


Regards

Kai

--
Kai Koehne, Senior Manager R | The Qt Company

The Qt Company GmbH, Rudower Chaussee 13, 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
http://lists.qt-project.org/mailman/listinfo/development

[Development] Could someone help me to change my full name in bugreports.qt.io?

[Boxiang Sun]

Hi,

I am contributing to PySide2. And I set up my account in
https://account.qt.io correctly, which is "Boxiang Sun". But my full name
in https://bugreports.qt.io is not, which is "Alexander Sun". I used the
latter one before. But not for Qt. How can I change my full name in
bugreports? Or is there someone(website manager, maybe?) who can help me to
change my name, please?

Thanks!

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