Jump to content

Frameworks/Meetings/Akademy2013: Difference between revisions

From KDE Community Wiki
Ervin (talk | contribs)
Created page with "= KDE Frameworks presence at Akademy 2013 = == Office Hours == Every morning we'll be available in room B4. The goal is to be able to effectively work as a team in a single ..."
 
Dfaure (talk | contribs)
 
(3 intermediate revisions by 2 users not shown)
Line 11: Line 11:
== Release mode BoF ==
== Release mode BoF ==


Thursday afternoon, we'll be available in room B4 to discuss bigger topics to set the direction in KF5 in order to prepare for a 5.0 release.
Thursday afternoon, we'll be available in room B1 to discuss bigger topics to set the direction in KF5 in order to prepare for a 5.0 release.


Topics:
Topics:
* What's coming after KDEUI Crumble
* Finalize the KIO core/gui split
* Centralized? KDE SC versioning (KDE_VERSION)
* The famous "tier4"
* git repos
* C++11 support in KF5
* C++11 support in KF5
* Finalize the KIO core/gui split
* Frameworks diagram
* What's coming after KDEUI Crumble
* Identify critical blockers for release
* Identify critical blockers for release

Latest revision as of 13:24, 18 July 2013

KDE Frameworks presence at Akademy 2013

Office Hours

Every morning we'll be available in room B4. The goal is to be able to effectively work as a team in a single room, and have a faster turn around in preparing patches. Also, smaller topics can be discussed during that time and it will be the perfect arena for people who want to get involved to receive help for their setup.

Tasks and Topics:

  • Setting up build environment
  • Churning patches quicker as everyone is in the same room

Release mode BoF

Thursday afternoon, we'll be available in room B1 to discuss bigger topics to set the direction in KF5 in order to prepare for a 5.0 release.

Topics:

  • What's coming after KDEUI Crumble
  • Finalize the KIO core/gui split
  • Centralized? KDE SC versioning (KDE_VERSION)
  • The famous "tier4"
  • git repos
  • C++11 support in KF5
  • Frameworks diagram
  • Identify critical blockers for release