summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101013/001128.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20101013/001128.html')
-rw-r--r--zarb-ml/mageia-dev/20101013/001128.html99
1 files changed, 99 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101013/001128.html b/zarb-ml/mageia-dev/20101013/001128.html
new file mode 100644
index 000000000..65a798121
--- /dev/null
+++ b/zarb-ml/mageia-dev/20101013/001128.html
@@ -0,0 +1,99 @@
+<!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=%3CAANLkTim7-81L7tKZUc3r00pt%2Bws-HqWHSFdYoE37nvC0%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="001139.html">
+ <LINK REL="Next" HREF="001137.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Mageia repository sections, licenses, restrictions, firmware etc</H1>
+ <B>Romain d'Alverny</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=%3CAANLkTim7-81L7tKZUc3r00pt%2Bws-HqWHSFdYoE37nvC0%40mail.gmail.com%3E"
+ TITLE="[Mageia-dev] Mageia repository sections, licenses, restrictions, firmware etc">rdalverny at gmail.com
+ </A><BR>
+ <I>Wed Oct 13 11:49:24 CEST 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="001139.html">[Mageia-dev] Mageia repository sections, licenses, restrictions, firmware etc
+</A></li>
+ <LI>Next message: <A HREF="001137.html">[Mageia-dev] Mageia repository sections, licenses, restrictions, firmware etc
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1128">[ date ]</a>
+ <a href="thread.html#1128">[ thread ]</a>
+ <a href="subject.html#1128">[ subject ]</a>
+ <a href="author.html#1128">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>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:
+&gt;<i> Let the user then assume that responsibility/liability.
+</I>&gt;<i> This is where, I consider the &quot;easy urpmi&quot; served its purpose well. It
+</I>&gt;<i> installed repos where the available software that most users would need was
+</I>&gt;<i> made available, but this again was by user choice.
+</I>
+I don't really see how this would &quot;fix&quot; the issue; by using a
+third-party repository (plf or through easy urpmi) you just move the
+concerns to another provider:
+ - if the user is liable anyway, having a single or several providers
+doesn't matter;
+ - if the user is not liable anyway, having several providers only
+moves the liability from one provider to the other one.
+
+This particular point, about _patented_ software is a tricky one
+indeed. Dealing with local/international laws is tricky. Especially
+when both change over time.
+
+However, first point is not to mix different issues here:
+ - supported software and not-supported (and what means &quot;supported&quot;)
+ - free vs. non-free/proprietary software (as in FSF/OSI definitions)
+ - gratis vs. paid software
+ - for non-free software, distribution/usage cases may be tricky
+(skype, opera for instance)
+ - software implementation/distribution that violates/have to comply
+specific laws (encryption, DRMs)
+ - for patented software/methods, implementation/distribution/usage
+cases are tricky as well (a patent may or may not block you from using
+the method, depends on who holds the patent and for what purpose).
+ - maybe more with more details; Anssi pretty much defined categories
+in his first message here.
+
+We definitely can't say bluntly &quot;let's ignore all laws because we
+can't enforce them all&quot;. We must define our policies for what goes in
+Mageia repositories, what stays out, what goes out (and why). These
+policies must align with (and be part of) Mageia values and direction.
+
+
+Cheers,
+
+Romain
+</PRE>
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="001139.html">[Mageia-dev] Mageia repository sections, licenses, restrictions, firmware etc
+</A></li>
+ <LI>Next message: <A HREF="001137.html">[Mageia-dev] Mageia repository sections, licenses, restrictions, firmware etc
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1128">[ date ]</a>
+ <a href="thread.html#1128">[ thread ]</a>
+ <a href="subject.html#1128">[ subject ]</a>
+ <a href="author.html#1128">[ 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>