[ubuntu-studio-devel] Feature Spec Discussion: Workflow Categorization
rossgammon68 at gmail.com
Wed Jun 25 21:34:07 UTC 2014
Okay - no takers so far. So here goes for an attempt at defining
categories for Sound/Audio applications (the easiest one to start on):
Application to record audio (single or multi-track).
Do we need to differentiate between single & multi-track?
Setting levels and using signal processing on individual tracks.
Should we have a separate tag for signal processing?
This is a big category that includes anything that has midi
functionality (or an app relating to midi).
A virtual or software instrument (synthesiser).
An application or plugin that outputs audio when receiving data control
Neither Debtags nor Freedesktop have this category.
Should we have a separate tag for plugins?
This debtag is not explained. I suppose it could be intended for file
compression (e.g. wav > mp3). The Freedesktop category is for
compressing data (but not normally in the Audio category). Do we need
Application to play audio files.
Application that can record, edit, or play back audio using note and
performance information (typically midi but also audio in the case of a
Do we need to differentiate between DAWs & midi sequencers?
Freedesktop do not have this category. Do we need it?
Application to edit audio/video files.
No debtag exists for this. Does "sequencer" cover it?
Application to burn a disc.
Debtag not in "sound" facet (video also?). Request a new facet, or use
the "hardware" one?
Other missing categories?:
- effects/signal processing
- plugin hosts?
- radio (e.g. recording/streaming podcasts, running radio station)
- notation/scores (in publishing category?)
- Coding/Programming (e.g. Pure Data/Supercollider/CSound)
- Looping (is this under sequencing?)
- Sampling (under recording?)
- Soundfont (or is this under instrument?)
- Patching (or is this too specific)
Which of the "other missing categories" are important? Anything else
missing? Suggestions on terminology? Please note that Debtags are to
help search for packages that match a search-term and therefore the more
descriptive tags we have the better. On the other hand, the freedesktop
categories define where the application appears in the menu. Therefore
the categories are restricted/reserved (although we can add new ones
prefixed with an "X-" indicating an extension).
I know it is hard to comment on a table, so I will start by expanding
the following page on the wiki (to also include debtags) and plonking
the table there. This should allow easier contributions.
But any comments before I do that will be gratefully received.
On 05/18/2014 12:19 PM, Kaj Ailomaa wrote:
> # Workflow Categorization for
> Before we do any technical implementation of workflow categorization, we
> need to define a set of workflows that we want to support. Some work on
> that has been started here
> The defined workflows would serve as basis for our package selection
> process. But, could also be of great help in other areas, such as when
> searching for applications in an installer (if the packages are tagged
> with these workflows, and they tags are searchable).
> Also, the submenus in our menu could be populated directly from such
> The exact names aren't as importad in the first phase of defining the
> workflows. Once the workflows are defined, I suggest we start using
> debtags and freedesktop categories to name the workflows, and create new
> debtags and freedesktop categories for missing ones.
> debtags - https://wiki.debian.org/Debtags
> freedekstop categories -
> In order to do that, we will need to work with upstream. The benefit in
> doing so is that the work we do becomes available on all Debian based
> distros, and in the case with freedesktop categories - also in the whole
> of Linux audio world.
> # freedesktoop categories explained
> Freedesktop categories are used in .desktop files found in
> /usr/share/applications/, and are used for creating a menu structure in
> DEs that still use menus, such as KDE, LXDE and Xubuntu.
> The menus aren't strictly created using freedesktop categories, and in
> our case with ubuntustudio-menu, the structure is very much customized.
> By using freedesktop categories we could instead automate the build of
> the menu, and not place applications in correct categories one by one.
> Here's a list of all standard categories
> # debtags explained
> debtags are potentially useful when searching or browsing for packages.
> Each package can have multiple tags. Read more about debtags here
> Debian packages use debtags to fine tune categorization. But, not all
> packages are currently using a rich set of correct debtags.
> Debtags for the Debian Multimedia Blend packages can be edited here
> (select a task, and for the package, select “edit debtags”)
> To see debtags locally, install the package debtags and use this command
> (replace <package> with something that you have installed):
> debtags show <package>
> WORKITEMS for workflow categorization:
> So, I propose we:
> * Define a set of workflow categories we want to support in our package
> selection process
> * Assemble all debtags and freedesktop categories that relate to our
> workflows into a list.
> * Define new ones, if needed, and implement them upstrean.
> Here's a list of sections for Ubuntu trusty packages
> This is a fair bit of work, but will make further work a lot easier.
> Tags could be used in package installers (such as
> ubuntustudio-installer), while freedesktop categories make it easier to
> structure menus or search for applications in non-menu based gui shells,
> such as unity or gnome.
> Any takers?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ubuntu-studio-devel