KDEEdu/Sprint2012: Difference between revisions

From KDE Community Wiki
m (→‎Agenda: Fix those some grammar issues)
No edit summary
 
(11 intermediate revisions by 2 users not shown)
Line 4: Line 4:
= Agenda =
= Agenda =


*KDE Edu
* KDE Edu and Teachers [[KDEEdu/Sprint2012/TeachersNotes|Notes]]
** Presentation on "Cooperative Learning"
** Presentation on "Cooperative Learning"
** Brainstorming for new educational applications based on "Cooperative Learning"
** Brainstorming for new educational applications based on "Cooperative Learning"
** How can we introduce teachers in the development process?
** How can we introduce teachers in the development process?
*** How to get teaching material for our applications/that make use of our applications?
*** How to get teaching material for our applications/that make use of our applications?
* New KDE Edu programs [[KDEEdu/Sprint2012/NewProgramsNotes|Notes]]
** Couple of participants mentioned that during the face to face introduction they have new ideas. Let us have a discussion about those!
** Couple of participants mentioned that during the face to face introduction they have new ideas. Let us have a discussion about those!
*** Mula mockups: https://projects.kde.org/projects/playground/edu/mula/repository/revisions/master/show/frontends/mockup
*** Mula mockups: https://projects.kde.org/projects/playground/edu/mula/repository/revisions/master/show/frontends/mockup




* KDE Edu on Windows
* KDE Edu on Windows [[KDEEdu/Sprint2012/WindowsNotes|Notes]]
** How to attract contributors to fix runtime or build issues on Windows?
** How to attract contributors to fix runtime or build issues on Windows?
** Cross compilation on Linux if no license available? Document how to do it?
** Cross compilation on Linux if no license available? Document how to do it?
Line 20: Line 23:




* KDE Edu on Mobile
* KDE Edu on Mobile [[KDEEdu/Sprint2012/MobileNotes|Notes]]
** What projects should be ported?
** What projects should be ported?
** Do we want different versions for the Mobile version?
** Do we want different versions for the Mobile version?
Line 33: Line 36:
** Evaluation: what metrics make a platform more potential than another for KDE Edu?  
** Evaluation: what metrics make a platform more potential than another for KDE Edu?  
** How to make the build simple for various platforms (i.e. helping developer, packagers, and so forth)?
** How to make the build simple for various platforms (i.e. helping developer, packagers, and so forth)?
** Mobile edu logo (less detailed? Getting svgs so that is easier to handle forth and back?)




* Website
* Website [[KDEEdu/Sprint2012/WebsiteNotes|Notes]]
** State?
** State?
** What's missing?
** What's missing?
Line 41: Line 45:




* Plasma Active
* Plasma Active [[KDEEdu/Sprint2012/PlasmaActiveNotes|Notes]]
** How can we make sure we are a first citizen on the project?
** How can we make sure we are a first citizen on the project?
** How can we take advantage from it?
** How can we take advantage from it?




* Quality
* Quality [[KDEEdu/Sprint2012/QualityNotes|Notes]]
** Code testing coverage?
** Code testing coverage?
** Testing? More collaboration with the Quality team and teachers to test new releases?
** Testing? More collaboration with the Quality team and teachers to test new releases?
Line 54: Line 58:




* Artwork, UI Design, and Usability
* Artwork, UI Design, and Usability [[KDEEdu/Sprint2012/ArtworkNotes|Notes]]
** Do we have something we can do better for attracting such contributors?
** 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?
** How can we do this better ourselves when we have a lack of expertise around? What guidelines should we consider?
Line 60: Line 64:




* Qt5 and KDE Frameworks
* Qt5 and KDE Frameworks [[KDEEdu/Sprint2012/Qt5KFNotes|Notes]]
** Worth starting?
** Worth starting?
** Are there contributors for porting and experimenting?
** Are there contributors for porting and experimenting?
=Goals=

Latest revision as of 17:59, 25 September 2012

General Information

Randa Sprint in sprints.kde.org

Agenda

  • KDE Edu and Teachers Notes
    • Presentation on "Cooperative Learning"
    • Brainstorming for new educational applications based on "Cooperative Learning"
    • How can we introduce teachers in the development process?
      • How to get teaching material for our applications/that make use of our applications?



  • KDE Edu on Windows Notes
    • How to attract contributors to fix runtime or build issues on Windows?
    • Cross compilation on Linux if no license available? Document how to do it?
    • Can we distribute on their market?
    • What will happen with Metro+KDE?


  • KDE Edu on Mobile Notes
    • What projects should be ported?
    • Do we want different versions for the Mobile version?
    • Should they be available for free on the platform markets?
    • Localization issues?
    • How to advertise KDE Edu better in mobile softwares?
    • How to improve app-in purchase like a new translation? Porting GHNS or something else?
    • How to get devices or simulators up and running easily?
    • Common feedback from the appstore reviews?
    • Adding screenshots and few words on the website?
    • How can we lower the barrier to get into mobile tasks?
    • Evaluation: what metrics make a platform more potential than another for KDE Edu?
    • How to make the build simple for various platforms (i.e. helping developer, packagers, and so forth)?
    • Mobile edu logo (less detailed? Getting svgs so that is easier to handle forth and back?)


  • Website Notes
    • State?
    • What's missing?
    • How can we improve it?


  • Plasma Active Notes
    • How can we make sure we are a first citizen on the project?
    • How can we take advantage from it?


  • Quality Notes
    • Code testing coverage?
    • Testing? More collaboration with the Quality team and teachers to test new releases?
    • Documentation of the project, even software architectures?
    • How to get the best code out from not primarily programmers, but scientists?
    • Continous Integration and Jenkins, something missing?


  • Artwork, UI Design, and Usability Notes
    • 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?


  • Qt5 and KDE Frameworks Notes
    • Worth starting?
    • Are there contributors for porting and experimenting?