aboutsummaryrefslogtreecommitdiffhomepage
path: root/third_party/nanopb/CONTRIBUTING.md
diff options
context:
space:
mode:
authorGravatar Nicolas "Pixel" Noble <pixel@nobis-crew.org>2016-09-29 01:31:54 +0200
committerGravatar Nicolas "Pixel" Noble <pixel@nobis-crew.org>2016-09-29 01:31:54 +0200
commit87a108121134e9603e3e60e732b23cbeb619be14 (patch)
treef19efe6ed3dc6706b21fc9138a975fce74d66783 /third_party/nanopb/CONTRIBUTING.md
parentb97f867b390193daf18988958183143726602727 (diff)
parent4f13db3c6cfaae52b6d7e35edaa352bccff70b66 (diff)
Merge remote-tracking branch 'google/v1.0.x' into master-upmerge-from-deep-under
Diffstat (limited to 'third_party/nanopb/CONTRIBUTING.md')
-rw-r--r--third_party/nanopb/CONTRIBUTING.md32
1 files changed, 32 insertions, 0 deletions
diff --git a/third_party/nanopb/CONTRIBUTING.md b/third_party/nanopb/CONTRIBUTING.md
new file mode 100644
index 0000000000..4041bc3caf
--- /dev/null
+++ b/third_party/nanopb/CONTRIBUTING.md
@@ -0,0 +1,32 @@
+Contributing to Nanopb development
+==================================
+
+Reporting issues and requesting features
+----------------------------------------
+
+Feel free to report any issues you see or features you would like
+to see in the future to the Github issue tracker. Using the templates
+below is preferred:
+
+* [Report a bug](https://github.com/nanopb/nanopb/issues/new?body=**Steps%20to%20reproduce%20the%20issue**%0a%0a1.%0a2.%0a3.%0a%0a**What%20happens?**%0A%0A**What%20should%20happen?**&labels=Type-Defect)
+* [Request a feature](https://github.com/nanopb/nanopb/issues/new?body=**What%20should%20the%20feature%20do?**%0A%0A**In%20what%20situation%20would%20the%20feature%20be%20useful?**&labels=Type-Enhancement)
+
+Requesting help
+---------------
+
+If there is something strange going on, but you do not know if
+it is actually a bug in nanopb, try asking first on the
+[discussion forum](https://groups.google.com/forum/#!forum/nanopb).
+
+Pull requests
+-------------
+
+Pull requests are welcome!
+
+If it is not obvious from the commit message, please indicate the
+same information as you would for an issue report:
+
+* What functionality it fixes/adds.
+* How can the problem be reproduced / when would the feature be useful.
+
+