[
https://issues.apache.org/jira/browse/METRON-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16302138#comment-16302138
]
ASF GitHub Bot commented on METRON-1071:
----------------------------------------
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/881#discussion_r158571753
--- Diff: CONTRIBUTING.md ---
@@ -0,0 +1,27 @@
+# How To Contribute
+As an open source project, Metron welcomes contributions of all forms.
There are several great ways to contribute!
+
+* [Contributing a Code Change](#contributing-a-code-change)
+* Reviewing pull requests on our GitHub page. Check out current open [Pull
Requests](https://github.com/apache/metron/pulls)
+* Improve our documentation. Our docs are self contained in the project in
README files. Doc changes is the same process as a code change. See
[Contributing a Code Change](#contributing-a-code-change)
--- End diff --
Good catch. Changed it.
> Create CONTRIBUTING.md
> ----------------------
>
> Key: METRON-1071
> URL: https://issues.apache.org/jira/browse/METRON-1071
> Project: Metron
> Issue Type: Improvement
> Reporter: Justin Leet
> Assignee: Justin Leet
>
> The idea is to have a document on contributing to Metron that lives alongside
> our code (and we can then move away from the wiki). This document should
> have a couple things in it:
> * What we look for from code contributions
> * How people can actually contribute code
> * How people can contribute, even without code (e.g. reviews)
> * Helpful things like setting up Travis on personal repos to avoid full
> testing time locally.
> It should also integrate nicely with the site-book, so just make sure
> everything plays nicely.
> See: https://github.com/blog/1184-contributing-guidelines
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
