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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-webteam] Need help for mageia-app-db's licence
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20Need%20help%20for%20mageia-app-db%27s%20licence&In-Reply-To=%3C201101021307.00283.stormi%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000083.html">
<LINK REL="Next" HREF="000085.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-webteam] Need help for mageia-app-db's licence</H1>
<B>Samuel Verschelde</B>
<A HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20Need%20help%20for%20mageia-app-db%27s%20licence&In-Reply-To=%3C201101021307.00283.stormi%40laposte.net%3E"
TITLE="[Mageia-webteam] Need help for mageia-app-db's licence">stormi at laposte.net
</A><BR>
<I>Sun Jan 2 13:07:00 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="000083.html">[Mageia-webteam] Need help for mageia-app-db's licence
</A></li>
<LI>Next message: <A HREF="000085.html">[Mageia-webteam] Designing mageia-app-db's homepage
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#84">[ date ]</a>
<a href="thread.html#84">[ thread ]</a>
<a href="subject.html#84">[ subject ]</a>
<a href="author.html#84">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le samedi 1 janvier 2011 16:40:16, andre999 a écrit :
><i> Samuel Verschelde a écrit :
</I>><i> > Hi,
</I>><i> >
</I>><i> > In the process of releasing mageia-app-db 0.1, we have to fix licensing
</I>><i> > issues. Could someone help us on that ?
</I>><i> >
</I>><i> > I never released free software before, so I'd like to know what to do
</I>><i> > once the licence has been chosen :
</I>><i> > - create a simple LICENSE file at the root of the project ?
</I>><i> > - add a notice in every source file ? (there are lots of them, many
</I>><i> > automatically generated by the framework mechanisms)
</I>><i> > - other ?
</I>><i> >
</I>><i> > Among the possible licences, there's Gnu Affero GPLv3, which forces
</I>><i> > anyone running the software (or one of its derivatives) on a server to
</I>><i> > make the source code available to users. However, I don't know if this
</I>><i> > license is compatible with our XML-RPC querying sophie.zarb.org when
</I>><i> > needed (does the Gnu Affero GPLv3 imply that we must also give sophie's
</I>><i> > source code to users (sophie being a separate project from Olivier
</I>><i> > Thauvin), and does it imply that sophie should be under the Gnu Affero
</I>><i> > GPLv3 licence ? I think not but I'd like to be sure.
</I>><i> >
</I>><i> > Regards
</I>><i> >
</I>><i> > Samuel Verschelde
</I>><i>
</I>><i> Hi Samuel
</I>><i>
</I>><i> I'm no expert, but reading the Affero GPLv3 licence, it looks like it is
</I>><i> what you're looking for.
</I>><i>
</I>><i> In section (1) Source Code, it requires releasing "Corresponding
</I>><i> Source", defined as :
</I>><i> ----
</I>><i> The "Corresponding Source" for a work in object code form means all the
</I>><i> source code needed to generate, install, and (for an executable work)
</I>><i> run the object code and to modify the work, including scripts to control
</I>><i> those activities. However, it does not include the work's System
</I>><i> Libraries, or general-purpose tools or generally available free programs
</I>><i> which are used unmodified in performing those activities but which are
</I>><i> not part of the work. For example, Corresponding Source includes
</I>><i> interface definition files associated with source files for the work,
</I>><i> and the source code for shared libraries and dynamically linked
</I>><i> subprograms that the work is specifically designed to require, such as
</I>><i> by intimate data communication or control flow between those subprograms
</I>><i> and other parts of the work.
</I>><i> ----
</I>><i> So it wouldn't require you to release sophie source code, since you are
</I>><i> only using it unmodified. It is not part of mageia-app-db.
</I>><i>
</I>><i> Under the heading "How to Apply These Terms to Your New Programs",
</I>><i> it suggests attaching a brief copyright notice at the beginning of
</I>><i> each source file, with a pointer to where the full notice is found.
</I>><i> Also adding info on how to contact you by "electronic and paper mail"
</I>><i>
</I>><i> See <A HREF="http://www.gnu.org/licenses/agpl.html">http://www.gnu.org/licenses/agpl.html</A>
</I>><i>
</I>><i> Regards
</I>><i> André
</I>
Thanks, this is the license we finally chose.
I added a LICENSE file at the project's root. We'll try to add a copyright
notice at the beginning of most source files.
Regards
Samuel
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000083.html">[Mageia-webteam] Need help for mageia-app-db's licence
</A></li>
<LI>Next message: <A HREF="000085.html">[Mageia-webteam] Designing mageia-app-db's homepage
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#84">[ date ]</a>
<a href="thread.html#84">[ thread ]</a>
<a href="subject.html#84">[ subject ]</a>
<a href="author.html#84">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-webteam">More information about the Mageia-webteam
mailing list</a><br>
</body></html>
|
