Initial implementation

Author: creativcoder

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+liberapay: creativcoder
+custom: ["https://www.buymeacoffee.com/creativcoder"]

.github/ISSUE_TEMPLATE/1-problem.md

@@ -0,0 +1,5 @@
+---
+name: Problem
+about: Something does not seem right
+
+---

.github/ISSUE_TEMPLATE/2-suggestion.md

@@ -0,0 +1,5 @@
+---
+name: Suggestion
+about: Share how Avrow could support your use case better
+
+---

.github/ISSUE_TEMPLATE/3-documentation.md

@@ -0,0 +1,5 @@
+---
+name: Documentation
+about: Certainly there is room for improvement
+
+---

.github/workflows/ci.yml

@@ -0,0 +1,54 @@
+on: [push, pull_request]
+
+jobs:
+  linux:
+    name: Test Suite (linux)
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        rust:
+          - stable
+          - nightly
+          - 1.37.0
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions-rs/toolchain@v1
+        with:
+          toolchain: ${{ matrix.rust }}
+      - run: cargo test --release --all-features
+
+  windows:
+    name: Test suite (windows)
+    runs-on: windows-latest
+    steps:
+      - uses: actions/checkout@v2
+        with:
+          toolchain: ${{ matrix.rust }}
+      - run: cargo test --all-features
+
+  lints:
+    name: Lints
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout sources
+        uses: actions/checkout@v2
+
+      - name: Install stable toolchain
+        uses: actions-rs/toolchain@v1
+        with:
+          profile: minimal
+          toolchain: stable
+          override: true
+          components: rustfmt, clippy
+
+      - name: Run cargo fmt
+        uses: actions-rs/cargo@v1
+        with:
+          command: fmt
+          args: --all -- --check
+
+      - name: Run cargo clippy
+        uses: actions-rs/cargo@v1
+        with:
+          command: clippy
+          args: -- -D warnings

.gitignore

@@ -0,0 +1,11 @@
+
+/target
+**/*.rs.bk
+Cargo.lock
+NOTES.md
+*.avro
+*.jar
+experiments/
+TODO.md
+# .vscode
+avrow-cli/target

.vscode/launch.json

@@ -0,0 +1,16 @@
+{
+    // Use IntelliSense to learn about possible attributes.
+    // Hover to view descriptions of existing attributes.
+    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
+    "version": "0.2.0",
+    "configurations": [
+        {
+            "type": "lldb",
+            "request": "launch",
+            "name": "Debug",
+            "program": "${workspaceFolder}/<your program>",
+            "args": [],
+            "cwd": "${workspaceFolder}"
+        }
+    ]
+}

CHANGELOG.md

@@ -0,0 +1,16 @@
+# Changelog
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+# [Unreleased]
+
+
+# [0.1.0] - 2020-10-08
+
+## Added
+
+Initial implementation of
+- avrow
+- avrow-cli (av)

CODE_OF_CONDUCT.md

@@ -0,0 +1,75 @@
+
+## Code of Conduct
+
+### Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+### Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+### Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+### Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,26 @@
+
+# Contributing
+
+When contributing to this repository, please first discuss the change you wish to make via issue,
+email, or any other method with the owners of this repository before making a change. 
+
+Please note we have a [code of conduct](./CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
+
+## Pull Request Process
+
+Following is a cursory guideline on how to make the process of making changes more efficient for the contributer and the maintainer.
+
+1. File an issue for the change you want to make. This way we can track the why of the change. 
+   Get consensus from community for the change.
+2. Clone the project and perform a fresh build. Create a branch with the naming "feature/issue-number.
+3. Ensure that the PR only changes the parts of code which implements/solves the issue. This includes running
+   the linter (cargo fmt) and removing any extra spaces and any formatting that accidentally were made by
+   the code editor in use.
+4. If your PR has changes that should also reflect in README.md, please update that as well.
+5. Document non obvious changes and the `why` of your changes if it's unclear. 
+6. If you are adding a public API, add the documentation as well.
+7. Increase the version numbers in Cargo.toml files and the README.md to the new version that this
+   Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
+8. Update the CHANGELOG.md to reflect the change if applicable.
+
+More details: https://github.community/t/best-practices-for-pull-requests/10195