Merge pull request #23 from aiv01/release_v0.9.0

Technical Relase v0.9.0

.travis.yml

@@ -0,0 +1,66 @@
+language: csharp
+solution: aiv-fast3d.sln
+notifications:
+  #email: false
+  email:
+    if: branch = master
+    on_success: true
+    on_failure: true
+before_script:
+  - export AUTO_PATH_SLN=aiv-fast3d.sln
+  - export AUTO_PATH_LIBR_REL=aiv-fast3d/bin/Release
+  - export AUTO_PATH_LIBR_DLL=$AUTO_PATH_LIBR_REL/aiv-fast3d.dll
+  ##### - export AUTO_PATH_TEST_DLL=Tests/bin/Release/Tests.dll
+  - export AUTO_PATH_NUSPEC=aiv-fast3d.nuspec
+  - export AUTO_PATH_DOCS=auto-docs/html
+  - export AUTO_PATH_ARTIFACTS=artifacts
+  - export AUTO_YEAR=$(date +%Y)
+  - export AUTO_TAG=$(if [ -z "$TRAVIS_TAG" ]; then echo "0.0.0"; else echo $TRAVIS_TAG; fi) 
+  # Need to stop build if TAG is not like X.Y.Z(.A)
+  # Workaround becase doesn't exists TAG EXCLUSION mechanism for build
+  # https://docs.travis-ci.com/user/customizing-the-build#using-regular-expressions
+  - export AUTO_TAG_REGEX="^[0-9]+(\.[0-9]+){2,3}$"
+  - if [[ ! $AUTO_TAG =~ $AUTO_TAG_REGEX ]]; then echo "Tag '$AUTO_TAG' is not valid. Build will be terminated" && travis_terminate 1; fi
+script:
+  - echo "=== INSTALL ==="
+    && nuget restore $AUTO_PATH_SLN
+    && sudo apt-get install doxygen
+  - echo "=== BUILD ===" 
+    && msbuild /p:Configuration=Release $AUTO_PATH_SLN
+    && ls -l $AUTO_PATH_LIBR_DLL
+  ##### - echo "=== TEST ==="
+  ##### && packages/NUnit.ConsoleRunner.3.*/tools/nunit3-console.exe $AUTO_PATH_TEST_DLL
+  - echo "=== PACKAGE ===" 
+    && sed -i "s/@AUTO_TAG/$AUTO_TAG/" $AUTO_PATH_NUSPEC
+    && sed -i "s/@AUTO_YEAR/$AUTO_YEAR/" $AUTO_PATH_NUSPEC
+    && cat $AUTO_PATH_NUSPEC
+    && nuget pack $AUTO_PATH_NUSPEC -Verbosity detailed
+  - echo "=== DOCUMENTATION ===" 
+    && doxygen
+    && zip -r docs.zip $AUTO_PATH_DOCS
+  - echo "=== ARTIFACTS ==="
+    && mkdir $AUTO_PATH_ARTIFACTS
+    && cp *.nupkg             $AUTO_PATH_ARTIFACTS
+    && mv docs.zip            $AUTO_PATH_ARTIFACTS
+    && ls -l $AUTO_PATH_ARTIFACTS 
+deploy:
+  - provider: script
+    script: nuget push ./*.nupkg -Verbosity detailed -ApiKey $NUGET_API_KEY -Source $NUGET_SOURCE
+    on:
+      tags: true
+    skip_cleanup: true
+
+  - provider: pages
+    github_token: $GITHUB_API_KEY
+    local_dir: $AUTO_PATH_DOCS
+    on:
+      tags: true
+    skip_cleanup: true
+
+  - provider: releases
+    api_key: $GITHUB_API_KEY
+    file_glob: true
+    file: $AUTO_PATH_ARTIFACTS/*
+    on:
+      tags: true
+    skip_cleanup: true

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant 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, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, 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. 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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,25 @@
+# Reporting an Issue
+To ask for support, enhancement, new feature or to state a bug open a dedicated issue as detailed as possible.
+
+# Working an Issue
+To Contribute to an issue:
+- if you are a **Contributor**, just Assign yourself the issue. A branch will be automatically created with the pattern issue-N-title. Make sure when pushing that your branch will pass Continuos Integration.
+- if you are an external contributor, fork this repository to your account following github flux.
+
+When you are ready to submit your work, open a **Pull Request** (in case of fork follow [this](https://help.github.com/articles/creating-a-pull-request-from-a-fork/)) declaring in the description which issue will close (like: "Closes #11"). 
+Minumum requirement, for the Pull Request, to be accepted is to pass Continuous Integration check.
+
+# Releasing new version
+Release process can be executed by Maintainers:
+1. [Github] Merge on "master" branch. Better with a Pull Request.
+1. [Github] Draft New Release named "X.Y.Z". NOTE: This will trigger travis automation
+1. [Travis] Wait for travis. In the end:
+  * package is published on Nuget
+  * api docs is published on Github Pages
+  * artifacts are uploaded to the Github Release
+
+# License
+Any kind of contribution to this project will be subject to [GNU](LICENSE) license.
+
+# Code of Conduct
+Remember: any actions taken on this project must respect Code of Conduct defined [here](CODE_OF_CONDUCT.md).

CONTRIBUTORS

@@ -0,0 +1,3 @@
+Roberto De Ioris
+Matteo Chironi
+Federico De Felici