diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110318/003420.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110318/003420.html | 221 |
1 files changed, 221 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110318/003420.html b/zarb-ml/mageia-dev/20110318/003420.html new file mode 100644 index 000000000..68ff805f2 --- /dev/null +++ b/zarb-ml/mageia-dev/20110318/003420.html @@ -0,0 +1,221 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Seamonkey package + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Seamonkey%20package&In-Reply-To=%3C4D82C22B.5010808%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="003407.html"> + <LINK REL="Next" HREF="003432.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Seamonkey package</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Seamonkey%20package&In-Reply-To=%3C4D82C22B.5010808%40laposte.net%3E" + TITLE="[Mageia-dev] Seamonkey package">andr55 at laposte.net + </A><BR> + <I>Fri Mar 18 03:23:39 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="003407.html">[Mageia-dev] Seamonkey package +</A></li> + <LI>Next message: <A HREF="003432.html">[Mageia-dev] Seamonkey package +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3420">[ date ]</a> + <a href="thread.html#3420">[ thread ]</a> + <a href="subject.html#3420">[ subject ]</a> + <a href="author.html#3420">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>nicolas vigier a écrit : +><i> +</I>><i> On Thu, 17 Mar 2011, andre999 wrote: +</I>><i> +</I>>><i> nicolas vigier a écrit : +</I>>>><i> +</I>>>><i> On Thu, 10 Mar 2011, Tux99 wrote: +</I>>>><i> +</I>>>>><i> +</I>>>>><i> +</I>>>>><i> Quote: Christiaan Welvaart wrote on Thu, 10 March 2011 23:26 +</I>>>>><i> ---------------------------------------------------- +</I>>>>>><i> On Thu, 10 Mar 2011, nicolas vigier wrote: +</I>>>>>><i> +</I>>>>>>><i> On Thu, 10 Mar 2011, Christiaan Welvaart wrote: +</I>>>>>>><i> +</I>>>>>>>><i> Unfortunately the seamonkey name and logos are trademarked and the +</I>>>>>><i> license +</I>>>>>>>><i> terms are most likely not acceptable so it seems to me we'll have +</I>>>>>><i> to +</I>>>>>>>><i> rename/rebrand it. +</I>>>>>>><i> +</I>>>>>>><i> Is it different than firefox license terms ? +</I>>>>>><i> +</I>>>>>><i> Same rules AFAIK, see +</I>>>>>><i> <A HREF="http://www.mozilla.org/foundation/trademarks/policy.html">http://www.mozilla.org/foundation/trademarks/policy.html</A> +</I>>><i> +</I>>><i> Indeed, exactly the same rules. +</I>>><i> +</I>>>>><i> I don't see why we need to change the name. The policy says: +</I>>>>><i> +</I>>>>><i> "If you compile Mozilla unmodified source code (including code and config +</I>>>>><i> files in the installer) and do not charge for it, you do not need +</I>>>>><i> additional permission from Mozilla to use the relevant Mozilla Mark(s) for +</I>>>>><i> your compiled version." +</I>>>><i> +</I>... +>>><i> And it seems mandriva seamonkey package also has some patchs : +</I>>>><i> <A HREF="http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/seamonkey/current/SOURCES/">http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/seamonkey/current/SOURCES/</A> +</I>>><i> +</I>>><i> These are mosty against obsolete versions of Seamonkey. (Which may predate +</I>>><i> the current Mozilla policy.) +</I>><i> +</I>><i> This is the package for version 2.0.12, which is the latest version, +</I>><i> released 2 weeks ago. Is this what you call an obsolete version ? +</I> +Didn't notice that, about 5 pages down. And they were mostly +localisation modules, I assume unmodified. In any case, most +correctives should be available in (Mozilla) cvs. +There were pages of entries for the obsolete versions 1.17 or before, +which I believe predates the Mozilla policy change. + +><i> And the Mozilla policy is not new, I doubt the patches predate the +</I>><i> policy ... +</I>><i> +</I>... +>><i> +</I>>><i> Note also that if applied patches come from Mozilla, that shouldn't require +</I>>><i> permission. (And Mozilla issues a lot of patches, particularly for +</I>>><i> security.) +</I>><i> +</I>><i> This is not security patches. Did you look at the patches ? +</I> +Whatever, they could come from Mozilla. +If a bug is found, it can easily be submitted to Mozilla, and applied +once accepted, from cvs -- which doesn't have to await another release. + +><i> By the way, did you really see Mozilla issue a lot of patches ? +</I>><i> They usually don't release patch on their ftp server, and only release +</I>><i> new tarballs for new versions when they need to fix security issues. +</I>><i> +</I>><i> And did you really see anything in the policy talking about patches +</I>><i> coming from Mozilla, or is it just an other random statement ? +</I> +Did you happen to notice the references to obtaining the source code +from (Mozilla) cvs ? + +Surprisingly, that is where they put their patches. And no, it is not a +random statement. I have downloaded Mozilla patches from cvs. +(Much if not most are to scripts, very easily applied without even +recompiling.) + +>><i> As well, we don't use the logo for advertising, we are just repackaging the +</I>>><i> software as part of our distribution. +</I>><i> +</I>><i> We are using the logo and the name, so we need to follow the policy (or +</I>><i> use rebranded version). +</I> +We are not using the logo and name outside of the product itself, which +as I understand remains unchanged. + +>><i> It might install in a somewhat different location, but that doesn't change +</I>>><i> the contained binaries or scripts. Also, binaries distributed by Mozilla +</I>>><i> without installer (in a compressed file) can be installed (almost) anywhere +</I>>><i> one likes. +</I>><i> +</I>><i> The list of changes that require permision to use the Mozilla Marks +</I>><i> includes "file location changes". Did you read the policy ? +</I> +I read it. Are you saying that an installer version is chosen and the +install locations are changed, or that a non-installer version is +chosen, and the relative locations are changed by Mageia compiles ? +If it wasn't clear, my point is that we can work around that without +problem. + +>>><i> Also the "do not charge for it" would make it non free (but it does not +</I>>>><i> seem to be mentioned in the "Modifications" section, only in the +</I>>>><i> "Unaltered Binaries" section). +</I>>><i> +</I>>><i> Why would "do not charge for it" make it non-free ? +</I>>><i> That doesn't seem to be a requirement of open source. Although charging +</I>>><i> for it is generally permitted in unmodified open source licenses. +</I>><i> +</I>><i> Did you read the open source definition ? +</I>><i> <A HREF="http://www.opensource.org/docs/osd">http://www.opensource.org/docs/osd</A> +</I>><i> First line says : "The license shall not restrict any party from selling +</I>><i> or giving away the software ..." +</I> +You forgot the rest of the sentence, which reads : "... as a component +of an aggregate software distribution containing programs from several +different sources. The license shall not require a royalty or other fee +for such sale." +In other words, no bar on forbidding the sale of a particular component +in itself. Which, as I understand it, is compatible with the position +of Mozilla. +In a previous post in this thread, I pointed out that the FSF considers +the Xinetd license to be a free software license, albeit not compatible +with GPL. The Xinetd license contains a clause not permitting selling +the software. +See <<A HREF="http://fedoraproject.org/wiki/Licensing/Xinetd_License">http://fedoraproject.org/wiki/Licensing/Xinetd_License</A>> + +><i> You're talking about a policy that you didn't read. +</I> +Or perhaps you didn't understand what I said ... + +><i> You're talking about "open source" while you didn't read the definition. +</I> +Or more exactly, that you didn't finish reading the sentence. Or maybe +you didn't understand ? +Note that you chose the OSI definition of open source -- and evidently. +there are others. + +><i> It would be nice if you could stop sending emails with almost only false informations, and instead only +</I> talk about what you know, or take the time to check what you're saying. + +Sorry that you feel so challenged by differing opinions ... + +>>><i> So maybe we need to request permission, as explained in the +</I>>>><i> "Modifications" section. +</I>>><i> +</I>>><i> I don't think we need to, but we can always confirm via +</I>>><i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">trademarks at mozilla.com</A> +</I>><i> +</I>><i> It probably won't be a problem to get permission, but we need to ask. +</I>><i> I think Romain plans to see this with people from Mozilla europe. +</I> +Like I said, we can always confirm. + +Btw, it's great to have these nice friendly discussions, with free and +open exchange of opinion -- don't you think ? :) + +-- +André +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="003407.html">[Mageia-dev] Seamonkey package +</A></li> + <LI>Next message: <A HREF="003432.html">[Mageia-dev] Seamonkey package +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3420">[ date ]</a> + <a href="thread.html#3420">[ thread ]</a> + <a href="subject.html#3420">[ subject ]</a> + <a href="author.html#3420">[ 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> |