summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20101218/cfca6c54/attachment.html
blob: c5ed04e17e28d76b68e628431c7652bf3f65dc6b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
.... sorry, my little son found the send button ....<br><br>That way we could provide something for nearly every need.<br>We even could offer separate kernels.<br><br>But first lets see how we can integrate the idea of spinoffs into the mageia projekt.<br>
<br>greetings, Sascha<br><br><div class="gmail_quote">2010/12/18 SaschaS <span dir="ltr">&lt;<a href="mailto:ungleichklang@gmail.com">ungleichklang@gmail.com</a>&gt;</span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
So I see basically that we need a guidline on how mageia deals with Spinoffs first.<br><br>If all task are in the repos, I can understand those who say that there are to many task.<br>If the spinoffs are handled as separate projects, we could provide a cusom .iso and different sound-tasks, that people download from the spinoff page.<br>

The a<br><br><div class="gmail_quote">2010/12/18 Daniel Kreuter <span dir="ltr">&lt;<a href="mailto:daniel.kreuter85@googlemail.com" target="_blank">daniel.kreuter85@googlemail.com</a>&gt;</span><div><div></div><div class="h5">
<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div><br><br><div class="gmail_quote">On Sat, Dec 18, 2010 at 7:04 AM, herman <span dir="ltr">&lt;<a href="mailto:herman@aeronetworks.ca" target="_blank">herman@aeronetworks.ca</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
On Fri, 2010-12-17 at 15:30 -0700, Frank Kober wrote:<br>
&gt; I&#39;m here for sure. Doing subtasks was one of the ideas coming in from several <a href="http://linuxmao.org" target="_blank">linuxmao.org</a> members. This idea got rejected from the mdv people with the argument that there are already too many task metapackages. It was difficult to get a common opinion on it by the musicians anyway, but finally the most useful division would be a bit in the sense of the current task-sound-studio, i.e. use cases: Audio recording, Audio synthesis and composing, live tools (loopers, etc..), sounds (soundfonts in particular which are large data files), video?.<br>



&gt; But you will see that it is not so easy to make coherent and useful subsets. Another example would be the ubuntu studio grouping.<br>
&gt;<br>
&gt; I think there should be just a clear separation of music consumer tasks and music creation tasks, and already the latter includes some of the first one...<br>
IMHO the most important thing is to make a basic package that works.<br>
The user can then add other things they like.  As things are, it is very<br>
difficult for an ordinary mortal to make a working sound system by<br>
installing individual packages.<br>
<br>
</blockquote></div><br></div></div>The basic music tasks such as soundserver (pulse or alsa), music/video player should already be in the main distribution included like we know already from existing distributions.<br>What I would like is a task-package which includes everything needed for a working multimedia computer such like mpd for music streaming, and something similar for video streaming over a network.<br>


<br>And maybe we can also make a similar task for the creators out there?<div><div></div><div><br clear="all"><br>-- <br>Mit freundlichen Grüßen<br><br>Greetings<br><br>Daniel Kreuter<br><br><br><br>
</div></div></blockquote></div></div></div><br>
</blockquote></div><br>