DeveloperDocumentation
Size: 5471
Comment:
|
Size: 5492
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 66: | Line 66: |
* [[UbuntuStudio/ManagingBlueprints]] - how to create them, and manage them for each new cycle | * [[UbuntuStudio/ManagingBlueprints| Managing Blueprints]] - how to create them, and manage them for each new cycle |
Whiteboard
- Add vocabulary list (words like upstream, SRU, etc)
- public relations - list of places to make announcements, hashtags to
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 Developer Tasks
Create Blueprints for each new release, which contain work items that can be assigned to a developer.
Maintain documentation
- Update the web site.
Keep the list of default Ubuntu Studio applications up to date, and relevant - Seed Management
Design application categories and documentation to follow a 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.
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
ubuntu-studio-users mail list - user mail list
ubuntu-studio-devel mail list - general development discussion
ubuntustudio-bugs mail list - not active atm
ubuntustudio-testing list - A place where to post testing results
Team Structure
By keeping a clear team structure it is easy to keep track of who is doing what, and whom to ask about specific topics.
Developer Reference
Managing Blueprints - how to create them, and manage them for each new cycle
Bug Management (launchpad account)
Backports (ubuntu dev-tools)
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)
Projects
https://launchpad.net/ubuntustudio-project - Root project for Ubuntu Studio projects
https://launchpad.net/ubuntustudio - The Ubuntu Studio Project
Documentation Resources
UbuntuStudio/DeveloperDocumentation (last edited 2015-08-21 09:45:06 by 83)