Scratchpad

Differences between revisions 1 and 12 (spanning 11 versions)
⇤ ← Revision 1 as of 2013-05-09 22:41:03 →
Size: 65
Editor: h-4-180
Comment:
← Revision 12 as of 2013-05-10 16:27:14 → ⇥
Size: 2253
Editor: h-4-180
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= list of everything covering Ubuntu Studio development = <<Include(UbuntuStudio/Navigation/Header)>>
||<tablestyle="width: 30%; float: right; background-color: #e1f0f4; border-radius: 10px;"><<Include(UbuntuStudio/Navigation/DevSideBar)>>||
Line 3: Line 4:
.. <<TableOfContents()>>

= All About Ubuntu Flavor Development =

== What Makes Up A Ubuntu Flavor Operative System? ==

=== The Flavor Meta ===

The flavor meta source is a single package source, which, when built, may result in a multitude of binary meta packages. The metas themselves are always empty, but depends on a set of packages, which form what you could call a '''package set''' - the list of packages that make up that flavor.

=== Seeds ===

When building a meta package, it looks for the dependencies from what we call seeds. The seeds are basically a set of text files, where all the package dependencies are listed.

==== Install Tasks (correct term?) ====

The seeds are also used for creating "install tasks", which are selectable from a expert install medium, such as the Ubuntu netinstall.

=== Other Flavor Packages ===

At the very least, each flavor will have a package called '''<flavor>-default-settings'''. This is not an empty package, like the meta, and includes some specific system settings for that flavor.

Some flavors will have additional special packages, such as theming packages, or flavor specific applications.





'''What makes up the OS'''
 * The Packages
  * Seeds - the Flavor package set
  * The flavor Meta
  * task-installs
 * Debian Packaging - uploading, syncing, merging, PPA, bzr, etc
 * Strategy/Policy for package selection (flavor dependent)
 * How ISOs are built (the build server)

'''Updates'''
 * Bug Fixes
  * Setting Up Notification of bugs
  * Fixing bugs upstream in Debian and orig source
 * SRU - Stable Release Update
 * Backports

'''Quality Assurance'''
 * Testing ISOs (Pre Release)
 * Testing new uploads of packages
  * Setting Up Notification of changes
 * Using Testing Tools - Autopilot, UTAH, scripts

'''Feature Development'''
 * Software Development
 * Pushing for changes upstream

'''Artwork'''
 * Development Process

'''Tools'''
 * The Launchpad Server
 * Additional Website Services
 * Development tools
  * bzr
  * git

Contents

  1. All About Ubuntu Flavor Development
    1. What Makes Up A Ubuntu Flavor Operative System?
      1. The Flavor Meta
      2. Seeds
        1. Install Tasks (correct term?)
      3. Other Flavor Packages

All About Ubuntu Flavor Development

What Makes Up A Ubuntu Flavor Operative System?

The Flavor Meta

The flavor meta source is a single package source, which, when built, may result in a multitude of binary meta packages. The metas themselves are always empty, but depends on a set of packages, which form what you could call a package set - the list of packages that make up that flavor.

Seeds

When building a meta package, it looks for the dependencies from what we call seeds. The seeds are basically a set of text files, where all the package dependencies are listed.

Install Tasks (correct term?)

The seeds are also used for creating "install tasks", which are selectable from a expert install medium, such as the Ubuntu netinstall.

Other Flavor Packages

At the very least, each flavor will have a package called <flavor>-default-settings. This is not an empty package, like the meta, and includes some specific system settings for that flavor.

Some flavors will have additional special packages, such as theming packages, or flavor specific applications.

What makes up the OS

  • The Packages
    • Seeds - the Flavor package set
    • The flavor Meta
    • task-installs
  • Debian Packaging - uploading, syncing, merging, PPA, bzr, etc
  • Strategy/Policy for package selection (flavor dependent)
  • How ISOs are built (the build server)

Updates

  • Bug Fixes
    • Setting Up Notification of bugs
    • Fixing bugs upstream in Debian and orig source
  • SRU - Stable Release Update
  • Backports

Quality Assurance

  • Testing ISOs (Pre Release)
  • Testing new uploads of packages
    • Setting Up Notification of changes
  • Using Testing Tools - Autopilot, UTAH, scripts

Feature Development

  • Software Development
  • Pushing for changes upstream

Artwork

  • Development Process

Tools

  • The Launchpad Server
  • Additional Website Services
  • Development tools
    • bzr
    • git

UbuntuStudio/DeveloperDocumentation/Scratchpad (last edited 2013-05-17 01:50:29 by h-4-180)