PreliminaryBlueprintsDraft1304

Differences between revisions 43 and 44
Revision 43 as of 2012-10-25 14:06:18
Size: 5360
Editor: h-161-160
Comment:
Revision 44 as of 2012-10-25 16:00:22
Size: 5398
Editor: h-161-160
Comment:
Deletions are marked like this. Additions are marked like this.
Line 53: Line 53:
 * list of places to make announcements, hashtags to  * --(list of places to make announcements, hashtags to)-- ADDED
Line 56: Line 56:
 * Find ways to attract developers to Ubuntu Studio
 * Start making routine news postings on social channels/websites/mail lists
 *  --(Find ways to attract developers to Ubuntu Studio)-- ADDED
 *  --(Start making routine news postings on social channels/websites/mail lists)-- ADDED

Assembling blueprints here for the 13.04 cycle.

Resources

Blueprints Draft for 13.04

R-Documentation

  • 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 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
  • 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
  • user docs - in the wiki or the website, we should pick one and do it (currently being developed at the community wiki)

  • Document all steps of Ubuntu Studio development
  • Create reference for all development tasks
  • Create database of all Ubuntu Studio related sources
  • 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)

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? (covered by user docs, and the possible HW matrix)

Public Relations

  • list of places to make announcements, hashtags to ADDED

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

  • Find ways to attract developers to Ubuntu Studio ADDED

  • Start making routine news postings on social channels/websites/mail lists ADDED

R-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
  • Add audio group as a default group for newly created users (not only the first user)

Video

  • video: Add a screencast application

R-PerformanceTesting (used to be "performance")

Testing system tweaks for the different workflows

  • Finish audio-testing script (ailo)

R-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

  • Make wubi.exe also support Ubuntu Studio (bug #1070682)

R-Artwork

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

R-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)

WorkflowApplication

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

R-Misc

  • Decide how to handle ubuntustudio-bugs team and mail list
  • 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 in the desktop main menu TODO: VERIFY THIS ISN'T DONE ALREADY OR FLESH IT OUT MORE
  • multihead - improve the persistance or document how to fix it

R-OldReleaseMaintenance

  • backports team - start backporting to precise

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