Annotation of kupu/doc/CONTRIBUTING.txt, revision 1.1.1.1
1.1 dwinter 1: ====================
2: Contributing to kupu
3: ====================
4:
5: Who can contribute?
6: -------------------
7:
8: Anyone. If possible, you will be given appropriate credit in the
9: CREDITS.txt file. In case we should not mention you, please write us an
10: email.
11:
12: How can I contribute?
13: ---------------------
14:
15: For small contributions, please send an email with a UNIX patchfile attached
16: to kupu-dev@codespeak.net. Make sure you say what version the patch applies
17: to, what it changes and why this was necessary.
18:
19: Alternatively, you can submit bug reports and/or patches to the issue
20: tracker: http://codespeak.net/issues/kupu/ (mind the trailing slash).
21:
22: If you have written a target-platform customization layer for kupu and would
23: like us to include it in the main distribution, please send a detailed email
24: to kupu-dev@codespeak.net. Depending on our decision whether to include it or
25: not, you will receive SVN checkin rights. You will then also be responsible
26: for maintaining this customization layer.
27:
28: What are the rules?
29: -------------------
30:
31: 1. Contributions must only only contain code written by you. You may
32: not contribute code copyrighted by anyone else. You will be held
33: responsible if you violate this rule.
34:
35: 2. By contributing, you agree that the code contributed by you will be
36: published in the kupu distribution under the Kupu License. See
37: LICENSE.txt for license text.
38:
39: 3. Code in the kupu/common layer may not contain any platform specific
40: code, neither the ZPT macros nor the JavaScript. The unwritten law is:
41: The common layer shall be viewable in a web browser directly off of
42: the filesystem.
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>