Re: [DISCUSS] Easing the ramp-up into contributing

I created METRON-1071 to track the CONTRIBUTING.md. I also called out personal Travis setup instructions, because that's pretty closely tied our dev experience and seems like a good place to let it live. On Fri, Jul 28, 2017 at 1:43 PM, Michael

Re: [DISCUSS] Easing the ramp-up into contributing

Hi Artem, You could probably get away with not running them locally since we use Travis, which functions similarly to Jenkins from a testing perspective. Additionally, you can hook up Travis to run on your own github account as many Metron committers have already done. The upshot is that if your

Re: [DISCUSS] Easing the ramp-up into contributing

Being new to this community and attempting to contribute METRON-1058, METRON-1059 and METRON-1063, my experience is that requirement to run the full tests and integration tests in order to contribute even a simple patch is overkill. I understand that community wants high quality contributions but

Re: [DISCUSS] Easing the ramp-up into contributing

Really good discussion thread, thanks for opening it Justin. I’m a fan of adding javadocs to the publicly available doc set. It’s not the most important of the items listed below, but it is easy, and will push people to be more attentive to dev documentation. METRON-759 is open for that, and

Re: [DISCUSS] Easing the ramp-up into contributing

Beyond this, I think we need to encourage PR review and testing as a way to contribute, along with documentation. So things that help with those topics will be good. Maybe an expended "ways to get involved including”, and why they are important. Increased participation leading to PR’s that don’t