summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndreas Fankhauser hiddenalpha.ch2022-12-23 23:47:53 +0100
committerAndreas Fankhauser hiddenalpha.ch2022-12-23 23:47:53 +0100
commitfeb267dd2020267c4a9264a669c0f0c046c8dc5d (patch)
tree99521ec32c792d26e1e5b1e4dc48023e67010265
parente3450fca17fdeb5f64df260b224916b6b2cbdb73 (diff)
downloadxtra4j-feb267dd2020267c4a9264a669c0f0c046c8dc5d.zip
xtra4j-feb267dd2020267c4a9264a669c0f0c046c8dc5d.tar.gz
Add a "contributing" file
-rw-r--r--CONTRIBUTING.txt28
1 files changed, 28 insertions, 0 deletions
diff --git a/CONTRIBUTING.txt b/CONTRIBUTING.txt
new file mode 100644
index 0000000..60b1bd5
--- /dev/null
+++ b/CONTRIBUTING.txt
@@ -0,0 +1,28 @@
+
+This project is NOT open for direct contributions (you may still
+contribute by providing patches for download somewhere else for
+example).
+
+You still can open a PR if you like. But it may be not accepted, or even
+just ignored.
+
+If the PR is accepted or not, solely depends on this projects original
+authors opinion. There are NO objective "rules" or similar that need to
+be fulfilled for a PR to get merged. It only gets merged if the original
+author thinks he should merge it.
+
+For example there are neither any formatting rules nor is there any
+definition of what kind of changes even are allowed in this project. (As
+already said) this fully depends on the original authors opinion and
+even facts are not accepted as arguments.
+
+Be aware that opinions are no hard rules too. Therefore they can change
+at will. Only because a similar decision was made earlier, does not mean
+that now a similar approach is acceptable.
+
+Further, the original projects author may apply any changes of any kind
+before or after merging a contribution.
+
+If a PR does not get merged, it is recommended to publish your work as
+patch files somewhere outside this repository.
+