KDE Core/Platform 11/KDEQtRelationship: Difference between revisions
No edit summary |
No edit summary |
||
| (5 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{warning|This page contains rough working notes from discussion sessions at Platform 11, the contents of which may not accurately reflect any decisions made. Please do not infer anything from these notes, official summaries of the conclusions reached will be made available for discussion as soon as possible.}} | |||
What is the relationship between the Qt and KDE communities, in particular on a non-technical level? What can we do to improve it. What are the topics to address, and how do we do that? | What is the relationship between the Qt and KDE communities, in particular on a non-technical level? What can we do to improve it. What are the topics to address, and how do we do that? | ||
== Us and Them == | == Us and Them == | ||
There still is a us and them mentality. Communities could be closer together. There are a lot of common ideas. Lots of personal ties, but always changing. We need mutual respect. Core people should act as role models for community and users. | |||
== Technical collaboration == | == Technical collaboration == | ||
| Line 11: | Line 13: | ||
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. | 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. | ||
KDE is part of ecosystem of independent Qt libraries that are not part of Qt. | |||
independent Qt libraries | |||
System how to get libraries, similar to ruby gems, cpan? | |||
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? | ||
| Line 32: | Line 33: | ||
== Open Governance == | == Open Governance == | ||
Can we convince people to help with modularization and clean up for KDE? | |||
Can we convince people to | |||
Get a foot into the door: go for qt creator | Get a foot into the door: go for qt creator | ||
| Line 39: | Line 39: | ||
Can we put cmake projects into qt creator? Make it possible to create KDE applications by default. | Can we put cmake projects into qt creator? Make it possible to create KDE applications by default. | ||
What about QML designer | What about QML designer? | ||
== KDE plan for QCS == | == KDE plan for QCS == | ||
''This needs input from the outcome of other groups and topics discussed at the platform sprint. Do another breakout session towards the end of the sprint with the people who will be at the contributors' summit.'' | |||
Present KDE vision to Qt people | |||
=== Goals === | |||
* Show KDE's attractiveness | |||
* Present KDE vision to Qt people | |||
=== General sessions === | |||
* KDE and Qt communities and working together, what can we learn from each other (community processes, e.g. code of conduct) (Frederik, Cornelius) | |||
=== Technical sessions === | |||
* The things that should be merged: KUrl and friends | |||
KLocale QLocale | * KLocale QLocale | ||
Printing | * Printing | ||
Config systems | * Config systems | ||
Archive handling | * Archive handling | ||
* ... | |||
=== Topics to discuss === | |||
What do we want to discuss? Who are the people to discuss with? What do we want to achieve? What do other people expect? How do we address pushback? | |||
The contributor agreement? | * The contributor agreement? | ||
* ... | |||
Latest revision as of 16:31, 6 June 2011
Warning
What is the relationship between the Qt and KDE communities, in particular on a non-technical level? What can we do to improve it. What are the topics to address, and how do we do that?
Us and Them
There still is a us and them mentality. Communities could be closer together. There are a lot of common ideas. Lots of personal ties, but always changing. We need mutual respect. 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.
KDE is part of ecosystem of independent Qt libraries that are not part of Qt.
System how to get libraries, similar to 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 help with 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
This needs input from the outcome of other groups and topics discussed at the platform sprint. Do another breakout session towards the end of the sprint with the people who will be at the contributors' summit.
Goals
- Show KDE's attractiveness
- Present KDE vision to Qt people
General sessions
- KDE and Qt communities and working together, what can we learn from each other (community processes, e.g. code of conduct) (Frederik, Cornelius)
Technical sessions
- The things that should be merged: KUrl and friends
- KLocale QLocale
- Printing
- Config systems
- Archive handling
- ...
Topics to discuss
What do we want to discuss? Who are the people to discuss with? What do we want to achieve? What do other people expect? How do we address pushback?
- The contributor agreement?
- ...