Re: Re: Updating our contributions guide

2019-07-16 Thread Matt Rutkowski
ading that", "never saw that link", "i never explicitly agreed to that" (i.e., is it legally binding)? From: James Thomas To: dev@openwhisk.apache.org Date: 07/16/2019 07:29 AM Subject: [EXTERNAL] Re: Updating our contributions guide On Sat, 13 Jul 2019 at 22:07

Re: Updating our contributions guide

2019-07-16 Thread James Thomas
On Sat, 13 Jul 2019 at 22:07, Matt Sicker wrote: > > I've looked around for some existing guidelines around CLA > requirements, and so far I've found this: > > https://www.apache.org/licenses/contributor-agreements.html#clas > > So basically, the general idea I've seen is that small, trivial >

Re: Updating our contributions guide

2019-07-13 Thread Rodric Rabbah
Thanks Matt. One of the improvements I thought I’d make is to explain exactly this: when a cla is required and when we can accept improvements to documentation, typos, minors fixes etc. without. -r > On Jul 13, 2019, at 5:07 PM, Matt Sicker wrote: > > I've looked around for some existing

Re: Updating our contributions guide

2019-07-13 Thread Matt Sicker
I've looked around for some existing guidelines around CLA requirements, and so far I've found this: https://www.apache.org/licenses/contributor-agreements.html#clas This relates eventually to the provenance of source code hosted at the ASF:

Updating our contributions guide

2019-07-09 Thread Rodric Rabbah
It was pointed out that our contributing guide sets a higher bar than other Apache projects by requiring an ICLA. Looking at some of the other successful Apache projects they do a better job explaining how to contribute, and all the ways someone can be contributor, and how to open a PR,