Difference between revisions of "KDE Core/Platform 11/KDEQtRelationship"

Jump to: navigation, search
(Created page with '= Qt KDE relations = == Us and Them == Respect should go both ways? Tone of messages should be friendly. Offering KDE as playground - less strict, gets feedback, gets real app ...')
 
Line 2: Line 2:
  
 
== Us and Them ==
 
== Us and Them ==
Respect should go both ways? Tone of messages should be friendly.
 
  
Offering KDE as playground - less strict, gets feedback, gets real app exposure
+
We need mutual respect. Lots of personal ties, but always changing. Core people should act as role models for community and users.
  -> more that a Qt labs project
 
  
== Qt and KDE ==
+
== Technical collaboration ==
Qt is cross platform, KDE is not there
 
  
 +
KDE as space for innovation - less strict, gets feedback, gets real app exposure, more than a Qt labs project
  
== KDE plan for QCS ==
+
Qt is cross platform, KDE is not there yet. Qt standards like unit tests, API review, continuous integration are or would also be good KDE standards.
 
 
Make KDE attractive
 
Present KDE vision to Qt people
 
 
 
 
 
Sessions: KDE and Qt communities and working together, what can we learn from each other
 
Code of conduct
 
 
 
Technical: The things that should be merged: KUrl and friends
 
KLocale QLocale
 
Printing
 
Config systems
 
Archive handling
 
 
 
  
 
3rd party libraries
 
3rd party libraries
Line 31: Line 15:
 
Libraries for Qt developers that are not part of Qt  
 
Libraries for Qt developers that are not part of Qt  
 
  - system how to get libraries ?!? ruby gems, cpan
 
  - system how to get libraries ?!? ruby gems, cpan
 
 
The contributor agreement?
 
 
  
 
How do we handle improved KDE stuff that goes into Qt but has a different api?
 
How do we handle improved KDE stuff that goes into Qt but has a different api?
  
 +
== What is attractive for Qt in KDE ==
  
Open Governance
+
* App developers
 +
* KDE is still a great public showcase and large resource of openly available Qt application code.
 +
* KDE is an early adopter, commercial customers are way behind.
 +
* KDE is a good pool for people.
 +
* KDE wants to contribute to Qt.
 +
* KDE cares about Qt. High quality feedback and contributions.
 +
* Example for successful library: QJson
 +
* Rekonq is interesting because it is a real world demo using qt webkit.
 +
* Git is a bonus
  
App developers:
+
== Open Governance ==
  
KDE is still a great public showcase and large resource of Qt example code.
 
KDE is an early adopter, commercial customers are way behind.
 
KDE is a good pool for people.
 
KDE wants to contribute to Qt.
 
KDE cares about Qt. High quality feedback and contributions.
 
  
Example for successful library: QJson
+
Can we convince people to do modularization and clean up for KDE?
  
- modularization is great
+
Get a foot into the door: go for qt creator
  
Rekonq is interesting because it is a real world demo using qt webkit.
+
Can we put cmake projects into qt creator? Make it possible to create KDE applications by default.
  
Git is a bonus
+
What about QML designer
  
Can we convince people to do modularization and clean up for KDE?
+
== KDE plan for QCS ==
Can kdelibs benefit from Qt test infrastructure.
 
  
KDE attitude: complain about blog post
+
Make KDE attractive
 +
Present KDE vision to Qt people
  
  
 +
Sessions: KDE and Qt communities and working together, what can we learn from each other
 +
Code of conduct
  
Buildsystem???
+
Technical: The things that should be merged: KUrl and friends
 +
KLocale QLocale
 +
Printing
 +
Config systems
 +
Archive handling
  
  
Can we put cmake projects into qt creator.
 
  
Get a foot into the door: go for qt creator
+
The contributor agreement?
What about QML designer
 

Revision as of 21:51, 2 June 2011

Qt KDE relations

Us and Them

We need mutual respect. Lots of personal ties, but always changing. Core people should act as role models for community and users.

Technical collaboration

KDE as space for innovation - less strict, gets feedback, gets real app exposure, more than a Qt labs project

Qt is cross platform, KDE is not there yet. Qt standards like unit tests, API review, continuous integration are or would also be good KDE standards.

3rd party libraries independent Qt libraries Libraries for Qt developers that are not part of Qt

- system how to get libraries ?!? ruby gems, cpan

How do we handle improved KDE stuff that goes into Qt but has a different api?

What is attractive for Qt in KDE

  • App developers
  • KDE is still a great public showcase and large resource of openly available Qt application code.
  • KDE is an early adopter, commercial customers are way behind.
  • KDE is a good pool for people.
  • KDE wants to contribute to Qt.
  • KDE cares about Qt. High quality feedback and contributions.
  • Example for successful library: QJson
  • Rekonq is interesting because it is a real world demo using qt webkit.
  • Git is a bonus

Open Governance

Can we convince people to do modularization and clean up for KDE?

Get a foot into the door: go for qt creator

Can we put cmake projects into qt creator? Make it possible to create KDE applications by default.

What about QML designer

KDE plan for QCS

Make KDE attractive Present KDE vision to Qt people


Sessions: KDE and Qt communities and working together, what can we learn from each other Code of conduct

Technical: The things that should be merged: KUrl and friends KLocale QLocale Printing Config systems Archive handling


The contributor agreement?


Content is available under Creative Commons License SA 4.0 unless otherwise noted.