summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101013/001137.html
blob: 6dc7a0b143deb1a33fecf9c02f85f22ff9468204 (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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Mageia repository sections, licenses, restrictions, firmware etc
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mageia%20repository%20sections%2C%20licenses%2C%20restrictions%2C%0A%20firmware%20etc&In-Reply-To=%3C4CB5C812.7060603%40laposte.net%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="001128.html">
   <LINK REL="Next"  HREF="001126.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Mageia repository sections, licenses, restrictions, firmware etc</H1>
    <B>andr&#233;</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mageia%20repository%20sections%2C%20licenses%2C%20restrictions%2C%0A%20firmware%20etc&In-Reply-To=%3C4CB5C812.7060603%40laposte.net%3E"
       TITLE="[Mageia-dev] Mageia repository sections, licenses, restrictions, firmware etc">andr55 at laposte.net
       </A><BR>
    <I>Wed Oct 13 16:54:10 CEST 2010</I>
    <P><UL>
        <LI>Previous message: <A HREF="001128.html">[Mageia-dev] Mageia repository sections, licenses, restrictions, firmware etc
</A></li>
        <LI>Next message: <A HREF="001126.html">[Mageia-dev] Mageia repository sections, licenses, restrictions, firmware etc
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1137">[ date ]</a>
              <a href="thread.html#1137">[ thread ]</a>
              <a href="subject.html#1137">[ subject ]</a>
              <a href="author.html#1137">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Romain d'Alverny a &#233;crit :
&gt;<i> On Wed, Oct 13, 2010 at 06:50, Marc Par&#233;&lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">marc at marcpare.com</A>&gt;  wrote:
</I>&gt;<i>    
</I>&gt;&gt;<i> Let the user then assume that responsibility/liability.
</I>&gt;&gt;<i> This is where, I consider the &quot;easy urpmi&quot; served its purpose well. It
</I>&gt;&gt;<i> installed repos where the available software that most users would need was
</I>&gt;&gt;<i> made available, but this again was by user choice.
</I>&gt;&gt;<i>      
</I>&gt;<i> I don't really see how this would &quot;fix&quot; the issue; by using a
</I>&gt;<i> third-party repository (plf or through easy urpmi) you just move the
</I>&gt;<i> concerns to another provider:
</I>&gt;<i>   - if the user is liable anyway, having a single or several providers
</I>&gt;<i> doesn't matter;
</I>&gt;<i>   - if the user is not liable anyway, having several providers only
</I>&gt;<i> moves the liability from one provider to the other one.
</I>&gt;<i>
</I>&gt;<i> This particular point, about _patented_ software is a tricky one
</I>&gt;<i> indeed. Dealing with local/international laws is tricky. Especially
</I>&gt;<i> when both change over time.
</I>&gt;<i>
</I>&gt;<i> However, first point is not to mix different issues here:
</I>&gt;<i>   - supported software and not-supported (and what means &quot;supported&quot;)
</I>&gt;<i>   - free vs. non-free/proprietary software (as in FSF/OSI definitions)
</I>&gt;<i>   - gratis vs. paid software
</I>&gt;<i>   - for non-free software, distribution/usage cases may be tricky
</I>&gt;<i> (skype, opera for instance)
</I>&gt;<i>   - software implementation/distribution that violates/have to comply
</I>&gt;<i> specific laws (encryption, DRMs)
</I>&gt;<i>   - for patented software/methods, implementation/distribution/usage
</I>&gt;<i> cases are tricky as well (a patent may or may not block you from using
</I>&gt;<i> the method, depends on who holds the patent and for what purpose).
</I>&gt;<i>   - maybe more with more details; Anssi pretty much defined categories
</I>&gt;<i> in his first message here.
</I>&gt;<i>
</I>&gt;<i> We definitely can't say bluntly &quot;let's ignore all laws because we
</I>&gt;<i> can't enforce them all&quot;. We must define our policies for what goes in
</I>&gt;<i> Mageia repositories, what stays out, what goes out (and why). These
</I>&gt;<i> policies must align with (and be part of) Mageia values and direction.
</I>&gt;<i>
</I>&gt;<i>
</I>&gt;<i> Cheers,
</I>&gt;<i>
</I>&gt;<i> Romain
</I>&gt;<i>    
</I>A good summary of the issues involved

- Andr&#233; (andre999)
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="001128.html">[Mageia-dev] Mageia repository sections, licenses, restrictions, firmware etc
</A></li>
	<LI>Next message: <A HREF="001126.html">[Mageia-dev] Mageia repository sections, licenses, restrictions, firmware etc
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#1137">[ date ]</a>
              <a href="thread.html#1137">[ thread ]</a>
              <a href="subject.html#1137">[ subject ]</a>
              <a href="author.html#1137">[ 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>