KDEEdu/Sprint2012/ArtworkNotes: Difference between revisions

Latest revision as of 18:01, 25 September 2012

* Artwork, UI Design, and Usability
 * Do we have something we can do better for attracting such contributors?
 * How can we do this better ourselves when we have a lack of expertise around? What guidelines should we consider?
 * Any lessons learned from previous mobile efforts or from desktop? 
  - Aleix comments it was hard to get people to help with Pairs design when he thinks
    it should have been an easy task
  - Marco comments randomly aproaching people on G+ "design" circles
  - It is hard to find people outside our circles
  - We need to be proactive and make big steps into contacting people
  - Make it easier for users to give feedback (forum? app stores?)

@@ Line 1: / Line 1: @@
 <pre>
-* Qt5 and KDE Frameworks
+* Artwork, UI Design, and Usability
-  * Worth starting?
+  * Do we have something we can do better for attracting such contributors?
-  - KF modularization is better for appstores
+ * How can we do this better ourselves when we have a lack of expertise around? What guidelines should we consider?
-  - Too early unless you want to experiment
+  * Any lessons learned from previous mobile efforts or from desktop?
-  - Create a frameworks branch to experiment there
+   - Aleix comments it was hard to get people to help with Pairs design when he thinks
-  * Are there contributors for porting and experimenting?
+    it should have been an easy task
-   - Porting should be "easy" since Qt5 and KF "promise" almost API compatibility
+  - Marco comments randomly aproaching people on G+ "design" circles
-   - Sebastian looking forward to use QtQuick2 on KTouch next
+  - It is hard to find people outside our circles
-   - Make it on a second step, first port to frameworks, then port to QtQuick2
+   - We need to be proactive and make big steps into contacting people
-    - Components?
+  - Make it easier for users to give feedback (forum? app stores?)
-     - Qt Contributor Summit "decided" the various component platforms
-       should have API compatibility
 </pre>