[
https://issues.apache.org/jira/browse/METRON-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16302403#comment-16302403
]
ASF GitHub Bot commented on METRON-1071:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/881
@ottobackwards I think you're right, we should have the header in the MD
files. I looked back at the discussion you kicked off, the general agreement
was that we should, but we didn't follow up.
I've added it here and validated that it doesn't show up in the rendering
on GitHub or in the site-book. I'll be creating a Jira and PR to add it to the
remaining markdown files, and removing the exclusion from the rat.
@JonZeolla You okay with this change?
> 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)
