PreliminaryBlueprintsDraft1304

Differences between revisions 21 and 22
⇤ ← Revision 21 as of 2012-10-24 05:46:13 →
Size: 2359
Editor: h-161-160
Comment:
← Revision 22 as of 2012-10-25 07:57:06 → ⇥
Size: 4357
Editor: 80
Comment:
Deletions are marked like this. Additions are marked like this.
Line 28: Line 28:
 * testing documentation - create docs that walk new people into
helping with testing

 * hardware testing/documentation - we should prioritize which hardware
we want to support, test it, fix it (if required and possible), and
document all. do we support firewire? usb?

 * tutorial videos - identify a select few and make them and host on youtube

 * tutorials/walkthroughs - can be videos, libre office, html formats.
ship on image. for important, core items.

 * help/faq shipped on image - can be text file or html or whatever

 * mission statement - create one that define and documents target
audience, use cases, hardware supported

 * public relations - list of places to make announcements, hashtags to
use, standard announcement verbiage, and links to various resources
like banners/other graphics

 * user docs - in the wiki or the website, we should pick one and do it

 * dev docs - reconcile "contribute to development" and kaj's pages
Line 34: Line 59:
 * default jack settings - set reasonable, yet sane, default jack settings
 * audio plugins - we ship a large amount, can this be cleaned up
 * audio plugins - can we create a list of popular ones with example settings
Line 39: Line 68:
== Q-Performance == == Q-Testing (used to be "performance") ==
Line 47: Line 76:
 * ubiquity plugin - allows users to choose which packages to install
during installation
Line 52: Line 83:
== Q-StartupSystemCheckScript == == Q-SoftwareDevelopment ==
Line 54: Line 85:
 * Idea: set audio device for jack at first login (will require persistent card selection, based on name - how does Pulseaudio do it?)  * StartupSystemCheckScript: Idea: set audio device for jack at first login (will require persistent card selection, based on name - how does Pulseaudio do it?)
 * StartupSystemCheckScript: "first start" notifications - can point out help/faq doc, tutorials,
walkthrough, etc locations or important settings
Line 56: Line 89:
== Q-UbuntuStudioControls ==  * UbuntuStudioControls: Option to keep it in the systray with a dropdown menu
 * UbuntuStudioControls: Administer user realtime privilege (not only currently logged in user)
 * UbuntuStudioControls: Killall jack button, killall pulseaudio button
 * UbuntuStudioControls: Make settings for graphics and videos (as done [[http://www.rileybrandt.com/2012/07/31/linux-photo-1/|here]])
Line 58: Line 94:
 * Option to keep it in the systray with a dropdown menu
 * Administer user realtime privilege (not only currently logged in user)
 * Killall jack button, killall pulseaudio button
 * Make settings for graphics and videos (as done [[http://www.rileybrandt.com/2012/07/31/linux-photo-1/|here]])		  * workflow manager: (for installing/removing work flows)
Line 63: Line 96:
== Q-Workflowpanel ==  * workflow assistant: (for starting applications within a work flow)
Line 70: Line 104:
 * lowlatency kernel - finish coordination with UKT and start maintaining it (underway)
 * start having meetings
 * "support" sub-menu TODO: VERIFY THIS ISN'T DONE ALREADY OR FLESH IT OUT MORE
 * backports team - start backporting to precise
 * multihead - improve the persistance or document how to fix it

Assembling blueprints here for the 13.04 cycle.

Resources

Blueprints Draft for 13.04

Q-Documentation

  • User documentation
    • Migrating from other OS's (Windows, Mac)
    • Hardware Support (possible hardware matrix for audio devices)
    • System configuration (drivers, codecs, monitor calibration)
    • Workflows
      • Audio
      • Graphics
      • Video
      • Photography
      • Publishing
  • Developer Documentation
  • Add links to Ubuntu Studio social channels somewhere (at the website and the wiki) (known channels are Ubuntu Studio at g+ and facebook)
  • testing documentation - create docs that walk new people into

helping with testing

  • hardware testing/documentation - we should prioritize which hardware

we want to support, test it, fix it (if required and possible), and document all. do we support firewire? usb?

  • tutorial videos - identify a select few and make them and host on youtube
  • tutorials/walkthroughs - can be videos, libre office, html formats.

ship on image. for important, core items.

  • help/faq shipped on image - can be text file or html or whatever
  • mission statement - create one that define and documents target

audience, use cases, hardware supported

  • public relations - list of places to make announcements, hashtags to

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

  • user docs - in the wiki or the website, we should pick one and do it
  • dev docs - reconcile "contribute to development" and kaj's pages

Q-Workflows

Audio

  • Possibly add LMMS to seeds
  • Possibly replace XFCE mixer with qasmixer (or just adding it to the mix)
  • Decide whether to add volti (volume control in systray for alsa)
  • default jack settings - set reasonable, yet sane, default jack settings
  • audio plugins - we ship a large amount, can this be cleaned up
  • audio plugins - can we create a list of popular ones with example settings

Video

  • Add a screencast application

Q-Testing (used to be "performance")

  • Finish audio-testing script (ailo)

Q-LiveDVD

  • Fix upgrade so that photography and publishing metas are included (LP #1066401)
  • SRU the above to 12.10
  • ubiquity plugin - allows users to choose which packages to install

during installation

Q-Artwork

  • Ask for user contributed artwork on the website (wallpaper at the very least)

Q-SoftwareDevelopment

  • StartupSystemCheckScript: Idea: set audio device for jack at first login (will require persistent card selection, based on name - how does Pulseaudio do it?)

  • StartupSystemCheckScript: "first start" notifications - can point out help/faq doc, tutorials,

walkthrough, etc locations or important settings

  • UbuntuStudioControls: Option to keep it in the systray with a dropdown menu

  • UbuntuStudioControls: Administer user realtime privilege (not only currently logged in user)

  • UbuntuStudioControls: Killall jack button, killall pulseaudio button

  • UbuntuStudioControls: Make settings for graphics and videos (as done here)

  • workflow manager: (for installing/removing work flows)
  • workflow assistant: (for starting applications within a work flow)

Q-Misc

  • Decide how to handle ubuntustudio-bugs team and mail list
  • Add audio group as a default group for newly created users (not only the first user)
  • Change GRUB config to label our partition a Ubuntu Studio with the kernel type (generic or lowlatency)
  • lowlatency kernel - finish coordination with UKT and start maintaining it (underway)
  • start having meetings
  • "support" sub-menu TODO: VERIFY THIS ISN'T DONE ALREADY OR FLESH IT OUT MORE
  • backports team - start backporting to precise
  • multihead - improve the persistance or document how to fix it

UbuntuStudio/PreliminaryBlueprintsDraft1304 (last edited 2012-10-27 15:11:25 by h-161-160)