Difference between revisions of "Projects/KDevelop4/Meeting2011"

Jump to: navigation, search
(Project Dashboard)
(Project Dashboard)
Line 82: Line 82:
  
 
plasmoids:
 
plasmoids:
 
 
* vcs commit log (provided by vcs plugin)
 
* vcs commit log (provided by vcs plugin)
* project info:
+
* file contents view
** news
+
* webslide
** resources (bugtracker, mailing list, irc...)
+
* feedreader
* notes, i.e. personal todo, project todo, ... => file view / webslide?
+
 
 +
use cases:
 +
* project website news (feed reader)
 +
* project resources: bugtracker, mailing list, ... (webslide / file contents view)
 +
* recent commits (vcs plugin)
  
 
=== Tue ===
 
=== Tue ===

Revision as of 11:06, 3 June 2011

Contents

Randa 2011 KDevelop Meeting

Agenda

Thu

  • get up with an agenda

Plugins

requirements for plugins in extragear/kdevelop/*:

  • kdereview
  • maintainer
  • releasable
  • unit tests (and none failing)

plugins to merge:

  • kdevplatform/
    • controlflowgraph
      • TODO: investigate status, get out of kdereview
    • execute script
      • TODO: investigate status, get into kdereview
  • kdevelop/
    • qmake
      • TODO: Milian: investigate status, get into kdereview
  • kdevelop/plugins/
    • merge php/php-docs
      • TODO: Milian
    • css
      • TODO: investigate status, get into kdereview
    • execute browser
      • TODO: investigate status, get into kdereview
    • xdebug
      • TODO: investigate status, get into kdereview

notes on /plugins:

  • not a single big repo (devs against it)
  • TODO: document easy "build-all" process on techbase

note for developers: kdevplatform API breakages must be fixed in every stable repo, i.e. everything in https://projects.kde.org/projects/extragear/kdevelop must be compiling

Build Bot & Unit Testing

  • TODO: Get a build bot running
    • either on every commit (much work)
    • or at least once a day (single to implement)
  • TODO: Get a unit test bot running
    • requirements:
      • no failing unit tests (XFAIL is OK)
      • no agressive performance tests (time limit, memory limit, ...)
  • TODO: investigate cdash
    • kdelibs dashboard is down, not a good impression
  • TODO: ask PovAddict on his experience with build bot + unit tests

Gluon

  • try to rebase gluoncreator on kdevplatform
  • put improvements into the platform
    • plugin based diff-viewer (i.e. to compare designer files, images, ...)
    • improved history viewer (timeline, ...)
  • alternatively try to reuse parts of kdevplatform in gluoncreator
    • problem: kdevplatform (rightly so!) expect full kdevplatform availability

Unit Tests

developers:

  • never submit failing unit tests (use QEXPECT_FAIL)
  • try to run unit tests regularily

Wed

Project Dashboard

saving/sharing:

  • opt-in 'save to project file' which is shared to users via project.kdev4
    • good for users opening the project the first time in kdevelop
  • by default save changes to dashboard in .kdev4/ folder

plasmoids:

  • vcs commit log (provided by vcs plugin)
  • file contents view
  • webslide
  • feedreader

use cases:

  • project website news (feed reader)
  • project resources: bugtracker, mailing list, ... (webslide / file contents view)
  • recent commits (vcs plugin)

Tue

Fri

Sat

Sun

Mon

Thu

  • wrap up & leave home

Discussion TODO

not so controversial

  • [DONE] merge control flow into kdevplatform
  • [DONE] merge qmake into kdevelop
  • [DONE] extra-plugins module: css, execute-script, execute-browser, andreas' custom project manager, ...
  • gluon integration
  • handle rename/delete of file in editor view
  • handle switching branch -> reload open (changed) files
  • port mailing list to kde infrastructure
  • improve website / wikis / ...
    • promotion part
  • integrate wiki documentation

controversial

  • browser-like tabs
  • welcome page
  • drag&drop
  • merge aliex's thesis work

very controversial

  • destroy areas
  • chromium-like UI

Hacking TODO

  • remove/disable/fix failing unit tests
  • fix QWarnings (esp. timer issues etc.)
  • go through review requests
  • extended cli support (open in existing instance)
    • requires extended dbus interface
  • krunner integration (session)

KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal