Add v0.1.0 codebase

.github/workflows/unit_tests.yml

@@ -0,0 +1,14 @@
+name: CI
+
+on: [push]
+
+jobs:
+  unit-tests:
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v1
+      - name: Unit tests
+        run: ant test
+

.gitignore

@@ -11,7 +11,6 @@
 .mtj.tmp/
 
 # Package Files #
-*.jar
 *.war
 *.nar
 *.ear
@@ -21,3 +20,12 @@
 
 # virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
 hs_err_pid*
+
+# IntelliJ IDEA files
+.idea/
+
+# Output directory for generated class files
+bin/
+
+# Output directory for distribution
+dist/

CONTRIBUTING.md

@@ -0,0 +1,32 @@
+# Contributing
+
+Prior to submitting a PR, please ensure that:
+
+1. The proposed change has been clearly documented and motivated in a GitHub issue and discussed with the owners of this repository.
+2. There is no existing or obsolete ticket which addresses your proposed change.
+
+## Build Requirements
+
+* Java 8 or later
+* [Ant](https://ant.apache.org/) 1.10.7 or later
+
+## Build and Run
+
+     $ ant
+     $ java -jar dist/aldb.jar
+
+## Running Tests
+
+     $ ant test
+     
+## Pull Request Process
+
+1. Ensure your code builds successfully.
+2. Test your changes manually if possible by running the JAR and manipulating a non-trivial model if applicable.
+3. Ensure that existing tests pass.
+4. Ensure that you have added new tests where necessary.
+5. Write a descriptive and concise commit message, PR title, and description.
+6. Ensure that a GitHub issue is referenced in the PR description with a `Closes` statement.
+7. Create your PR.
+8. Once all status checks pass, assign one or more owners as reviewers.
+9. Once you have at least one approval from an owner, you can squash and merge your PR.