Skip to content

Commit 4d706b2

Browse files
authored
Add Apache License V2 (#98)
* Add Apache License V2, PR template, contributing guidelines --------- Co-authored-by: Madhavan Sridharan <[email protected]>
1 parent 5bf3b9f commit 4d706b2

File tree

3 files changed

+37
-2
lines changed

3 files changed

+37
-2
lines changed

.github/pull_request_template.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
<!-- Thanks for sending a pull request! -->
2+
3+
**What this PR does**:
4+
5+
**Which issue(s) this PR fixes**:
6+
Fixes #<issue number>
7+
8+
**Checklist:**
9+
- [ ] Automated Tests added/updated
10+
- [ ] Documentation added/updated
11+
- [ ] CLA Signed: [DataStax CLA](https://cla.datastax.com/)

CONTRIBUTING.md

Lines changed: 24 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,26 @@ get started are described here.
3232
address a non-trivial issue that has been reported, you can follow the steps that the original user
3333
reported. Updating issues with such findings is immensely helpful to the maintainers.
3434

35+
### Commits
36+
37+
Keep your changes **focused**. Each commit should have a single, clear purpose expressed in its
38+
message.
39+
40+
Resist the urge to "fix" cosmetic issues (add/remove blank lines, move methods, etc.) in existing
41+
code. This adds cognitive load for reviewers, who have to figure out which changes are relevant to
42+
the actual issue. If you see legitimate issues, like typos, address them in a separate commit (it's
43+
fine to group multiple typo fixes in a single commit).
44+
45+
Commit message subjects start with a capital letter, use the imperative form and do **not** end
46+
with a period.
47+
48+
Avoid catch-all messages like "Minor cleanup", "Various fixes", etc. They don't provide any useful
49+
information to reviewers, and might be a sign that your commit contains unrelated changes.
50+
51+
We don't enforce a particular subject line length limit, but try to keep it short.
52+
53+
You can add more details after the subject line, separated by a blank line.
54+
3555
### Pull Requests
3656

3757
All contributions to this project are made in the form of pull requests, including:
@@ -55,6 +75,9 @@ All contributions to this project are made in the form of pull requests, includi
5575
and requires some study of the codebase. If you take the time to understand the code a bit before submitting
5676
pull requests, then the maintainers will take the time to help you make your pull requests better.
5777

78+
- Like commits, pull requests should be focused on a single, clearly stated goal.
79+
Contributors need to sign the [DataStax CLA](https://cla.datastax.com/).
80+
5881
### Maintainers
5982

6083
We are looking for more community ownership in this project. That means that we will be supportive of
@@ -133,4 +156,4 @@ For recognizing contributions, please follow [this documentation](https://allcon
133156

134157
<!-- ALL-CONTRIBUTORS-LIST:END -->
135158

136-
---
159+
---

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
[![License Apache2](https://img.shields.io/hexpm/l/plug.svg)](http://www.apache.org/licenses/LICENSE-2.0)
12
[![Star on Github](https://img.shields.io/github/stars/datastax/cassandra-data-migrator.svg?style=social)](https://github.com/datastax/cassandra-data-migrator/stargazers)
23

34
# cassandra-data-migrator
@@ -114,4 +115,4 @@ This mode is specifically useful to processes a subset of partition-ranges that
114115
# Contributors
115116
Checkout all our wonderful contributors [here](./CONTRIBUTING.md#contributors).
116117

117-
---
118+
---

0 commit comments

Comments
 (0)