Debian Multimedia Menus (discussion)

[rosea.grammostola]

On 12/24/2010 01:53 AM, Jonas Smedegaard wrote:
> Great that you put attention to this!

Thanks for your 0.02 ct
>
> An extra menu package dosn't feel very Debian to me, though.  Debian 
> logic is to propose a change to Debian Policy to have the improved 
> organisation apply universally, not only when a certain package is 
> installed.
>
>    aptitude install less debian-policy
>    zless /usr/share/doc/debian-policy/menu-policy.txt.gz
>
> That said, nothing stops us from *both* work on improving the official 
> Debian Menu System *and* some package with a custom tweak tied to one 
> or more specific desktop menu systems.  Same initial discussion that 
> you've now opened apply to both. :-)

OK

>
>
>> I split up Multimedia (players) and Sound & Video (production)
>
> +1

Some multimedia players (aqualung for instance) have already a category 
'Player' in the desktop file afaik.

>
>
>> At this point I have 7 extra entries in Sound & Video
>>
>>  1. Audio Editing (Editing, Mixing, Mastering: Audacity, jack-rack,
>>     lv2rack, guitarix etc )
>>  2. JACK (Jack and Alsa tools like qjackctl, japa, jack_mixer and
>>     software mixers for alsa audio cards for example)
>>  3. MIDI (Midi tools like Vkeybd, qsynth)
>>  4. Musician (Musescore notation editor, solfege, Chordata, gtklick 
>>     etc)
>>  5. Recording (DAW: ardour, qtractor)
>>  6. Synth (phasex, yoshimi, puredata, Qutecsound etc.)
>>  7. Video Editing (pitivi, xjadeo, kino etc)
>>
>> I tried to keep it as simple as possible, not to many entries and 
>> pretty broad areas cause every Debian Audio production app should be 
>> able to be entered in a certain entry...
>
> Let's use the same format as the Debian Menu System - both to ease 
> passing the discussion to the debian-policy@ list later, and to help 
> ensure we are talking about same things (e.g. where exactly in the 
> menu hierarchy each section is placed, and what is descriptive text):
>
> Applications/Sound & Video
>     Sound & Video production
>
>     Applications/Sound & Video/Audio Editing
>         Editing, Mixing, Mastering
>
>         Examples: audacity, jack-rack, lv2rack, guitarix
>
>     Applications/Sound & Video/JACK
>         Jack and Alsa tools
>
>         Examples: qjackctl, japa, jack_mixer
>     Applications/Sound & Video/MIDI
>         Midi tools
>
>         Examples: vkeybd, qsynth
>
>     Applications/Sound & Video/Musician
>         Music score composition, and live musician training tools
>
>         Examples: musescore, solfege, chordata, gtklick
>     Applications/Sound & Video/Recording
>         Digital Audio Workstation (DAW) and harddisk recording (HDR)
>
>         Examples: ardour, qtractor
>
>     Applications/Sound & Video/Synth
>         Syntesizers and programmatic sound processing
>
>         Examples: phasex, yoshimi, puredata, qutecsound
>
>     Applications/Sound & Video/Video Editing
>
>         Examples: pitivi, xjadeo, kino
>     Applications/Multimedia
>         Players
>
>
> I took the liberty to add or extend some descriptive text.  Please 
> double-check that I did not distort your intended meaning of some.

We're talking the same language.

>
>
>> A other thing that has to be thought of, is how this all applies to 
>> other WMs like KDE, XFCE etc. All though, if you create a 
>> DebianMultimedia-menu, people are free to install it or not...
>
> The Debian menu system has plugins for various WMs.  The beauty of 
> this is that if we stick to that, we need not deal with the details of 
> each and every oddball WM menu engine.

Ok nice.

If we decide we want something like this, would you like to contribute 
to this (all though if we decide it, you have no choice I think ;) )

Regards,

\r