I agree with Thiago. It doesn't have to be in core. But it needs to be readily 
available. Having it as a Qt Solution was fine for me. 


I am wondering if there shouldn't be a linuxconfig- like GUI interface for Qt 
now that it is going all modular. And have it work like Cygwin's setup. Where 
you can get the binaries, the source, etc. I would love to have a front-end to 
git, for everyone that doesn't want to learn another CVS. Or SVN. Or Perforce. 
Even my techie friends complain about git. (Not that now is the time to 
complain, that was long ago.) But for those of us who rather not need to know 
how to use git, git branches and all that, a GUI would be most helpful.

Anyway back to the subject, the GUI would just turn QtServices availibilty 
on/off with a checkbox.






________________________________
From: Thiago Macieira <[email protected]>
To: [email protected]
Sent: Tuesday, June 7, 2011 6:12 PM
Subject: Re: [Qt5-feedback] TLC for QtService...moving it into Qt5

Em Tuesday, 7 de June de 2011, às 14:10:34, BRM escreveu:
> > Why  does it need to be in QtCore?
> 
> I would put it in QtCore primarily b/c that is where QCoreApplication and
> QApplication live, and it should be as available to everyone as those to
> are. However, I am not deadset on doing so - that is part of the reason for
> this discussion. It could be in a QtService module.
> My primary concern is that it is easily available on all Qt installations as
> a native part of Qt.

Assume that there is a place that makes it easily available to all Qt 
installations and users. Do you need in QtCore for any special reason?

If not, I recommend starting as an outside module. Move to QtCore if it's 
necessary or if too many applications require it.

I've just noticed this below:

> ----- Original Message ----
[snip]
> Thiago,
> 
> As I am looking to enable both commercial licensees and FLOSS users of Qt to
> use this, what is the best licensing route? I noticed that the current
> QtService component is BSD licensed[1]. Do we need to do the same? Or is
> there another route we would need to take?

In order to contribute code to Qt, you need to license it under the 
Contribution License Agreement, which means your code gets released as Open 
Source under the LGPL and it allows Nokia to relicense it to Digia so they can 
have a commercial version.

You don't need to do anything special. Just contribute the code that you write 
yourself. You cannot take code from somewhere else.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

_______________________________________________
Qt5-feedback mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
_______________________________________________
Qt5-feedback mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback

Reply via email to