forked from OpenXT/openxt
-
Notifications
You must be signed in to change notification settings - Fork 0
JIRA Components
Kevin Pearson edited this page Aug 29, 2014
·
51 revisions
TO BE DELETED AFTER NEW JIRA SETUP
Some questions:
- Does our JIRA instance support subcomponents so that we can arrange things hierarchically? A flat list will likely need to be vague to prevent the component list from getting too long.
- Audio
- Build System
- (KP) Added, as this is just as important as the code itself and should be tracked appropriately
- Documentation
- Hardware Support
- Input Devices
- Installer
- [KP] Added, as there are known problems to be tagged against this
- Linux FS
- [KP] This is ambiguous. Should this be Dom0 File System?
- Linux Kernel
- [KP] This is ambiguous. Should this be Dom0 Kernel?
-
Management Policy
- [KP] Not sure what this ever really meant.
- Network
- [KP] Should this be renamed to be specific to NDVM? Otherwise is ambiguous
- Passthrough Devices
- [KP] Added to address direct passthrough, such as GFX/NIC/USB controller
- Security Policy
- [KP] Should this be renamed to be Dom0 Security Policy, should it be broken down?
- Stubdom
- Sync-client
- Synchronizer
- TPM/TXT
- USB
- User Interface
- Video
- [KP] Should this be renamed to something like "Switched Graphics"?
- Windows PV Drivers
Do not edit unless something was missed
- Audio
- Documentation
- Hardware Support
- Input Devices
- Linux FS
- Linux Kernel
- Management Policy
- Network
- Security Policy
- Stubdom
- Sync-client
- Synchronizer
- TPM/TXT
- USB
- User Interface
- Video
- Windows PV Drivers