Planning

Differences between revisions 34 and 38 (spanning 4 versions)
Revision 34 as of 2010-04-26 13:40:12
Size: 6396
Editor: eth0
Comment:
Revision 38 as of 2010-04-28 14:56:42
Size: 7718
Editor: dslb-088-073-106-104
Comment:
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
 * [[UbuntuSpec:foundations-m-brtfs-support|brtfs Support]]  * [[UbuntuSpec:foundations-m-btrfs-support|btrfs Support]]
 * [[UbuntuSpec:foundations-m-uefi-support|UEFI Firmware Support]]
Line 23: Line 25:
 * As part of their UNE work, Desktop may end up promoting Chomium to main  * As part of their UNE work, Desktop may end up promoting Chromium to main
Line 58: Line 60:

---- /!\ '''Edit conflict - other version:''' ----

---- /!\ '''Edit conflict - your version:''' ----
== Support FOR Foundations ==

Collect here items which we would like to see be done by other teams

=== Desktop ===

 * Java Applet maintainance / development
 * Stable xulrunner-1.9 interfaces when having more than one xulrunner version on the desktop (both eclipse and the icedtea6-plugin don't seem to get it right).

=== Launchpad ===

 * Soyuz/IS: Rebuild tests take too long, or slow down PPA buildds.



---- /!\ '''End of edit conflict''' ----
Line 65: Line 87:

---- /!\ '''Edit conflict - other version:''' ----
Line 68: Line 92:
   * Python 2.7?    * [[UbuntuSpec:foundations-m-python-2.7|Python 2.7]] (BarryWarsaw)

---- /!\ '''Edit conflict - your version:''' ----
   * NO more symlinks or files created at configure time of packages.
   * Automated transition testing framework (build, run upstream unit test, 2to3, report on ftbfs and test failures, against any/every python version)
   * Migration to Python 3? Unlikely, but we need sessions on building a package stack for Python3.
   * Eliminate symlinks for python-[central|support] using PEP 3147?
   * Python 2.7? That could be tested before UDS as a basis for a decision.

---- /!\ '''End of edit conflict''' ----

Ideas

Foundations Support

As usual, Foundations will be providing Ubuntu support for the other teams. A high-level listing of projects where we likely will be involved is given in this section.

Desktop

  • As part of their UNE work, Desktop may end up promoting Chromium to main
  • HUGE push for Software Center
    1. goal: sell stuff in software center,
    2. goal: figure out how to deliver opportunistic apps via the software center
    3. finish ratings
  • Big push for touch, not sure what the impact is going to be for Foundations yet, but we need to be aware of it
  • It would really help Desktop if Upstart+Plymouth work stabilized so they could work with it

Design

  • Wayland (no idea what state this is in upstream, and the X side of things should be desktop, but at the very least we'll need to look at how this overlaps/interacts with Plymouth);
  • We probably ought to have a look-in on the multi-screen work, if it's dealing with remembering configurations for individual devices;
  • Installer, first boot, upgrades, Update Manager, and Software Centre;
  • System settings (maybe, depending on what this comes down to);
  • Possibly keyboard indicator but it depends what they're doing (if it's just visual then probably not).

Server

The server team has listed their planning by priority; their bullet items below reflect this.

  • Priority 1: Cloud cluster file system (not sure if we'll be needed for this or not)
  • Priority 2: Java/JDK improvements (doko does a lot of that; Server team is getting a Java person, so this may impact us less)
  • Priority 2: Support of alternate install modes
  • Priority 3: Upstart conversion

Kernel

  • Improved battery power support work; Foundations may need to (or be able to) assist
  • synaptec multi-touch (multi-finger... not multi-touch)
  • new multi-touch driver enhancements that may need work from Foundations

OEM

  • TBD


Warning /!\ Edit conflict - other version:



Warning /!\ Edit conflict - your version:


Support FOR Foundations

Collect here items which we would like to see be done by other teams

Desktop

  • Java Applet maintainance / development
  • Stable xulrunner-1.9 interfaces when having more than one xulrunner version on the desktop (both eclipse and the icedtea6-plugin don't seem to get it right).

Launchpad

  • Soyuz/IS: Rebuild tests take too long, or slow down PPA buildds.


Warning /!\ End of edit conflict


Placeholders for Big Topics

  • 10.04 Review - hold this early to aid breakout topics, maybe in the first roundtable

  • Distributed Development
  • Boot Performance/Experience
  • Spring Clean (right after an LTS release is a good time for an aggressive cleanup of things we don't need or that should be extensively refactored)
  • Python


Warning /!\ Edit conflict - other version:


  • Automated transition testing framework (build, run upstream unit test, 2to3, report on ftbfs and test failures, against any/every python version)
  • Migration to Python 3?
  • Eliminate symlinks for python-[central|support] using PEP 3147?
  • Python 2.7 (BarryWarsaw)


Warning /!\ Edit conflict - your version:


  • NO more symlinks or files created at configure time of packages.
  • Automated transition testing framework (build, run upstream unit test, 2to3, report on ftbfs and test failures, against any/every python version)
  • Migration to Python 3? Unlikely, but we need sessions on building a package stack for Python3.
  • Eliminate symlinks for python-[central|support] using PEP 3147?
  • Python 2.7? That could be tested before UDS as a basis for a decision.


Warning /!\ End of edit conflict


  • Freezing (e.g. cx_freeze) critical dist upgrade tools?

Lucid specs not done

(Numbers in parentheses indicate to-do/postponed/done.)

Lucid specs partly done

Lucid specs mostly done

FoundationsTeam/Maverick/Planning (last edited 2010-05-04 14:04:46 by p5B09F55E)