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
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
|
<!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=%3Cm38w0rtzlr.fsf%40euphor.blino.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000559.html">
<LINK REL="Next" HREF="000617.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-sysadm] Main tasks for the next days</H1>
<B>Olivier Blin</B>
<A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Main%20tasks%20for%20the%20next%20days&In-Reply-To=%3Cm38w0rtzlr.fsf%40euphor.blino.org%3E"
TITLE="[Mageia-sysadm] Main tasks for the next days">mageia at blino.org
</A><BR>
<I>Wed Nov 17 22:22:08 CET 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000559.html">[Mageia-sysadm] Main tasks for the next days
</A></li>
<LI>Next message: <A HREF="000617.html">[Mageia-sysadm] Main tasks for the next days
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#591">[ date ]</a>
<a href="thread.html#591">[ thread ]</a>
<a href="subject.html#591">[ subject ]</a>
<a href="author.html#591">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">misc at zarb.org</A>> writes:
><i> So, my own analysis :
</I>><i>
</I>><i> If the name is displayed in a released product to identify it, yes, this
</I>><i> is problematic. In the rpm name, in the interface like "mandriva control
</I>><i> center" in title or "about page", in the documentation.
</I>
Agreed
><i> If the name is used in email, or for copyright notice, then we need to
</I>><i> keep it ( as doing otherwise would be seen as copyright violation ).
</I>
Yes
><i> If the name is used in a comment, in a procedure or variable name, or in
</I>><i> a url for technical reason, I do not think it need to be removed
</I>><i> ( except for technical reason, obviously ).
</I>
Agreed as well
><i> Now, the tricky part :
</I>><i> If we have a file in svn that would display the name in such a way that
</I>><i> would be used as brand, it this a problem ?
</I>><i>
</I>><i> I think it is not, as long as we do not distribute this as a product
</I>><i> ( ie, release a tarball ), nor encourage people to use the old version
</I>><i> ( ie if we say "use the old svn version as the feature are much better
</I>><i> with all unfixed bug" ). We will be clearly doing the contrary, ie
</I>><i> distribute fixed software ( with fixed meaning without actively using
</I>><i> Mandriva name in such a way that we will use it as a brand, distribute
</I>><i> mean "putting a tarball on our server" ) and push usually the latest
</I>><i> version.
</I>
If the SVN is public and contain packages like mandriva-release, that's
opening the door for potential troubles.
I think we should not take risk, and start cleaning packages of the
Mandriva name in a private SVN, and only make public a new SVN repo
starting from the cleaned packages, without any reference to previous
Mandriva stuff.
><i> Hearst lawyers didn't asked to remove the name from svn/cvs afaik.
</I>><i> Neither did mozilla asked Debian to do so for the mozilla/iceweasel
</I>><i> case.
</I>
Doesn't mean it won't happen for us :)
><i> For example, let's take urpmi :
</I>><i> [<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">misc at virgo</A> ~] $ grep -i -s mandriva $(rpm -ql urpmi) | grep -v
</I>><i> Copyright
</I>><i>
</I>><i> I removed Copyright because that's legal mention that IMO we need to
</I>><i> keep.
</I>><i>
</I>><i> And so it give :
</I>><i> /usr/share/doc/urpmi/NEWS is not using the mark ( 2 links and 2
</I>><i> explanation upon a new feature about mandriva kernel ), this is ot used
</I>><i> as a distinctive sign.
</I>><i>
</I>><i> /usr/lib/perl5/vendor_perl/5.10.0/urpm.pm
</I>><i> used in the description of the tool.
</I>><i>
</I>><i> urpm - Mandriva perl tools to handle the urpmi database
</I>><i>
</I>><i> this one is likely be something we will need to change if we distribute
</I>><i> the module.
</I>
Ok
><i> /usr/lib/perl5/vendor_perl/5.10.0/urpm/cfg.pm
</I>><i> -> url to the mirror, can be kept in svn ( but need to be changed to
</I>><i> work again )
</I>><i>
</I>><i>
</I>><i> /usr/lib/perl5/vendor_perl/5.10.0/urpm/media.pm
</I>><i>
</I>><i> $distribconf->settree('mandriva');
</I>><i>
</I>><i> name is used as a constant, this is not displayed anywhere. Therefore,
</I>><i> no problem in keeping it in the history.
</I>><i>
</I>><i> /usr/lib/perl5/vendor_perl/5.10.0/urpm/mirrors.pm
</I>><i>
</I>><i> -> a procedure called _mandriva_mirrorlist. Not a trademark
</I>><i> violation, as this is never displayed. It should be indeed changed to be
</I>><i> cleaner.
</I>><i> And some urls used by the procedure.
</I>
I would feel safer if all these get burried and don't appear on our
public website (viewvc).
><i> /usr/lib/perl5/vendor_perl/5.10.0/urpm/msg.pm
</I>><i>
</I>><i> a comment telling this come from svn.mandriva.com. Not a trademark
</I>><i> violation.
</I>><i>
</I>><i> So basically, for urpmi ( a old version ), the only thing to change is
</I>><i> the documentation. And as long as we do not distribute it ( ie, in a
</I>><i> package or in a tarball ), I think it is not used as a distinctive
</I>><i> sign.
</I>><i>
</I>><i> I will also add that Mandriva is a trademark, but mdv and mdk are not.
</I>><i>
</I>><i> Therefore, except the various mandriva-foo-config ( who are more
</I>><i> configuration than software ) and rpm-mandriva-setup, the software name
</I>><i> will likely not be a problem.
</I>
Yep
Same for drakx
><i> Now, if we decide that we also need to clean svn, we can use git and
</I>><i> tailor to do some trick to clean the source code ( ie, in the case of
</I>><i> urpmi, remove the name mandriva from the pod documentation ).
</I>
We can start working in a private svn to clean the Mandriva references,
and only publish the last revision, containing a completely clean repo
--
Olivier Blin - blino
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000559.html">[Mageia-sysadm] Main tasks for the next days
</A></li>
<LI>Next message: <A HREF="000617.html">[Mageia-sysadm] Main tasks for the next days
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#591">[ date ]</a>
<a href="thread.html#591">[ thread ]</a>
<a href="subject.html#591">[ subject ]</a>
<a href="author.html#591">[ 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>
|
