Fix: ansible-galaxy minus to underscore

.travis.yml

@@ -1,29 +1,30 @@
 ---
-# TODO: Build better testing for multiple containers and os support
 language: python
-python: "2.7"
+python:
+  - "2.7"
+  - "3.6"
 
 sudo: false
 
-# Install ansible
+# Install python-pip
 addons:
   apt:
     packages:
     - python-pip
+    - aspell
+    - aspell-en
 
 install:
   # Install ansible
   - pip install ansible
   - pip install ansible-lint
+  - pip install ansible-review
 
   # Check ansible version
   - ansible --version
 
-  # Create ansible.cfg with correct roles_path
-  - printf '[defaults]\nroles_path=../' >ansible.cfg
-
   # Link github repo to ansible-galaxy name
-  - ln -s  $PWD ../while-true-do.yum-cron
+  - ln -s  $PWD ../while_true_do.yum_cron
 
 # Run the tests
 script:
@@ -33,4 +34,9 @@ script:
   - tests/test-spelling.sh
 
 notifications:
-  webhooks: https://galaxy.ansible.com/api/v1/notifications/
+  webhooks:
+    urls:
+      - https://galaxy.ansible.com/api/v1/notifications/
+    on_success: always
+    on_failure: never
+    on_pull_requests: false

LICENSE

@@ -1,6 +1,3 @@
-------------------
-BSD 3 Clause
-------------------
 Copyright (c) 2018, While True Do
 All rights reserved.
 

README.md

@@ -1,6 +1,6 @@
 [![Build Status](https://travis-ci.org/while-true-do/ansible-role-yum-cron.svg?branch=master)](https://travis-ci.org/while-true-do/ansible-role-yum-cron)
 
-# Ansible Role: yum-cron 
+# Ansible Role: yum-cron
 | A role to install and configure yum-cron
 
 ## Motivation
@@ -9,25 +9,25 @@ Install and configure yum-cron to stay up to date.
 
 ## Installation
 
-Install from [Ansible Galaxy](https://galaxy.ansible.com/while-true-do/yum-cron)
+Install from [Ansible Galaxy](https://galaxy.ansible.com/while_true_do/yum_cron)
 
 ```
-ansible-galaxy install while-true-do.yum-cron
+ansible-galaxy install while_true_do.yum-cron
 ```
 
 Install from [Github](https://github.com/while-true-do/ansible-role-yum-cron)
 
 ```
-git clone https://github.com/while-true-do/ansible-role-yum-cron.git while-true-do.yum-cron
+git clone https://github.com/while-true-do/ansible-role-yum-cron.git while_true_do.yum-cron
 ```
 
 ## Requirements
 
 YUM must be /will be installed, of course.
-Its a good idea to configure yum, first. 
+Its a good idea to configure yum, first.
 
 You will find an ansible role here:
-<https://galaxy.ansible.com/while-true-do/yum>
+<https://galaxy.ansible.com/while_true_do/yum>
 <https://github.com/while-true-do/ansible-role-yum>
 
 Used Modules:
@@ -36,7 +36,7 @@ Used Modules:
 
 ## Dependencies
 
--   [while-true-do.yum](https://galaxy.ansible.com/while-true-do/yum/)
+-   [while-true-do.yum](https://galaxy.ansible.com/while_true_do/yum/)
 
 ```
 ansible-galaxy install -r requirements.yml
@@ -96,18 +96,18 @@ wtd_yum_cron_hourly_output_width: '80'
 Simple Example:
 
 ```
-- hosts: servers 
+- hosts: servers
   roles:
-    - { role: while-true-do.yum-cron }
+    - { role: while_true_do.yum_cron }
 ```
 
 Advanced Example:
 
 ```
 # To enable E-Mail Notifications
-- hosts: servers 
+- hosts: servers
   roles:
-    - { role: while-true-do.yum-cron, wtd_yum_cron_emit_via: 'email', wtd_yum_cron_email_to: '[email protected]' }
+    - { role: while_true_do.yum_cron, wtd_yum_cron_emit_via: 'email', wtd_yum_cron_email_to: '[email protected]' }
 ```
 
 ## Testing
@@ -125,7 +125,7 @@ bash ./tests/test-ansible.sh
 ## Contribute / Bugs
 
 Thank you so much for considering to contribute. Every contribution helps us.
-We are really happy, when somebody is joining the hard work. Please have a look 
+We are really happy, when somebody is joining the hard work. Please have a look
 at the links first.
 
 -   [Contribution Guidelines](./docs/CONTRIBUTING.md)

docs/CODE_OF_CONDUCT.md

@@ -0,0 +1,54 @@
+# Code of Conduct
+| While True Do Code of Conduct
+
+This guideline is only a snapshot. Please have a look [here](https://github.com/while-true-do/community/tree/master/docs) to check the latest version.
+
+## Welcome
+
+Welcome to While True Do. Thank you so much for considering to participate to our community and projects.
+
+In this document you can find some guidance how we take care and what we expect from our maintainers and contributors.
+
+## Contents
+
+-   [Vision](#Vision)
+-   [Standards](#Standards)
+-   [Responsibility](#Responsibility)
+-   [Enforcement](#Enforcement)
+-   [Attribution](#Attribution)
+
+## Vision
+
+We as contributors and maintainers want to establish a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Standards
+
+Examples of behaviour that contributes to creating a positive environment:
+
+-   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 behaviour by participants:
+
+-   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
+
+## Responsibility
+
+Project maintainers are responsible for clariying the standards of acceptable behaviour. They are expected to take corrective action in response to any instances of unacceptable behaviour.
+
+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 the Code of Conduct.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. 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.
+
+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, version 1.4, available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>

docs/COMMIT_TEMPLATE.md

@@ -1,8 +1,8 @@
 <!--
 Please have a look at the contribution guidelines and pull request template first.
 
-https://github.com/while-true-do/community/docs/CONTRIBUTING.md
-https://github.com/while-true-do/community/docs/PULL_REQUEST_TEMPLATE.md
+https://github.com/while-true-do/community/blob/master/docs/CONTRIBUTING.md
+https://github.com/while-true-do/community/blob/master/docs/PULL_REQUEST_TEMPLATE.md
 
 Nice to read:
 
@@ -11,11 +11,11 @@ https://chris.beams.io/posts/git-commit/
 
 # Commit Types
 
-- Fix: is solving an issue/problem
-- Rework: is refactoring something existing for stability or performance
+- Fix: Is solving an issue/problem
+- Rework: Is refactoring something existing for stability or performance
 - Add: Is adding a feature or enhancing an existing one
 - Update: Mostly for updating documentation or dependencies
-- Polish: Something which is "finishing" a work
+- Polish: Something which is "the finishing touch"
 - Remove: If a feature/function is entirely dropped
 
 # Commit Template
@@ -32,7 +32,7 @@ Further paragraphs come after blank lines, if needed.
  - Bullet points are okay, too.
  - A hyphen or asterisk is used for the bullet, preceded by a single space and can
    be wrapped around.
-   
+
  - Resolves: #12
  - See also: #33, #44
 ```

docs/CONTRIBUTING.md

@@ -1,6 +1,7 @@
-# Contribution Guidelines
+# Contribution Code
+| While True Do Contribution Guidelines
 
-This guideline is only a snapshot. Please have a look [here](https://github.com/while-true-do/community/docs/) to check the latest version.
+This guideline is only a snapshot. Please have a look [here](https://github.com/while-true-do/community/blob/master/docs/CONTRIBUTING.md) to check the latest version.
 
 ## Welcome
 
@@ -15,14 +16,14 @@ In this document you can find some guidance, how you can take care of bugs, subm
 -   [Submit Changes and Pull Requests](#Submit-Changes-and-Pull-Requests)
 -   [Documentation](#Documentation)
 -   [Testing](#Testing)
-  
+
 ## Resources
 
 -   Documents: <https://github.com/while-true-do/community/>
 -   Issue tracker: linked in every [README.md](../README.md)
 -   Website: <https://while-true-do.org>
 -   Github: <https://github.com/while-true-do/>
--   Communication: mail@while-true-do.org
+-   Communication: hello@while-true-do.org
 
 ## Report Bugs and Requests
 

docs/ISSUE_TEMPLATE.md

@@ -1,6 +1,8 @@
+<!--
 If this is your first report, please have a look at the contribution guidelines first.
 
-https://github.com/while-true-do/community/docs/CONTRIBUTING.md
+https://github.com/while-true-do/community/blob/master/docs/CONTRIBUTING.md
+-->
 
 ### Type of Report
 
@@ -20,4 +22,4 @@ https://github.com/while-true-do/community/docs/CONTRIBUTING.md
 
 ### Attachments
 
-<!-- Please attach everything, what can help to understand the issue like screenshots, code snippets, error codes, animations, etc. -->
+<!-- Please attach everything, that can help to understand the issue like screenshots, code snippets, error codes, animations, etc. -->

docs/PULL_REQUEST_TEMPLATE.md

@@ -1,24 +1,30 @@
 <!--
 Please have a look at the contribution guidelines and commit template first.
 
-https://github.com/while-true-do/community/docs/CONTRIBUTING.md
-https://github.com/while-true-do/community/docs/COMMIT_TEMPLATE.md
+https://github.com/while-true-do/community/blob/master/docs/CONTRIBUTING.md
+https://github.com/while-true-do/community/blob/master/docs/COMMIT_TEMPLATE.md
 -->
+
 # Subject of max. 50 characters
+
 <!--
 Further paragraphs come after blank lines, if needed.
 
  - Bullet points are okay, too
  - A hyphen or asterisk is used for the bullet, preceded by a single space.
 -->
+
 ## Reference
+
 <!--
 Please be aware, that every pull-request/merge-request for released (stable) repositories needs an issue.
 -->
+
  - Resolves: #12, #13
  - See also: #33, #44
 
 ## (Optional) People
+
 <!--
 @mentions of somebody who was involved or should be involved.
 @mentions of the person or team responsible for reviewing proposed changes.

meta/main.yml

@@ -1,11 +1,12 @@
-dependencies: ['while-true-do.yum']
+dependencies:
+  - while_true_do.yum
 
 galaxy_info:
+  role_name: yum_cron
   author: while-true-do.org
   description: A role to install and configure yum-cron.
   company: while-true-do.org
 
-  issue_tracker_url: https://github.com/while-true-do/ansible-role-yum-cron/issues
   github_branch: master
   license: BSD
 

requirements.yml

@@ -1,3 +1,3 @@
 ---
-# Install while-true-do.yum from galaxy
-- src: while-true-do.yum
+# Install while_true_do.yum from galaxy
+- src: while_true_do.yum

tests/.aspell.en.pws

@@ -11,3 +11,4 @@ reachability
 refactoring
 screenshots
 wtd
+yml