(→N) |
(→C) |
||
| (6 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| + | MeeGo has many terms whose meaning is not immediately apparent. This page will attempt to help rectify that. | ||
| + | |||
== A == | == A == | ||
;''Architecture: '' | ;''Architecture: '' | ||
| Line 4: | Line 6: | ||
;''ARM: '' | ;''ARM: '' | ||
| - | :The CPU powering the N900 and many other mobile devices. | + | :The CPU powering the N900 and many other mobile devices. See [[ARM]] |
;''ATM: '' | ;''ATM: '' | ||
| Line 12: | Line 14: | ||
;''Beagle-board: '' | ;''Beagle-board: '' | ||
| - | :Is an OMAP3 based development board suitable for embedded projects | + | :Is an OMAP3 based development board suitable for embedded projects. See [[ARM/Meego on the Beagle]] |
;''BME (Battery Management Entity): '' | ;''BME (Battery Management Entity): '' | ||
| Line 18: | Line 20: | ||
;''BOSS: (Build Orchestration Supervision System) '' | ;''BOSS: (Build Orchestration Supervision System) '' | ||
| - | :Is the workflow tool for releases | + | :Is the workflow tool for releases. See [[Release Infrastructure/BOSS]] |
== C == | == C == | ||
| + | |||
| + | ;''CE'' | ||
| + | :[[Community Edition]] | ||
| + | |||
;''Compliance: '' | ;''Compliance: '' | ||
| - | : is designed to make sure things stay compatible, such that the devices supporting a particular MeeGo version can run the same software | + | : is designed to make sure things stay compatible, such that the devices supporting a particular MeeGo version can run the same software. [[Quality/Compliance]] |
== D == | == D == | ||
| + | |||
| + | ;''DE'' | ||
| + | :Developer edition. Has been renamed in June 2011 to CE (Community Edition). | ||
| + | |||
;''DirectUI (DUI)'' | ;''DirectUI (DUI)'' | ||
:see MeeGo Touch Framework | :see MeeGo Touch Framework | ||
;''Dual Boot'' | ;''Dual Boot'' | ||
| - | :is a way of allowing meego devices to run multiple operating systems | + | :is a way of allowing meego devices to run multiple operating systems. See [[ARM/N900/Install/Dual Boot]] |
== E == | == E == | ||
| Line 67: | Line 77: | ||
;''IIRC: '' | ;''IIRC: '' | ||
:If I Recall Correctly | :If I Recall Correctly | ||
| + | |||
| + | ;''IMG'' | ||
| + | :Image creator | ||
;''Intel'' | ;''Intel'' | ||
| Line 73: | Line 86: | ||
;''Kernel (linux)'' | ;''Kernel (linux)'' | ||
| - | : is the open source core of the operating system and without which we would not have Meego! | + | : is the open source core of the operating system and without which we would not have Meego! See [[MeeGo kernel documentation for contributors]] |
;''Kickstart files (.ks)'' | ;''Kickstart files (.ks)'' | ||
| - | : provide a list of packages and settings to use for automated installs. | + | : provide a list of packages and settings to use for automated installs. See [[Image Creation]] |
== L == | == L == | ||
| Line 127: | Line 140: | ||
:MeeGo Core + Reference Netbook UX | :MeeGo Core + Reference Netbook UX | ||
;''MeeGo SDK'' | ;''MeeGo SDK'' | ||
| - | :A [ | + | :A [[Getting started with the MeeGo SDK for Linux|software development kit for MeeGo]] |
;''MeeGo Touch Framework (MTF)'' | ;''MeeGo Touch Framework (MTF)'' | ||
:provides the features needed for developers creating applications for touch-enabled devices. Features include standardized window navigation, list and other widget behavior, and common theming for components. | :provides the features needed for developers creating applications for touch-enabled devices. Features include standardized window navigation, list and other widget behavior, and common theming for components. | ||
| Line 150: | Line 163: | ||
;''N900'' | ;''N900'' | ||
| - | : Nokia ARM powered handheld phone for open Meego development | + | : Nokia ARM powered handheld phone for open Meego development. See [[ARM/N900]] |
;''Netbook'' | ;''Netbook'' | ||
| Line 157: | Line 170: | ||
== O == | == O == | ||
;''OBS (OpenSuse Build System) : '' | ;''OBS (OpenSuse Build System) : '' | ||
| - | :The Opensuse Build Service. is an open and complete distribution development platform that provides a transparent infrastructure for development. The service provides software developers with a convenient and easy to use tool to create and release open source software for openSUSE and other Linux distributions on different hardware architectures and for a broad user audience. [ | + | :The Opensuse Build Service. is an open and complete distribution development platform that provides a transparent infrastructure for development. The service provides software developers with a convenient and easy to use tool to create and release open source software for openSUSE and other Linux distributions on different hardware architectures and for a broad user audience. See [[Build System]] |
| + | |||
;''OCS (Open Collaboration Services) : '' | ;''OCS (Open Collaboration Services) : '' | ||
| - | : a web API for browsing application catalogues, doing event and contact discovery [http://www.freedesktop.org/wiki/Specifications/open-collaboration-services OCS API] | + | : a web API for browsing application catalogues, doing event and contact discovery [http://www.freedesktop.org/wiki/Specifications/open-collaboration-services OCS API]. Also, OBS command line client |
;''Orbit'' | ;''Orbit'' | ||
| Line 168: | Line 182: | ||
;''OTS (Open Test System): '' | ;''OTS (Open Test System): '' | ||
| - | :Suite of testing tools and configuration files for managing reproducible QA testing | + | :Suite of testing tools and configuration files for managing reproducible QA testing. See [[Quality/QA-tools/OTS|OTS Wiki]] |
| + | |||
| + | == P == | ||
| + | ;''PA (PulseAudio)'' | ||
| + | : is the low level sound system component used by Meego. See [[Quality/TestSuite/PulseAudio Test Plan]] | ||
== Q == | == Q == | ||
| Line 192: | Line 210: | ||
;''Reference Handheld UX'' | ;''Reference Handheld UX'' | ||
:a reference (example) implementation of a user interface for handheld devices, based on the MeeGo Touch framework. It is expected to be replaced or augmented with manufacturer provided user interfaces/system applications on actual devices. | :a reference (example) implementation of a user interface for handheld devices, based on the MeeGo Touch framework. It is expected to be replaced or augmented with manufacturer provided user interfaces/system applications on actual devices. | ||
| + | |||
| + | ;''REVS'' | ||
| + | :Release Engineering Visibility System | ||
== S == | == S == | ||
| Line 212: | Line 233: | ||
;''TMO (talk.maemo.org): '' | ;''TMO (talk.maemo.org): '' | ||
:Main forum for Maemo non-technical community. | :Main forum for Maemo non-technical community. | ||
| + | |||
| + | ;''UC (Use Case): '' | ||
| + | : Nokianism for Use case description in documentation. | ||
== U == | == U == | ||
| Line 222: | Line 246: | ||
== Useful links == | == Useful links == | ||
* [http://www.acronymfinder.com Acronym Finder] | * [http://www.acronymfinder.com Acronym Finder] | ||
| - | * [http://wiki.maemo.org/Codenames Maemo Codenames] | + | * [http://wiki.maemo.org/Codenames Maemo Codenames] |
MeeGo has many terms whose meaning is not immediately apparent. This page will attempt to help rectify that.
Contents |