|
a/CONTRIBUTING |
|
b/CONTRIBUTING |
|
... |
|
... |
| 33 |
|
33 |
|
| 34 |
- REPORTING BUGS
|
34 |
- REPORTING BUGS
|
| 35 |
|
35 |
|
| 36 |
Report bugs to our public tracker at:
|
36 |
Report bugs to our public tracker at:
|
| 37 |
|
37 |
|
| 38 |
<http://sf.net/support>
|
38 |
<https://sourceforge.net/p/allura/tickets/>
|
| 39 |
|
39 |
|
| 40 |
Four things make for a good bug report:
|
40 |
Four things make for a good bug report:
|
| 41 |
|
41 |
|
| 42 |
+ it's not a duplicate of an existing bug
|
42 |
+ it's not a duplicate of an existing bug
|
| 43 |
|
43 |
|
|
... |
|
... |
| 71 |
- CONTRIBUTING CODE
|
71 |
- CONTRIBUTING CODE
|
| 72 |
|
72 |
|
| 73 |
Develop and test your patches locally and then get them to us in one of
|
73 |
Develop and test your patches locally and then get them to us in one of
|
| 74 |
two ways:
|
74 |
two ways:
|
| 75 |
|
75 |
|
| 76 |
+ use the git tools format-patch and send-email to send your patches
|
|
|
| 77 |
to the mailing list
|
|
|
| 78 |
|
|
|
| 79 |
<mailto:develop@discussion.allura.p.re.sf.net>
|
|
|
| 80 |
|
|
|
| 81 |
+ push your changes up to your 'forked' repo, and from there send us
|
76 |
+ push your changes up to your 'forked' repo, and from there send us
|
| 82 |
a merge request
|
77 |
a merge request
|
|
|
78 |
|
|
|
79 |
+ attach a patch file to a ticket
|
| 83 |
|
80 |
|
| 84 |
Things your patch-sequence must have/do:
|
81 |
Things your patch-sequence must have/do:
|
| 85 |
|
82 |
|
| 86 |
+ follow PEP-8 <http://www.python.org/dev/peps/pep-0008/> coding
|
83 |
+ follow PEP-8 <http://www.python.org/dev/peps/pep-0008/> coding
|
| 87 |
guidelines
|
84 |
guidelines
|
| 88 |
|
|
|
| 89 |
+ signify that you have full and clear rights to the code you are
|
|
|
| 90 |
supplying and that you wish to share it under the terms of the
|
|
|
| 91 |
Apache License Version 2.0 by using git commit --signoff
|
|
|
| 92 |
|
85 |
|
| 93 |
+ contain appropriate tests to be added to the automated testing
|
86 |
+ contain appropriate tests to be added to the automated testing
|
| 94 |
machinery
|
87 |
machinery
|
| 95 |
|
88 |
|
| 96 |
+ pass existing tests (and/or fix existing tests that need to change)
|
89 |
+ pass existing tests (and/or fix existing tests that need to change)
|
|
... |
|
... |
| 115 |
We intend to develop "out in the open", which means having a public
|
108 |
We intend to develop "out in the open", which means having a public
|
| 116 |
discussion where we talk about new features, submitted patches, bugs,
|
109 |
discussion where we talk about new features, submitted patches, bugs,
|
| 117 |
direction, and deployment. You can join in the discussion on the
|
110 |
direction, and deployment. You can join in the discussion on the
|
| 118 |
mailing list:
|
111 |
mailing list:
|
| 119 |
|
112 |
|
| 120 |
<mailto:develop@discussion.allura.p.re.sf.net>
|
113 |
<http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/>
|
| 121 |
|
114 |
|
| 122 |
|
115 |
|
| 123 |
- ASKING QUESTIONS
|
116 |
- ASKING QUESTIONS
|
| 124 |
|
117 |
|
| 125 |
First, is your question already answered in the FAQ?
|
118 |
First, is your question already answered in the FAQ?
|