DapperStandardsBase

Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2005-11-04 20:50:28 →
Size: 1469
Editor: 192_220_103_66-WIFI_HOTSPOTS
Comment: Adding summary and a use case
← Revision 4 as of 2005-11-04 20:51:35 → ⇥
Size: 1465
Editor: 192_220_103_66-WIFI_HOTSPOTS
Comment: Minor text changes
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
With only a little extra work, we can make it a fantastic thing by providing a set of dapper features that will be supported in every further Ubuntu release for five years. With only a little extra work, we can make a Standerds Base by providing a set of dapper features that will be supported in every further Ubuntu release for five years.

Summary

With only a little extra work, we can make a Standerds Base by providing a set of dapper features that will be supported in every further Ubuntu release for five years.

This standards base should specify the library APIs that can be used (old libraries can be shipped in a compat section or pocket of further releases) and also focus on the system APIs (how do you add your program to Applications, etc.) that we will support in Ubuntu releases (through packages in the compat section or pocket). This BOF should outline those APIs and provide a specification for writing the DapperStandardsBase document.

Rationale

Dapper will be supported for five years, which makes it a great thing for vendors that which to support their software on Ubuntu.

Use cases

* Sue from Oracle wants to certify that their DBMS runs on Ubuntu, and they don't want to have to recertify every release. *

Scope

Design

Implementation

Code

Data preservation and migration

Outstanding issues

Do we support the whole thing for five years, or do we try to split out a server api from desktop api stuff?

BoF agenda and discussion

DapperStandardsBase (last edited 2008-08-06 16:17:15 by localhost)