Browse Source

follow the advisor: add DCO and some improvements

Lunny Xiao 2 years ago
parent
commit
587d870f1e
2 changed files with 72 additions and 2 deletions
  1. 36 2
      CONTRIBUTING.md
  2. 36 0
      DCO

+ 36 - 2
CONTRIBUTING.md

@@ -8,13 +8,31 @@ It assumes you have followed the
8 8
 
9 9
 Sensitive security-related issues should be reported to [security@gitea.io](mailto:security@gitea.io).
10 10
 
11
+## Bug reports
12
+
13
+Please search the issues on the issue tracker with a variety of keywords to
14
+ensure your bug is not already reported.
15
+
16
+If unique, [open an issue](https://github.com/go-gitea/gitea/issues/new)
17
+and answer the questions so we can understand and reproduce the problematic
18
+behavior.
19
+
20
+The burden is on you to convince us that it is actually a bug in Gitea. This
21
+is easiest to do when you write clear, concise instructions so we can reproduce
22
+the behavior (even if it seems obvious). The more detailed and specific you are,
23
+the faster we will be able to help you. Check out
24
+[How to Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html).
25
+
26
+Please be kind, remember that Gitea comes at no cost to you, and you're
27
+getting free help.
28
+
11 29
 ## Discuss your design
12 30
 
13 31
 The project welcomes submissions but please let everyone know what
14 32
 you're working on if you want to change or add something to the Gitea repositories.
15 33
 
16 34
 Before starting to write something new for the Gitea project,
17
-please [file an issue](https://github.com/go-gitea/gitea/issues/new).
35
+please [file an issue](https://github.com/go-gitea/gitea/issues/new).  
18 36
 Significant changes must go through the
19 37
 [change proposal process](https://github.com/go-gitea/proposals)
20 38
 before they can be accepted.
@@ -42,6 +60,22 @@ Changes to Gitea must be reviewed before they are accepted,
42 60
 no matter who makes the change even if an owners or a maintainer.
43 61
 We use github's pull request workflow to do that and use [lgtm](http://lgtm.co) to ensure every PR is reviewed by at least 2 maintainers.
44 62
 
63
+## Sign your work
64
+
65
+The sign-off is a simple line at the end of the explanation for the patch. Your
66
+signature certifies that you wrote the patch or otherwise have the right to pass
67
+it on as an open-source patch. The rules are pretty simple: If you can certify
68
+[DCO](DCO), then you just add a line to every git commit message:
69
+
70
+```
71
+Signed-off-by: Joe Smith <joe.smith@email.com>
72
+```
73
+
74
+Please use your real name, we really dislike pseudonyms or anonymous
75
+contributions. We are in the opensource world without secrets. If you set your
76
+`user.name` and `user.email` git configs, you can sign your commit automatically
77
+with `git commit -s`.
78
+
45 79
 ## Contributors
46 80
 
47 81
 Everyone who sent a PR to Gitea that gets accepted will be as a contributor. Please send a PR to add your name to
@@ -69,7 +103,7 @@ I'm glad to be an owner of Gitea, I agree with [CONTRIBUTING](CONTRIBUTING.md).
69 103
 
70 104
 For a honor to the owners, this document will add the history owners below:
71 105
 
72
-2016-11-04 ~ 2017-12-31 lunny<xiaolunwen@gmail.com> tboerger<thomas@webhippie.de> bkcsoft<kim.carlbacker@gmail.com>
106
+2016-11-04 ~ 2017-12-31 lunny <xiaolunwen@gmail.com> tboerger <thomas@webhippie.de> bkcsoft <kim.carlbacker@gmail.com>
73 107
 
74 108
 ## Versions
75 109
 

+ 36 - 0
DCO

@@ -0,0 +1,36 @@
1
+Developer Certificate of Origin
2
+Version 1.1
3
+
4
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
5
+660 York Street, Suite 102,
6
+San Francisco, CA 94110 USA
7
+
8
+Everyone is permitted to copy and distribute verbatim copies of this
9
+license document, but changing it is not allowed.
10
+
11
+
12
+Developer's Certificate of Origin 1.1
13
+
14
+By making a contribution to this project, I certify that:
15
+
16
+(a) The contribution was created in whole or in part by me and I
17
+    have the right to submit it under the open source license
18
+    indicated in the file; or
19
+
20
+(b) The contribution is based upon previous work that, to the best
21
+    of my knowledge, is covered under an appropriate open source
22
+    license and I have the right under that license to submit that
23
+    work with modifications, whether created in whole or in part
24
+    by me, under the same open source license (unless I am
25
+    permitted to submit under a different license), as indicated
26
+    in the file; or
27
+
28
+(c) The contribution was provided directly to me by some other
29
+    person who certified (a), (b) or (c) and I have not modified
30
+    it.
31
+
32
+(d) I understand and agree that this project and the contribution
33
+    are public and that a record of the contribution (including all
34
+    personal information I submit with it, including my sign-off) is
35
+    maintained indefinitely and may be redistributed consistent with
36
+    this project or the open source license(s) involved.