DeveloperDocumentation

Differences between revisions 84 and 85
⇤ ← Revision 84 as of 2013-05-17 01:29:17 →
Size: 6883
Editor: h-4-180
Comment:
← Revision 85 as of 2015-04-26 16:35:49 → ⇥
Size: 2936
Editor: h-141-65
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
 * public relations - list of places to make announcements, hashtags
Line 15: Line 14:
 * Generate gnupg key - needed for things like a launchpad account [[https://help.ubuntu.com/community/GnuPrivacyGuardHowto]] (good info on developer.ubuntu.com)
Line 40: Line 38:
== Ubuntu Studio Developer Tasks ==

 * Create [[UbuntuStudio/Blueprints|Blueprints]] for each new release, which contain work items that can be assigned to a developer.

 * [[ubuntustudio/testing |Testing]] and [[UbuntuStudio/BugManagement |bug management]]

 * Maintain [[UbuntuStudio/DocumentationDevelopment |documentation]]

 * Update the web site.

 * Keep the list of default Ubuntu Studio applications up to date, and relevant - [[UbuntuStudio/Seeds | Seed Management]]

 * Design application categories and documentation to follow a [[UbuntuStudio/Workflows | workflow]] based format, so that users who want to do a specific task are easily led to relevant applications.

 * Test and tweak the system to find out how performance can be improved for various workflows.

 * Look at revamping ubuntustudio-controls to let the user more easily manage the system, without having to edit files manually, or using the terminal to pass commands (realtime privilege, adjusting rtirq - restarting, etc..)

 * Investigate the possibility of creating an application that helps the user more easily find tools for workflow specific tasks. Possibly a custom panel.
Line 79: Line 57:
== Team Structure ==
Line 81: Line 58:
By keeping a clear team structure it is easy to keep track of who is doing what, and whom to ask about specific topics.
Line 83: Line 59:
 * [[https://wiki.ubuntu.com/UbuntuStudio/TeamStructure | Team Structure]]

== Developer Reference ==

 * [[UbuntuStudio/ManagingBlueprints| Managing Blueprints]] - how to create them, and manage them for each new cycle
 * [[ubuntustudio/testing | Testing]] - rename page, duplicate to [[UbuntuStudio/Testing]]
 * [[UbuntuStudio/BugManagement | Bug Management]] (launchpad account)
 * [[UbuntuStudio/DocumentationDevelopment | Documentation]]
 * [[UbuntuStudio/Backports | Backports]] (ubuntu dev-tools)
 * [[UbuntuStudio/StableReleaseUpdates | Stable Release Updates]]
 * [[UbuntuStudio/Packaging | Packaging]]
 * [[UbuntuStudio/Seeds | Seed Management]]
 * [[UbuntuStudio/UploadingToPPA | Uploading to PPA]]
 * [[UbuntuStudio/Artwork | Artwork]]
 * [[UbuntuStudio/SoftwareDevelopment | Software Development]]
 * [[UbuntuStudio/DevelopmentCyclePlanning|Development Cycle Planning]]
 * [[UbuntuStudio/PatchingSourcePackages| Patching Ubuntu Source Packages]]
 * [[UbuntuStudio/UpdateDebianSource|Update a Debian source packiage]]
 * [[UbuntuStudio/SetupLocalIsoBuildServer|Set up local ISO build server]]
 * [[UbuntuStudio/DebDiff|Update a package using debdiff]]

== UbuntuStudio at Launchpad ==

=== Teams ===
 * [[https://launchpad.net/~ubuntustudio]] - open (not active atm)
 * [[https://launchpad.net/~ubuntustudio-bugs]] - open team (not active atm)
 * [[https://launchpad.net/~ubuntustudio-testers]] - open team (not active atm)
 * [[https://launchpad.net/~ubuntustudio-dev]] - closed team (core developer team)
 * [[https://launchpad.net/~ubuntustudio-kernel-team]] - closed team (kernel development team)
 * [[https://launchpad.net/~ubuntustudio-website]] - closed team (has access to the website)
 * '''Add Missing Teams Here...'''

=== Projects ===
 * [[https://launchpad.net/ubuntustudio-project]] - Root project for Ubuntu Studio projects
 * [[https://launchpad.net/ubuntustudio]] - The Ubuntu Studio Project
 * [[https://launchpad.net/ubuntustudio-resources]]
 * [[https://launchpad.net/ubuntustudio-kernel-team]]
 * [[https://launchpad.net/ubuntustudio-website]]
 * [[https://launchpad.net/ubuntustudio-artwork]]
 * [[https://launchpad.net/ubuntustudio-controls]]
 * [[https://launchpad.net/ubuntustudio-default-settings]]

== Documentation Resources ==

 * [[http://www.debian.org/doc/devel-manuals|Debian Development Manuals]]

Under Construction

Contents

  1. Whiteboard
  2. The purpose of Ubuntu Studio:
  3. Ubuntu Studio Development Schedule
  4. Setup Developer Environment
  5. Information Channels

UbuntuStudio/DeveloperDocumentation/Scratchpad

Whiteboard

  • Add vocabulary list (words like upstream, SRU, etc)

  • Ubuntu membership and benefits - https://wiki.ubuntu.com/Membership

  • Create page(s) about the relationship between Debian / Ubuntu / Ubuntu Studio packages. With hints on what to do, and when to do it when wanting to change a package.

use, standard announcement verbiage, and links to various resources like banners/other graphics

The purpose of Ubuntu Studio:

1.

Provide a desktop base suitable for multimedia production work

2.

Provide system performance needed for multimedia applications

3.

Include relevant and up to date applications that cover all multimedia workflows

4.

Provide documentation for users that covers every aspect of linux multimedia

5.

Provide various tools (application/documentation) to make system management easy for non-hackers

6.

Report/adress bugs/issues/ideas upstream to Ubuntu -> Debian -> Software Developers to improve applications and packages

Ubuntu Studio Development Schedule

UbuntuDevelopment/ReleaseProcess - The Ubuntu Release Process

Setup Developer Environment

UbuntuStudio/SetupDeveloperEnvironment

Information Channels

These are all the channels and methods used for communication within the Ubuntu Studio development community.

IRC at irc.freenode.net

  • #ubuntustudio-devel
  • #ubuntustudio (user channel)

IRC chatting is the quickest and most common communication method used in Ubuntu Studio development.

* IRC HowTo - for those not familiar with IRC

Mail lists

CategoryUbuntuStudio CategoryUbuntuStudioDev

UbuntuStudio/DeveloperDocumentation (last edited 2015-08-21 09:45:06 by 83)