|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?
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.
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?
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?
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.
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?