diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/20101013/001137.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/20101013/001137.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101013/001137.html | 103 |
1 files changed, 103 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101013/001137.html b/zarb-ml/mageia-dev/20101013/001137.html new file mode 100644 index 000000000..6dc7a0b14 --- /dev/null +++ b/zarb-ml/mageia-dev/20101013/001137.html @@ -0,0 +1,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é</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 écrit : +><i> On Wed, Oct 13, 2010 at 06:50, Marc Paré<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">marc at marcpare.com</A>> wrote: +</I>><i> +</I>>><i> Let the user then assume that responsibility/liability. +</I>>><i> This is where, I consider the "easy urpmi" served its purpose well. It +</I>>><i> installed repos where the available software that most users would need was +</I>>><i> made available, but this again was by user choice. +</I>>><i> +</I>><i> I don't really see how this would "fix" the issue; by using a +</I>><i> third-party repository (plf or through easy urpmi) you just move the +</I>><i> concerns to another provider: +</I>><i> - if the user is liable anyway, having a single or several providers +</I>><i> doesn't matter; +</I>><i> - if the user is not liable anyway, having several providers only +</I>><i> moves the liability from one provider to the other one. +</I>><i> +</I>><i> This particular point, about _patented_ software is a tricky one +</I>><i> indeed. Dealing with local/international laws is tricky. Especially +</I>><i> when both change over time. +</I>><i> +</I>><i> However, first point is not to mix different issues here: +</I>><i> - supported software and not-supported (and what means "supported") +</I>><i> - free vs. non-free/proprietary software (as in FSF/OSI definitions) +</I>><i> - gratis vs. paid software +</I>><i> - for non-free software, distribution/usage cases may be tricky +</I>><i> (skype, opera for instance) +</I>><i> - software implementation/distribution that violates/have to comply +</I>><i> specific laws (encryption, DRMs) +</I>><i> - for patented software/methods, implementation/distribution/usage +</I>><i> cases are tricky as well (a patent may or may not block you from using +</I>><i> the method, depends on who holds the patent and for what purpose). +</I>><i> - maybe more with more details; Anssi pretty much defined categories +</I>><i> in his first message here. +</I>><i> +</I>><i> We definitely can't say bluntly "let's ignore all laws because we +</I>><i> can't enforce them all". We must define our policies for what goes in +</I>><i> Mageia repositories, what stays out, what goes out (and why). These +</I>><i> policies must align with (and be part of) Mageia values and direction. +</I>><i> +</I>><i> +</I>><i> Cheers, +</I>><i> +</I>><i> Romain +</I>><i> +</I>A good summary of the issues involved + +- André (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> |