PreliminaryBlueprintsDraft1304

Revision 29 as of 2012-10-25 08:21:14

Clear message

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)
  • public relations - list of places to make announcements, hashtags to

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

  • testing documentation - create docs that walk new people into

helping with testing

  • 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 (something like this? https://wiki.ubuntu.com/UbuntuStudio/DeveloperDocumentation#The_purpose_of_Ubuntu_Studio)

  • user docs - in the wiki or the website, we should pick one and do it (currently being developed at the community wiki)
  • dev docs - reconcile "contribute to development" and kaj's pages (When developer documentation is mature enough, integrate it with the support section on the website)
  • 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? (covered by user docs, and the possible HW matrix)

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

  • Startup System Check Script - Idea: set audio device for jack at first login (will require persistent card selection, based on name - how does Pulseaudio do it?)
  • Startup System Check Script - "first start" notifications - can point out help/faq doc, tutorials,

walkthrough, etc locations or important settings

  • Startup System Check Script - Check the system for settings needed for good performance. If something is lacking, send notification.

UbuntuStudioControls

  • Ubuntu Studio Controls - Option to keep it in the systray with a dropdown menu
  • Ubuntu Studio Controls - Administer user realtime privilege (not only currently logged in user)
  • Ubuntu Studio Controls - Killall jack button, killall pulseaudio button
  • Ubuntu Studio Controls - Make settings for graphics and videos (as done here)

WorkflowSuite

  • workflow manager - (for installing/removing work flows)
  • workflow assistant - (for starting applications within a work flow)
  • workflowpanel - UI changes depending on workflow in use

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
  • multihead - improve the persistance or document how to fix it

Q-OldReleaseMaintenance

  • backports team - start backporting to precise