Skip to content
This repository was archived by the owner on May 28, 2025. It is now read-only.

Commit 6250ebe

Browse files
author
ebartkus
committed
initial commit
1 parent 93cfc36 commit 6250ebe

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

52 files changed

+5949
-12
lines changed

‎.gitignore

Lines changed: 19 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,18 @@
1-
# Compiled class file
2-
*.class
1+
local-*
2+
.idea
3+
*.iml
4+
.gradle
5+
build/
6+
out/
37

4-
# Log file
5-
*.log
8+
# Ignore Gradle GUI config
9+
gradle-app.setting
610

7-
# BlueJ files
8-
*.ctxt
9-
10-
# Mobile Tools for Java (J2ME)
11-
.mtj.tmp/
11+
# Cache of project
12+
.gradletasknamecache
1213

14+
# # Work around https://youtrack.jetbrains.com/issue/IDEA-116898
15+
# gradle/wrapper/gradle-wrapper.properties
1316
# Package Files #
1417
*.jar
1518
*.war
@@ -19,5 +22,10 @@
1922
*.tar.gz
2023
*.rar
2124

22-
# virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
23-
hs_err_pid*
25+
.settings
26+
.project
27+
.classpath
28+
bin
29+
30+
.vscode
31+
.DS_Store

‎.travis.yml

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
language: java
2+
3+
before_cache:
4+
- rm -f $HOME/.gradle/caches/modules-2/modules-2.lock
5+
- rm -fr $HOME/.gradle/caches/*/plugin-resolution/
6+
cache:
7+
directories:
8+
- $HOME/.gradle/caches/
9+
- $HOME/.gradle/wrapper/
10+
script:
11+
- ./gradlew build --build-cache -PwarningsAsErrors=true
12+
- ./gradlew shadowJar
13+
14+
deploy:
15+
provider: releases
16+
api_key: "$GITHUB_TOKEN"
17+
file: "build/libs/datalake-kafka-connect-dynamodb-${TRAVIS_TAG}.jar"
18+
skip_cleanup: true
19+
on:
20+
tags: true

‎CODE_OF_CONDUCT.md

Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies within all project spaces, and it also applies when
49+
an individual is representing the project or its community in public spaces.
50+
Examples of representing a project or community include using an official
51+
project e-mail address, posting via an official social media account, or acting
52+
as an appointed representative at an online or offline event. Representation of
53+
a project may be further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at [email protected]. All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72+
73+
[homepage]: https://www.contributor-covenant.org
74+
75+
For answers to common questions about this code of conduct, see
76+
https://www.contributor-covenant.org/faq

‎CONTRIBUTING.md

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
# Contributing to kafka-connect-dynamodb
2+
We want to make contributing to this project as easy and transparent as possible, whether it's:
3+
4+
- Reporting a bug
5+
- Discussing the current state of the code
6+
- Submitting a fix
7+
- Proposing new features
8+
- Becoming a maintainer
9+
10+
## Our Development Process
11+
We use GitHub to sync code to and from our internal repository. We'll use GitHub
12+
to track issues and feature requests, as well as accept pull requests.
13+
14+
## We Use [Github Flow](https://guides.github.com/introduction/flow/index.html)
15+
Pull requests are the best way to propose changes to the codebase
16+
(we use [Github Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
17+
18+
0. Create GitHub issue and discuss proposed changes.
19+
1. Fork the repo and create your branch from `master`.
20+
2. If you've added code that should be tested, add tests.
21+
3. If you've changed APIs, update the documentation.
22+
4. Ensure the test suite passes.
23+
5. Make sure your code lints/follows general repository conventions.
24+
6. Issue pull request.
25+
26+
## Report bugs using Github's issues
27+
We use GitHub issues to track public bugs. Please ensure your description is
28+
clear and has sufficient instructions to be able to reproduce the issue.
29+
30+
**Great Bug Reports** tend to have:
31+
32+
- A quick summary and/or background
33+
- Steps to reproduce
34+
- Be specific
35+
- Give sample code if you can
36+
- What you expected would happen
37+
- What actually happens
38+
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
39+
40+
## License
41+
By contributing, you agree that your contributions will be licensed under its MIT License.
42+
43+
## References
44+
This document was adapted from the open-source contribution guidelines for
45+
[Facebook's Draft](https://github.com/facebook/draft-js/blob/a9316a723f9e918afde44dea68b5f9f39b7d9b00/CONTRIBUTING.md)
46+
and [briandk](https://gist.github.com/briandk/3d2e8b3ec8daf5a27a62)

0 commit comments

Comments
 (0)