Comment 49 for bug 629622

ETA: Tuesday; aka Monday 2010-09-27 23:59 UTC

  When:

Robbie has notifed that the deadline is the above, and so that is the
target. Riddell is building CDs and is aware. This leaves 72^W...
60^W... 48^W... 42 hours, of I which I selfishly intend to reserve
some for sleeping.

  What:

The package will ship with the source available and the font-related
files under whatever licence Mark finalises at that point in time.
Documentation and code/script/packaging will be under GPLv3.

  font.ubuntu.com microsite (requested via RT)

The published URL for the Ubuntu Font Family will be
'font.ubuntu.com' and this will include a source .zip file, links to
PPA, Launchpad, Wiki, ... along with a copy-and-paste webfonts
configuration hosted on font.

  Webfonts:

Long term, an automatic build process can build the EOT/WOFF
web-optimised versions, but for the moment, can defer to Richard Lee
for current knowledge from fonttet.design.canonical.com.

The logistics of this /may/ be transferred off to a third party fairly
soon afterwards.

  Currency block:

At Mark's behest, there will be a push to get U+20B9 (the new Indian
Rupee Sign) populated with /something/, even if DM decide this wish
to tweak this later. We'll use this as a testbed for sending a
'patch' upstream, as well as getting it back again downstream:

 * https://bugs.launchpad.net/ubuntu-font-family/+bug/645987

  Documentation:

Collation of blogs/LP replies/off-list replies to cover as many design
rationale choices as possible. These will be GPLv3ed and shipped as
documentation in the "upstream" source tar, and Copyright Canonical.

  .deb

This will be converted to native and built off the expanded upstream
tarball (eg. ubuntu-font-family-0.68+doc) and (hopefully) meeting all
of Nicolas' requests.

  Licence formattting

Need as OOo and txt, for FAQs and markup.

  Licence switch over

Current intention is to patch the output .ttfs using Python to change
the licence, version and Family name inside them as the turnaround via
Dalton Maag might be too long... though as the code is not yet
written, this depends.

  Uploading

This bit is really easy assuming the paperwork checks out:

* Upload package (sladen)
* Source NEWed (riddell)
* Binary NEWed (riddell)
* MIR approval (doko, asac, kees)
* Migrate to main (riddell)
* Add to seeds (sladen)
* Add to meta packages (sladen)
* Upload meta packages (sladen)
* Accept meta packages (riddell)
* Re-build CDs lots (riddell)

  Limitation

Note, the priority here is to get it seeded and on to the CDs. If
some other party wishes to adapt their themes to use this installed
font package, then they will now be able to write their /own/ FFEs for
a theme tweak on their side!

  AOB

Lots of interesting conversations about Right-to-Left, Arabic and
Hebrew over the last couple of days, particularly in response to
Bruno's initial posting of the UFF Hebrew experiments in this
direction.