merikan

---
# ^^^ YAML documents must begin with the document separator "---"
#
#### Example docblock, I like to put a descriptive comment at the top of my 
#### playbooks.
#
# Overview: Playbook to bootstrap a new host for configuration management.
# Applies to: production
# Description: 
#   Ensures that a host is configured for management with Ansible.

merikan

<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
           http://maven.apache.org/maven-v4_0_0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.gordondickens.sample</groupId>
  <artifactId>sample-parent</artifactId>
  <version>1.0.0</version>

  <packaging>pom</packaging>

merikan

# This file is for unifying the coding style for different editors and IDEs usin EditorConfig
# http://EditorConfig.org

# All EditorConfig properties:
# https://github.com/editorconfig/editorconfig/wiki/EditorConfig-Properties

root = true

# global settings
[*]

merikan

Change Log

All notable changes to this project will be documented in this file.
This project adheres to Keep a CHANGELOG and Semantic Versioning

[Unreleased] - [unreleased]

Bug fixes

New features

merikan

How to Contribute

Pull requests are greatly appreciated and are what makes opensource great. Here's a quick guide:

• Fork it
• Create your feature branch (git checkout -b my-new-feature)
• Commit your changes (git commit -am 'Add some feature')
• Push to the branch (git push origin my-new-feature)
• Create new Pull Request

merikan

Project name

You are encouraged to add “badges” such as Travis CI’s image or Code Climate’s . See this blogpost for more information

Synopsis

At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)

Code Example

merikan

Typography

Headings

Headings from h1 through h6 are constructed with a # for each level:

# h1 Heading
## h2 Heading
### h3 Heading

merikan

Synopsis

At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)
You are encouraged to add “badges” such as Travis CI’s image or Code Climate’s . See this blogpost for more information

Code Example

Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.

Motivation

merikan

Keybase proof

I hereby claim:

• I am merikan on github.
• I am merikan (https://keybase.io/merikan) on keybase.
• I have a public key whose fingerprint is A93D 728B 0D00 28A7 1C47 EB10 6F86 D200 24CE 1D22

To claim this, I am signing this object:

merikan

This gist is for my project euler solutions