summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101218/001780.html
blob: 05d02b365c7a2c247ee320279a3f1cb037b62662 (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
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] mageia sound tasks
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mageia%20sound%20tasks&In-Reply-To=%3CAANLkTik%3DphC3m9YyBJYpzubTVnMCzjW%3Dj0ozJ4r_6ZDC%40mail.gmail.com%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="001778.html">
   <LINK REL="Next"  HREF="001781.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] mageia sound tasks</H1>
    <B>SaschaS</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mageia%20sound%20tasks&In-Reply-To=%3CAANLkTik%3DphC3m9YyBJYpzubTVnMCzjW%3Dj0ozJ4r_6ZDC%40mail.gmail.com%3E"
       TITLE="[Mageia-dev] mageia sound tasks">ungleichklang at gmail.com
       </A><BR>
    <I>Sat Dec 18 10:03:36 CET 2010</I>
    <P><UL>
        <LI>Previous message: <A HREF="001778.html">[Mageia-dev] mageia sound tasks
</A></li>
        <LI>Next message: <A HREF="001781.html">[Mageia-dev] mageia sound tasks
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1780">[ date ]</a>
              <a href="thread.html#1780">[ thread ]</a>
              <a href="subject.html#1780">[ subject ]</a>
              <a href="author.html#1780">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>So I see basically that we need a guidline on how mageia deals with Spinoffs
first.

If all task are in the repos, I can understand those who say that there are
to many task.
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.
The a

2010/12/18 Daniel Kreuter &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">daniel.kreuter85 at googlemail.com</A>&gt;

&gt;<i>
</I>&gt;<i>
</I>&gt;<i> On Sat, Dec 18, 2010 at 7:04 AM, herman &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">herman at aeronetworks.ca</A>&gt; wrote:
</I>&gt;<i>
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> On Fri, 2010-12-17 at 15:30 -0700, Frank Kober wrote:
</I>&gt;&gt;<i> &gt; I'm here for sure. Doing subtasks was one of the ideas coming in from
</I>&gt;&gt;<i> several linuxmao.org members. This idea got rejected from the mdv people
</I>&gt;&gt;<i> with the argument that there are already too many task metapackages. It was
</I>&gt;&gt;<i> difficult to get a common opinion on it by the musicians anyway, but finally
</I>&gt;&gt;<i> the most useful division would be a bit in the sense of the current
</I>&gt;&gt;<i> task-sound-studio, i.e. use cases: Audio recording, Audio synthesis and
</I>&gt;&gt;<i> composing, live tools (loopers, etc..), sounds (soundfonts in particular
</I>&gt;&gt;<i> which are large data files), video?.
</I>&gt;&gt;<i> &gt; But you will see that it is not so easy to make coherent and useful
</I>&gt;&gt;<i> subsets. Another example would be the ubuntu studio grouping.
</I>&gt;&gt;<i> &gt;
</I>&gt;&gt;<i> &gt; I think there should be just a clear separation of music consumer tasks
</I>&gt;&gt;<i> and music creation tasks, and already the latter includes some of the first
</I>&gt;&gt;<i> one...
</I>&gt;&gt;<i> IMHO the most important thing is to make a basic package that works.
</I>&gt;&gt;<i> The user can then add other things they like.  As things are, it is very
</I>&gt;&gt;<i> difficult for an ordinary mortal to make a working sound system by
</I>&gt;&gt;<i> installing individual packages.
</I>&gt;&gt;<i>
</I>&gt;&gt;<i>
</I>&gt;<i> The basic music tasks such as soundserver (pulse or alsa), music/video
</I>&gt;<i> player should already be in the main distribution included like we know
</I>&gt;<i> already from existing distributions.
</I>&gt;<i> What I would like is a task-package which includes everything needed for a
</I>&gt;<i> working multimedia computer such like mpd for music streaming, and something
</I>&gt;<i> similar for video streaming over a network.
</I>&gt;<i>
</I>&gt;<i> And maybe we can also make a similar task for the creators out there?
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i> --
</I>&gt;<i> Mit freundlichen Gr&#252;&#223;en
</I>&gt;<i>
</I>&gt;<i> Greetings
</I>&gt;<i>
</I>&gt;<i> Daniel Kreuter
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i>
</I>-------------- next part --------------
An HTML attachment was scrubbed...
URL: &lt;/pipermail/mageia-dev/attachments/20101218/880f7aaa/attachment-0001.html&gt;
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="001778.html">[Mageia-dev] mageia sound tasks
</A></li>
	<LI>Next message: <A HREF="001781.html">[Mageia-dev] mageia sound tasks
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1780">[ date ]</a>
              <a href="thread.html#1780">[ thread ]</a>
              <a href="subject.html#1780">[ subject ]</a>
              <a href="author.html#1780">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>