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/20101210/001692.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/20101210/001692.html')
-rw-r--r-- | zarb-ml/mageia-dev/20101210/001692.html | 149 |
1 files changed, 149 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101210/001692.html b/zarb-ml/mageia-dev/20101210/001692.html new file mode 100644 index 000000000..779504e50 --- /dev/null +++ b/zarb-ml/mageia-dev/20101210/001692.html @@ -0,0 +1,149 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Mirror layout + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout&In-Reply-To=%3CAANLkTi%3DU3%3DAxYJG9AMisYjZW%2BjRZspjFqGR1V2_VkF_C%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="001691.html"> + <LINK REL="Next" HREF="001693.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Mirror layout</H1> + <B>Romain d'Alverny</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout&In-Reply-To=%3CAANLkTi%3DU3%3DAxYJG9AMisYjZW%2BjRZspjFqGR1V2_VkF_C%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Mirror layout">rdalverny at gmail.com + </A><BR> + <I>Fri Dec 10 19:37:38 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001691.html">[Mageia-dev] Mirror layout +</A></li> + <LI>Next message: <A HREF="001693.html">[Mageia-dev] Mirror layout +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1692">[ date ]</a> + <a href="thread.html#1692">[ thread ]</a> + <a href="subject.html#1692">[ subject ]</a> + <a href="author.html#1692">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Fri, Dec 10, 2010 at 19:14, Wolfgang Bornath <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">molch.b at googlemail.com</A>> wrote: +><i> 2010/12/10 Romain d'Alverny <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">rdalverny at gmail.com</A>>: +</I>>><i> +</I>>><i> Ok, but you still take into account SP in your answer. :-p (we would +</I>>><i> have come to that, but the idea was to think about it from a naïve, +</I>>><i> software-patent-free perspective). +</I>><i> +</I>><i> If there were no software patents anywhere what would be the issue of +</I>><i> this discussion? +</I>><i> IMHO it makes no sense to discuss something which does not exist +</I> +It does. Because it helps looking at a problem from a totally +different perspective, build from that, and see the +missing/conflicting pieces when you look back at the full problem (or +as you used to look at it before). Which conflicting/missing pieces +may not be the ones one thought they were. + +><i> I see the strategy in your proposition but: +</I>><i> +</I>><i> 1. We know from the start that there ARE packages with software which +</I>><i> is patented in some countries. So, the "let's start empty and see what +</I>><i> comes up" is already done with. +</I> +Are there issues with it? (looking at my previous check-list, maybe to +improve). If so, yes, let's fill this up. If not, let's leave it alone +in the core. + +I mean, what difference does it make with PLF repositories that are +already mirrored? what differences does it make with Debian stuff that +is already mirrored? do they get cease & desist? do we hear about +this? + +><i> 2. In some countries mirror maintainers can not wait until somebody +</I>><i> raises his hand, there are lawyers who write nice "cease and desist" +</I>><i> letters, attached is a bill you have to pay. In Germany this is called +</I>><i> "Kostenpflichtige Abmahnung"  and has grown to a habit of some +</I>><i> lawyers. +</I> +Then in these cases, two options: + - just do not mirror; and people use mirrors on the borders; + - Mageia (or some related entity) provides legal services about this +(taking responsibility for the hosting or other). + +Why "just do not mirror"? Because, taking the strict statu-quo point +of view regarding the software patent thing, that is "just follow the +most restrictive set of rules", we won't be able to cope with just +medias to separate patented software from non-patented sw. It will be +a matter of tags, because the situation is different from territory to +territory. And there are more than two for that matter. + +><i> Meaning: you can't wait and see what happens, you have to make sure +</I>><i> that it does not happen from the start. +</I> +We can't be sure at all of anything. That's why that's to take a +risk-management attitude, provided what we want to achieve, what +stance we want to take. + +><i> I mean, opinions about software patents set aside for a minute, +</I>><i> software patents are protected by official law in those countries. You +</I>><i> can not break the law on the basis of "let's see what happens". +</I> +Many do. Not only for software, but for everything. For many reasons, +among which can be: the law is broken, the law is becoming obsolete, +people do not enforce it, the law should be changed, etc. + +Well, actually, there are two options: break the law/try it as it is. +Or follow it strictly to demonstrate its absurdity. What I propose +here is a middle-ground some other projects already take. + +With the reasonable attitude to manage cases that _are precisely +identified_ (so we avoid reports such as "this piece of software is +likely to be patented"; point needed is: is it? or not? how, why, by +who, is it valid, is it free, is it enforced, are we noticeable/a +target, does it matter given our size? + +As said before, regarding law on software patents, the situation today +is, that's a battlefield anyway. Although the situation in EU should +be clear (no SP), it's not (as many other things at the moment too, +sadly). + +That's a proposal. It has shortcomings too of course; what I find +interesting in this is that: + - it makes Mageia put a few steps into the software patents debate +(instead of only trying to cope with an inconsistent, unpracticable +set of rules that we mostly even don't find legitimate at the very +start); + - it may reveal to be less of a burden than we currently think; it +may be worse; either case, we can adapt from a situation we will have +_experienced_. + +Now, that's nothing more than a proposal. :-p + +Romain +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001691.html">[Mageia-dev] Mirror layout +</A></li> + <LI>Next message: <A HREF="001693.html">[Mageia-dev] Mirror layout +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1692">[ date ]</a> + <a href="thread.html#1692">[ thread ]</a> + <a href="subject.html#1692">[ subject ]</a> + <a href="author.html#1692">[ 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> |