diff options
Diffstat (limited to 'zarb-ml/mageia-sysadm/2010-November/000559.html')
| -rw-r--r-- | zarb-ml/mageia-sysadm/2010-November/000559.html | 186 |
1 files changed, 186 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2010-November/000559.html b/zarb-ml/mageia-sysadm/2010-November/000559.html new file mode 100644 index 000000000..9056474de --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-November/000559.html @@ -0,0 +1,186 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-sysadm] Main tasks for the next days + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Main%20tasks%20for%20the%20next%20days&In-Reply-To=%3C1289925900.722.451.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000552.html"> + <LINK REL="Next" HREF="000591.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] Main tasks for the next days</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Main%20tasks%20for%20the%20next%20days&In-Reply-To=%3C1289925900.722.451.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-sysadm] Main tasks for the next days">misc at zarb.org + </A><BR> + <I>Tue Nov 16 17:45:00 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="000552.html">[Mageia-sysadm] Main tasks for the next days +</A></li> + <LI>Next message: <A HREF="000591.html">[Mageia-sysadm] Main tasks for the next days +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#559">[ date ]</a> + <a href="thread.html#559">[ thread ]</a> + <a href="subject.html#559">[ subject ]</a> + <a href="author.html#559">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le mardi 16 novembre 2010 à 13:57 +0100, Olivier Blin a écrit : +><i> Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">misc at zarb.org</A>> writes: +</I>><i> +</I>><i> > We all agree that some softwares will need to be cleaned from icons, but +</I>><i> > IMHO, most of them don't. +</I>><i> +</I>><i> How about the Mandriva brand/name ? +</I> +Well, it depend, where exactly should it be cleaned ? + +Because I doubt that having the Mandriva word buried somewhere in a perl +file is "using the Mandriva brand", especially if the file is not +distributed in a tarball as a separate product. + +Definition from wikipedia ( us laws, but I think this part is harmonized +thanks to various treaties, and the french definition is similar ) : + +" a distinctive sign or indicator used by an individual, business +organization, or other legal entity to identify that the products or +services to consumers with which the trademark appears originate from a +unique source, and to distinguish its products or services from those of +other entities." + +If we don't use the name as a distinctive sign or indicator to identify +a product or a service, then it is not used as a brand or a trademark. + +So if we do not use it as a brand or trademark, then the protection do +not apply. + +For example, saying mandriva is not forbidden ( not yet :) ). On the +other hand, calling a association mandriva-duck would be using the name +as a brand/trademark and therefor would requires autorisation ( or be +risky ). + +So, my own analysis : + +If the name is displayed in a released product to identify it, yes, this +is problematic. In the rpm name, in the interface like "mandriva control +center" in title or "about page", in the documentation. + +If the name is used in email, or for copyright notice, then we need to +keep it ( as doing otherwise would be seen as copyright violation ). + +If the name is used in a comment, in a procedure or variable name, or in +a url for technical reason, I do not think it need to be removed +( except for technical reason, obviously ). + +Now, the tricky part : +If we have a file in svn that would display the name in such a way that +would be used as brand, it this a problem ? + +I think it is not, as long as we do not distribute this as a product +( ie, release a tarball ), nor encourage people to use the old version +( ie if we say "use the old svn version as the feature are much better +with all unfixed bug" ). We will be clearly doing the contrary, ie +distribute fixed software ( with fixed meaning without actively using +Mandriva name in such a way that we will use it as a brand, distribute +mean "putting a tarball on our server" ) and push usually the latest +version. + +Hearst lawyers didn't asked to remove the name from svn/cvs afaik. +Neither did mozilla asked Debian to do so for the mozilla/iceweasel +case. + + +For example, let's take urpmi : +[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">misc at virgo</A> ~] $ grep -i -s mandriva $(rpm -ql urpmi) | grep -v +Copyright + +I removed Copyright because that's legal mention that IMO we need to +keep. + +And so it give : +/usr/share/doc/urpmi/NEWS is not using the mark ( 2 links and 2 +explanation upon a new feature about mandriva kernel ), this is ot used +as a distinctive sign. + +/usr/lib/perl5/vendor_perl/5.10.0/urpm.pm +used in the description of the tool. + +urpm - Mandriva perl tools to handle the urpmi database + +this one is likely be something we will need to change if we distribute +the module. + + +/usr/lib/perl5/vendor_perl/5.10.0/urpm/cfg.pm +-> url to the mirror, can be kept in svn ( but need to be changed to +work again ) + + +/usr/lib/perl5/vendor_perl/5.10.0/urpm/media.pm + +$distribconf->settree('mandriva'); + +name is used as a constant, this is not displayed anywhere. Therefore, +no problem in keeping it in the history. + +/usr/lib/perl5/vendor_perl/5.10.0/urpm/mirrors.pm + +-> a procedure called _mandriva_mirrorlist. Not a trademark +violation, as this is never displayed. It should be indeed changed to be +cleaner. +And some urls used by the procedure. + + +/usr/lib/perl5/vendor_perl/5.10.0/urpm/msg.pm + +a comment telling this come from svn.mandriva.com. Not a trademark +violation. + +So basically, for urpmi ( a old version ), the only thing to change is +the documentation. And as long as we do not distribute it ( ie, in a +package or in a tarball ), I think it is not used as a distinctive +sign. + +I will also add that Mandriva is a trademark, but mdv and mdk are not. + +Therefore, except the various mandriva-foo-config ( who are more +configuration than software ) and rpm-mandriva-setup, the software name +will likely not be a problem. + + +Now, if we decide that we also need to clean svn, we can use git and +tailor to do some trick to clean the source code ( ie, in the case of +urpmi, remove the name mandriva from the pod documentation ). + +-- +Michael Scherer + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000552.html">[Mageia-sysadm] Main tasks for the next days +</A></li> + <LI>Next message: <A HREF="000591.html">[Mageia-sysadm] Main tasks for the next days +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#559">[ date ]</a> + <a href="thread.html#559">[ thread ]</a> + <a href="subject.html#559">[ subject ]</a> + <a href="author.html#559">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm +mailing list</a><br> +</body></html> |