]> git.ipfire.org Git - thirdparty/samba.git/blame - README.contributing
ldb-samba: ldif_read_objectSid() short-circuits without 'S'
[thirdparty/samba.git] / README.contributing
CommitLineData
bd01ae22
JA
1How to contribute a patch to Samba
2----------------------------------
3
07856586
AB
4Please see https://wiki.samba.org/index.php/Contribute
5for detailed set-by-step instructions on how to submit a patch
6for Samba via GitLab.
bd01ae22 7
07856586 8Samba's GitLab mirror is at https://gitlab.com/samba-team/samba
bd01ae22
JA
9
10Ownership of the contributed code
11---------------------------------
12
13Samba is a project with distributed copyright ownership, which means
14we prefer the copyright on parts of Samba to be held by individuals
15rather than corporations if possible. There are historical legal
16reasons for this, but one of the best ways to explain it is that it's
17much easier to work with individuals who have ownership than corporate
18legal departments if we ever need to make reasonable compromises with
19people using and working with Samba.
20
21We track the ownership of every part of Samba via git, our source code
22control system, so we know the provenance of every piece of code that
23is committed to Samba.
24
25So if possible, if you're doing Samba changes on behalf of a company
26who normally owns all the work you do please get them to assign
27personal copyright ownership of your changes to you as an individual,
28that makes things very easy for us to work with and avoids bringing
29corporate legal departments into the picture.
30
31If you can't do this we can still accept patches from you owned by
32your employer under a standard employment contract with corporate
33copyright ownership. It just requires a simple set-up process first.
34
35We use a process very similar to the way things are done in the Linux
36kernel community, so it should be very easy to get a sign off from
37your corporate legal department. The only changes we've made are to
38accommodate the licenses we use, which are GPLv3 and LGPLv3 (or later)
39whereas the Linux kernel uses GPLv2.
40
41The process is called signing.
42
43How to sign your work
44---------------------
45
46Once you have permission to contribute to Samba from
47your employer, simply email a copy of the following text
48from your corporate email address to contributing@samba.org
49
50------------------------------------------------------------
5fa89897 51Samba Developer's Declaration, Version 1.0
bd01ae22
JA
52
53By making a contribution to this project, I certify that:
54
55(a) The contribution was created in whole or in part by me and I
56 have the right to submit it under the appropriate
57 version of the GNU General Public License; or
58
59(b) The contribution is based upon previous work that, to the best
60 of my knowledge, is covered under an appropriate open source
61 license and I have the right under that license to submit that
62 work with modifications, whether created in whole or in part
63 by me, under the GNU General Public License, in the
64 appropriate version; or
65
66(c) The contribution was provided directly to me by some other
67 person who certified (a) or (b) and I have not modified
68 it.
69
70(d) I understand and agree that this project and the
71 contribution are public and that a record of the
72 contribution (including all metadata and personal
73 information I submit with it, including my sign-off) is
74 maintained indefinitely and may be redistributed
75 consistent with the Samba Team's policies and the
76 requirements of the GNU GPL where they are relevant.
77
78(e) I am granting this work to this project under the terms of both
79 the GNU General Public License and the GNU Lesser General Public
80 License as published by the Free Software Foundation; either version
81 3 of these Licenses, or (at the option of the project) any later
82 version.
83
84 http://www.gnu.org/licenses/gpl-3.0.html
85 http://www.gnu.org/licenses/lgpl-3.0.html
86------------------------------------------------------------
87
88We will maintain a copy of that email as a record that you have the
89rights to contribute code to Samba under the required licenses whilst
90working for the company where the email came from.
91
92Then when sending in a patch via the normal mechanisms described
93above, add a line that states:
94
95Signed-off-by: Random J Developer <random@developer.example.org>
96
97using your real name and the email address you sent the original email
5fa89897 98you used to send the Samba Developer's Declaration to us
bd01ae22
JA
99(sorry, no pseudonyms or anonymous contributions.)
100
101That's it ! Such code can then quite happily contain changes that have
102copyright messages such as :
103
104 (C) Example Corporation.
105
106and can be merged into the Samba codebase in the same way as patches
107from any other individual. You don't need to send in a copy of the
5fa89897 108Samba Developer's Declaration for each patch, or inside each
bd01ae22
JA
109patch. Just the sign-off message is all that is required once we've
110received the initial email.
111
112Have fun and happy Samba hacking !
113
114The Samba Team.
115
c15c40e0 116
5fa89897 117The "Samba Developer's Declaration, Version 1.0" is:
c15c40e0
BK
118 (C) 2011 Software Freedom Conservancy, Inc.
119 (C) 2005 Open Source Development Labs, Inc.
120
121licensed under Creative Commons Attribution-ShareAlike 4.0 License as found
122at https://creativecommons.org/licenses/by-sa/4.0/legalcode and based on
123"Developer's Certificate of Origin 1.1" as found at
124http://web.archive.org/web/20070306195036/http://osdlab.org/newsroom/press_releases/2004/2004_05_24_dco.html