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/2012-March/013622.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/2012-March/013622.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-March/013622.html | 127 |
1 files changed, 127 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-March/013622.html b/zarb-ml/mageia-dev/2012-March/013622.html new file mode 100644 index 000000000..fdf52d8fc --- /dev/null +++ b/zarb-ml/mageia-dev/2012-March/013622.html @@ -0,0 +1,127 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRFC%5D%20How%20to%20proceed%20with%20seamonkey/iceape%20for%0A%20security%20updates%20and%20freeze%20push&In-Reply-To=%3C4F735F91.2040803%40arcor.de%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="013762.html"> + <LINK REL="Next" HREF="013644.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push</H1> + <B>Florian Hubold</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BRFC%5D%20How%20to%20proceed%20with%20seamonkey/iceape%20for%0A%20security%20updates%20and%20freeze%20push&In-Reply-To=%3C4F735F91.2040803%40arcor.de%3E" + TITLE="[Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push">doktor5000 at arcor.de + </A><BR> + <I>Wed Mar 28 20:59:29 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="013762.html">[Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push +</A></li> + <LI>Next message: <A HREF="013644.html">[Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#13622">[ date ]</a> + <a href="thread.html#13622">[ thread ]</a> + <a href="subject.html#13622">[ subject ]</a> + <a href="author.html#13622">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Am 26.03.2012 19:46, schrieb Florian Hubold: +><i> I'm currently in contact with some seamonkey developers, to maybe clear up +</I>><i> why/if the rebrand is needed, if it's needed like it's currently done, and +</I>><i> why Fedora can simply ship seamonkey without the need for a rebrand, but +</I>><i> the dialog may take some time, this would be only relevant for option 2. +</I> + +As a followup, an answer from Justin Callek, seamonkey developer: + + +Am 28.03.2012 19:02, schrieb Justin Wood (Callek): +><i> Florian Hubold wrote: +</I>>>>><i> Could you please expand on this, and tell me if we need to rebrand seamonkey if +</I>>>>>>><i> we want to ship it, and how far the rebrand has to go and under +</I>>>>>>><i> which conditions we need to do the rebrand. As i'm currently wondering why +</I>>>>>>><i> f.ex. Fedora can ship seamonkey without any rebranding, or do they have +</I>>>>>>><i> official approval? +</I>>>>><i> Top of my head I'm not sure on the Fedora situation, so I won't comment +</I>>>>><i> on that. +</I>>><i> You know whom i can ask about this? No pressing issue, though ... +</I>>><i> Would be nice if somebody could tell me wether the Fedora way is approved, +</I>>><i> because one of my options would be to drop iceape in it's current form +</I>>><i> as it's hassle to maintain, and to reimport seamonkey as Fedora packages +</I>>><i> it: <A HREF="http://pkgs.fedoraproject.org/gitweb/?p=seamonkey.git;a=tree">http://pkgs.fedoraproject.org/gitweb/?p=seamonkey.git;a=tree</A> +</I>>><i> +</I>><i> Will address the rest of your message later, but this for now... +</I>><i> +</I>><i> I will thank Robert Kaiser for providing the wording for the answer of +</I>><i> the following, not sure if he meant to send it directly to you as well, +</I>><i> but this makes my reply soo much easier. +</I>><i> +</I>><i> `so far, we've handled those cases with a stance of "if you have +</I>><i> permission from Mozilla to ship an officially branded Firefox (and +</I>><i> Thunderbird) with those code changes, you have permission to ship +</I>><i> SeaMonkey with those same changes - if you don't modify the code or +</I>><i> deactivate (major) features, you're always allowed to ship with official +</I>><i> branding." As most of those distros offer Firefox and Thunderbird as +</I>><i> well, usually with higher priorities as SeaMonkey, that has worked out +</I>><i> fine so far without needing special additional rules. ` +</I>><i> +</I>><i> As said I'll skim the changes you mentioned, but if you are able to ship +</I>><i> Firefox/Thunderbird with these changes and with official branding, +</I>><i> consider it a 'go' from us. +</I>><i> +</I> +OK, so how do we handle this? As there is no explicit permission +by Mozilla to have us ship officially branded Mozilla apps, as i've +put up before, or at least i don't know of any explicit permission. + +As this applies to Firefox and Thunderbird as well ... + + +</PRE> + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="013762.html">[Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push +</A></li> + <LI>Next message: <A HREF="013644.html">[Mageia-dev] [RFC] How to proceed with seamonkey/iceape for security updates and freeze push +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#13622">[ date ]</a> + <a href="thread.html#13622">[ thread ]</a> + <a href="subject.html#13622">[ subject ]</a> + <a href="author.html#13622">[ 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> |