Frameworks/Terminology: Difference between revisions
No edit summary |
|||
| Line 12: | Line 12: | ||
Frameworks are classified along two axis: Tier and Type. This classification provides constraints on the outside dependencies of a Framework. For more details, see the [[Frameworks/Policies|Policies]] page. | Frameworks are classified along two axis: Tier and Type. This classification provides constraints on the outside dependencies of a Framework. For more details, see the [[Frameworks/Policies|Policies]] page. | ||
== Platform 11 == | == Platform 11 == | ||
[[KDE_Core/Platform_11|Platform 11] | [[KDE_Core/Platform_11|Platform 11] | ||
Revision as of 13:20, 20 November 2012
The people working on KDE Frameworks use some terms you might not find in other KDE teams. This page is listing and defining them.
Epic
This term comes of the agile movement. There people generally plan using user stories which are splitted in tasks. A group of story can form a feature, and then features would group in epics.
So in other word, an "Epic" is a very large body of work encompassing several different activities. It is comparable in size with a project in the traditional meaning (an effort of several months which has a start and an end).
Framework
A Framework is the base unit of KDE Frameworks. It is a self contained body of reusable code. It can consist of a single library in its simplest form, but it can grow to being several libraries and a few shipped plugins. A Framework is generally shipped also with tests, demos and examples.
Frameworks are classified along two axis: Tier and Type. This classification provides constraints on the outside dependencies of a Framework. For more details, see the Policies page.
Platform 11
[[KDE_Core/Platform_11|Platform 11]