diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20100927/001341.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20100927/001341.html | 120 |
1 files changed, 120 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20100927/001341.html b/zarb-ml/mageia-discuss/20100927/001341.html new file mode 100644 index 000000000..bbaa88bc6 --- /dev/null +++ b/zarb-ml/mageia-discuss/20100927/001341.html @@ -0,0 +1,120 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-discuss] commercial support + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20commercial%20support&In-Reply-To=%3C4CA00296.8050508%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001345.html"> + <LINK REL="Next" HREF="001382.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] commercial support</H1> + <B>andré</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20commercial%20support&In-Reply-To=%3C4CA00296.8050508%40laposte.net%3E" + TITLE="[Mageia-discuss] commercial support">andr55 at laposte.net + </A><BR> + <I>Mon Sep 27 04:33:58 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001345.html">[Mageia-discuss] rpm or deb? +</A></li> + <LI>Next message: <A HREF="001382.html">[Mageia-discuss] commercial support +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1341">[ date ]</a> + <a href="thread.html#1341">[ thread ]</a> + <a href="subject.html#1341">[ subject ]</a> + <a href="author.html#1341">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Romain d'Alverny a écrit : +><i> On Fri, Sep 24, 2010 at 21:24, Dick Gevers<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">dvgevers at xs4all.nl</A>> wrote: +</I>><i> +</I>>><i> If the need arises, what problem would there be if any number of Mageia +</I>>><i> volunteers set up a commercial "Mageia Service SA" with a license from the +</I>>><i> Mageia non-profit association to provide such commercial support? They +</I>>><i> could make a contract that the profits from the SA would go to the +</I>>><i> association and/or the shareholders and/or the employed volunteers at +</I>>><i> certain agreed percentages of the earnings. +</I>>><i> +</I>><i> This is something we expect and welcome to happen: companies providing +</I>><i> commercial support and services from and around the distribution. +</I>><i> +</I>><i> We expect this to happen as they would need, to be consistent with +</I>><i> their own business, to contribute back to the Mageia project: be it +</I>><i> upstream patches, sponsoring, resources, developers time, any other +</I>><i> role, etc. (of course, such a contribution would not, in any case, +</I>><i> alter the governance of the project). +</I>><i> +</I>><i> Indeed, licensing and guidelines for this to happen smoothly have to +</I>><i> be thought out properly. +</I>><i> +</I>><i> Romain +</I>><i> _____ +</I>><i> +</I>Note that gpl v3 doesn't require that 3rd parties contribute back to the +Mageia project, although Mageia could make that an additional requirement. +The GPL v3 does require that any changes that are conveyed to other +parties, be conveyed with the source code and a GPL v3 licence. +However if a customer contracts exclusive modifications not to be +conveyed to other parties, then under GPL v3 there is explicitly no +requirement to release this code (source or not) to any other party. +This should not be required by Mageia, either, as this provision allows +companies to make confidential modifications of GPL software for their +own exclusive use, or to commission others to do so for them. +Note that as Romain says, it generally would be in the interest of third +parties to contribute back changes to Mageia, particularly bug fixes. + +Also note that support doesn't necessarily involve changes to GPL +covered code. +There could be no coding involved. The coding could be not an integral +part of the GPL code. Or the code could link to a LGPL library, and +thus not be restricted. +Personally, I've done a lot of support covered by these situations. + +In short, there would be no problem for Mageia to maintain a list of +third parties wanting to do commercial support, as long as Mageia is not +a party to such transactions. + +- André +</PRE> + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001345.html">[Mageia-discuss] rpm or deb? +</A></li> + <LI>Next message: <A HREF="001382.html">[Mageia-discuss] commercial support +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1341">[ date ]</a> + <a href="thread.html#1341">[ thread ]</a> + <a href="subject.html#1341">[ subject ]</a> + <a href="author.html#1341">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss +mailing list</a><br> +</body></html> |