-
Notifications
You must be signed in to change notification settings - Fork 1
/
contributor.txt
82 lines (53 loc) · 2.67 KB
/
contributor.txt
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
= Contribution policies, workflows, and conventions =
:toc!:
:numbered!:
== GitLab.com is our forge ==
We use GitLab.com as our forge.
Our GitLab.com group is at https://gitlab.com/groups/NTPsec
Please use the issue tracker and the pull request process at that GitLab.com group.
== GitHub.com is a mirror, not our forge ==
We maintain a public mirror of the repo at https://github.com/ntpsec/ntpsec
Please do not use GitHub issues or GitHub pull requests.
== Hacking guide ==
Please read and obey the .../devel/hacking.txt file.
== License of contributions ==
Annoying but necessary legalese:
By submitting patches to this project, you agree to allow them to be
redistributed under the project's license according to the normal
forms and usages of the open-source community.
The license of new code is to be BSD-2-clause and the license for new
documentation is to be Creative Commons Attribute 4.0 License.
Contributions and patches with no license information will be assumed
to be under those licenses.
Please do *not* submit code under GPL or other licenses which place
conditions on derived works; we cannot accept such code. Please avoid
submitting code under any license other than BSD-2-clause, and avoid
submitting docs under any license other than the Creative Commons
Attribute 4.0 License.
It is your responsibility to make sure you have all the necessary
rights to contribute to the project.
== Development Practice ==
Before starting significant work, please propose it and discuss it
first in the mailto:[email protected] mailing list. Other people may
have suggestions, will want to collaborate, and will wish to review
your code.
Please work on one piece of conceptual work at a time. Keep each
narrative of work each in a different branch.
As much as possible, have each patch solve one problem.
A patch needs to comfortably fit in a reviewer's head.
A patch must not leave the project in a non-functional state.
== Optional: Send patches by email ==
If you are unable to use GitLab.com pull requests, we welcome simple
fix and "drive by" patches submitted by email.
Create the patch with git format-patch against the tip of master of
the main public repo.
You can email your patch to mailto:[email protected] if you are a
member of that mailing list, or you can email your patch to
mailto:[email protected] if you are not.
When we merge in your patch we will use the git parameter ---author
with the contents of the From header from your email and the git
parameter --date with the contents of the Date header from your email.
So make sure your From header is correct.
For complex contributions, please use GitLab.com.
image::clocktower64.png[align="center"]
// end