UbuntuLiquid
3192
Comment:
|
4472
|
Deletions are marked like this. | Additions are marked like this. |
Line 22: | Line 22: |
[[MobileTeam/UbuntuLiquid/KDELibs|KDE Library Changes]] |
|
Line 35: | Line 33: |
Seed is created within the standard Kubuntu seed set. The initial set is a mirror of the current Kubuntu Netbook seed and can be evolved from there. It will likely be necessary to migrate some items from kubuntu-common to kubuntu-desktop and kubuntu-netbook to trim kubuntu-mobile down to size. |
|
Line 44: | Line 44: |
* Create another source package for it from kde-workspace? | * Create another source package for it from kdebase-workspace? |
Line 50: | Line 50: |
* Create another source package for it from kde-workspace * ??? - Will we remove any feature? |
* Add opengles support * Check with upstream what needs improvement * leave it lighter - Will we remove any feature? * kdelibs * there are discussions about splitting it * we need to join this discussion |
Line 55: | Line 60: |
* [[http://labs.trolltech.com/blogs/2009/09/21/introducing-qmf-an-advanced-mobile-messaging-framework/|QMF/QTMail]] - ''ńeeds packaging'' | * Till already got it working on n900 * Till and Henri(mindgard2) will work to add support for midgard2 (that means sqlite support) * Ubuntu One? |
Line 57: | Line 64: |
[[http://www.omat.nl/2009/09/30/qmf-vs-akonadi/|A good comparison of the above two choices]] [[http://qt.gitorious.org/qt-mobility]] [[http://qt.gitorious.org/qt-labs/messagingframework]] |
* KPackageKit * [[http://wiki.openmoko.org/wiki/Om2008.8_Installer | Openmoko Assassin]] |
Line 66: | Line 70: |
=== Nice to Have Features === | * QWS and Lighthouse * Investigate * package it * needs a different build of qt? |
Line 68: | Line 75: |
* Run apps from: * Android http://mjfrey.blogspot.com/2009/05/hacking-android-on-ubuntu.html * Maemo * WebOS [[http://developer.palm.com/index.php?option=com_content&view=article&id=1597|html/css/javascript]] Webkit? Mozilla Prism? * Create/Use a SDK to attract more developers. It would be nice to have a consistent,centralized,easy way for developers to create application for Ubuntu/Ubuntu Liquid |
* Footprint * may still be large for maverick * for maverick+1 work to get it small |
Line 85: | Line 88: |
== Maverick UDS Discussion == * What is it: KDE plasma mobile * for handhelds: - n900 * ofono can talk to ofono modem ... login aka SIM PIN * how to build kde workspace in maverick? * we can duplicate source to understand what to do in the long run * kdelibs split -> cannot be done in the distro: upsteram is working on it * kwin opengles support * Upstream appears to be working on this. Martin is doing an Akademy talk on this in July * without X -> could be done as an experiment, but probably wouldnt be a default * KDM very much depends on X. (It historically is an XDM fork with a nice frontend) * Ubuntu One support for akonadi does not exist * QWS/lighthouse - Qt is ABI incompatible; * footprint: efforts by foundations, ubuntu on arm and server teams to reduce minimal diski footprint kdeworkspace / kdelibs might allow to avoid bloat Seeds: * kubuntu-plasma-mobile with strimmed Branding options: * Keep Liquid as a code name. * Consider shifting towards the Kubuntu brand later, depending on progress and rbelem's wishes (Perhaps "Kubuntu Mobile Remix") == Wiki Pages == * https://wiki.ubuntu.com/MobileTeam/UbuntuLiquid * https://wiki.ubuntu.com/MobileTeam/UbuntuLiquid/Seed |
Project Goals
The principal objective is to bring to mobile devices the latest updates available in the Ubuntu world. Associated aims are to build a community around the release and for the release to be as 'light' as possible.
It will be built using the Ubuntu infrastructure for creating a distribution. To help out with the development please join the Liquid Hackers team
Blueprint
To Do
The blueprint above is always updated with the current To Do list. Go there after setting up the development environment
Setting up the Development Environment
Braindump from the Developer Summit (for archive purposes)
On Screen Keyboard
http://www.notmart.org/index.php/Software/On_screen_keyboard
Plasma Mobile
Plasma Mobile (to package)
Seed
Seed is created within the standard Kubuntu seed set. The initial set is a mirror of the current Kubuntu Netbook seed and can be evolved from there. It will likely be necessary to migrate some items from kubuntu-common to kubuntu-desktop and kubuntu-netbook to trim kubuntu-mobile down to size. Liquid seed
What needs improvement
- Display Manager
- kdm
- Add plugin support
- Write plugins for different types of authentication
- Write plugin to unlock GSM PIM
- On Screen Keyboard
- Create another source package for it from kdebase-workspace?
- Remove xdmcp
- ??? - leave it lighter as possible
- Add plugin support
- kdm
- Window Manager
- kwin
- Add opengles support
- Check with upstream what needs improvement
- leave it lighter - Will we remove any feature?
- kwin
- kdelibs
- there are discussions about splitting it
- we need to join this discussion
- PIM
akonadi? ScottK -- KDAB is also doing an embedded version of Akonadi - packaged
- Till already got it working on n900
- Till and Henri(mindgard2) will work to add support for midgard2 (that means sqlite support)
- Ubuntu One?
- KPackageKit
- Office
Koffice - packaged
- QWS and Lighthouse
- Investigate
- package it
- needs a different build of qt?
- Footprint
- may still be large for maverick
- for maverick+1 work to get it small
Release Name
After the politics of the release are sorted out and we get round to actually releasing something, it will be called 'Original Liquid Vibe'
Discussions
Discussion about plasma-mobile @plasma-devel http://mail.kde.org/pipermail/plasma-devel/2009-November/009185.html
Maverick UDS Discussion
- What is it: KDE plasma mobile
- for handhelds: - n900
- ofono can talk to ofono modem ... login aka SIM PIN
- how to build kde workspace in maverick?
- we can duplicate source to understand what to do in the long run
kdelibs split -> cannot be done in the distro: upsteram is working on it
- kwin opengles support
- Upstream appears to be working on this. Martin is doing an Akademy talk on this in July
without X -> could be done as an experiment, but probably wouldnt be a default
- KDM very much depends on X. (It historically is an XDM fork with a nice frontend)
- Ubuntu One support for akonadi does not exist
- QWS/lighthouse - Qt is ABI incompatible;
- footprint: efforts by foundations, ubuntu on arm and server teams to reduce minimal diski footprint
- kdeworkspace / kdelibs might allow to avoid bloat
- kubuntu-plasma-mobile with strimmed Branding options:
- Keep Liquid as a code name.
- Consider shifting towards the Kubuntu brand later, depending on progress and rbelem's wishes
- (Perhaps "Kubuntu Mobile Remix")
Wiki Pages
Roadmap
Lucid Roadmap (needs updating)
MobileTeam/UbuntuLiquid (last edited 2010-09-28 17:54:32 by 189)