Hi,

We use in more of repositories PR template like:

===============================================
Following this checklist to help us incorporate your
contribution quickly and easily:

 - [ ] Make sure there is a [JIRA issue](
https://issues.apache.org/jira/browse/<projectKey>) filed
       for the change (usually before you start working on it).  Trivial
changes like typos do not
       require a JIRA issue.  Your pull request should address just this
issue, without
       pulling in other changes.
 - [ ] Each commit in the pull request should have a meaningful subject
line and body.
 - [ ] Format the pull request title like `[<key>-XXX] - Fixes bug in
ApproximateQuantiles`,
       where you replace `MWRAPPER-XXX` with the appropriate JIRA issue.
Best practice
       is to use the JIRA issue title in the pull request title and in the
first line of the
       commit message.
 - [ ] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
 - [ ] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will
       be performed on your pull request automatically.
 - [ ] You have run the integration tests successfully (`mvn -Prun-its
clean verify`).

If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License Agreement](
https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the [Apache License Version 2.0, January 2004](
http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.

 - [ ] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](
http://www.apache.org/licenses/LICENSE-2.0)

 - [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).

===============================================

We prefer linear history on default branches ...
So the questions:

1. Should we add a checkbox about squashing, one commit per PR?
Of course - we can squash commits during merge - should we inform the
contributors about it?

2. Why when PR has less than 20 lines changes we don;t require CLA?
Can we accept PR with more than 20 lines and without CLA?
Even more, can we accept any PR without CLA?

We can read on tha ASF page [1]:
  All contributors of ideas, code, or documentation to any Apache projects
must complete, sign, and submit via email an Individual Contributor License
Agreement (ICLA).

3. Should we mention CCLA?


[1] https://www.apache.org/licenses/contributor-agreements.html

-- 
Sławomir Jaranowski

Reply via email to