From aa49955e7bb849bf20e23ef235719208152cc151 Mon Sep 17 00:00:00 2001
From: Doug Chivers <doug.chivers@hp.com>
Date: Fri, 25 Sep 2015 14:35:50 +0100
Subject: [PATCH] Adding Killick structure

Change-Id: I9a4098daea837cb17b481a4ed672e0830f2d6118
---
 specs/mikata/killick/template.rst | 110 ++++++++++++++++++++++++++++++
 1 file changed, 110 insertions(+)
 create mode 100644 specs/mikata/killick/template.rst

diff --git a/specs/mikata/killick/template.rst b/specs/mikata/killick/template.rst
new file mode 100644
index 0000000..e62f617
--- /dev/null
+++ b/specs/mikata/killick/template.rst
@@ -0,0 +1,110 @@
+..
+
+This work is licensed under a Creative Commons Attribution 3.0 Unported
+License.
+http://creativecommons.org/licenses/by/3.0/legalcode
+
+..
+  This template should be in ReSTructured text. The filename in the git
+  repository should match the launchpad URL, for example a URL of
+  https://blueprints.launchpad.net/openstack-manuals/+spec/awesome-thing should
+  be named awesome-thing.rst .  Please do not delete any of the sections in
+  this template.  If you have nothing to say for a whole section, just write:
+  None For help with syntax, see http://sphinx-doc.org/rest.html
+  To test out your formatting, see http://www.tele3.cz/jbar/rest/rest.html
+
+=============================
+ The title of your blueprint
+=============================
+
+Include the URL of your launchpad blueprint:
+
+https://blueprints.launchpad.net/openstack-manuals/+spec/example
+
+Or
+
+https://blueprints.launchpad.net/bandit/+spec/example
+
+Introduction paragraph -- why are we doing anything?
+
+Problem description
+===================
+
+A detailed description of the problem.
+
+Proposed change
+===============
+
+Here is where you cover the change you propose to make in detail. How do you
+propose to solve this problem?
+
+If this is one part of a larger effort make it clear where this piece ends. In
+other words, what's the scope of this effort?
+
+Include which OpenStack security project this will apply to (OpenStack Security
+Guide, OpenStack Security Notes, Bandit, etc). Also include where in the
+OpenStack security project tree hierarchy this will reside.
+
+Alternatives
+------------
+
+This is an optional section, where it does apply we'd just like a demonstration
+that some thought has been put into why the proposed approach is the best one.
+
+Implementation
+==============
+
+Assignee(s)
+-----------
+
+Who is leading the writing of the code? Or is this a blueprint where you're
+throwing it out there to see who picks it up?
+
+If more than one person is working on the implementation, please designate the
+primary author and contact.
+
+Primary assignee:
+  <launchpad-id or None>
+
+Can optionally can list additional ids if they intend on doing
+substantial implementation work on this blueprint.
+
+Milestones
+----------
+
+Target Milestone for completion:
+  Liberty-1
+
+Work Items
+----------
+
+Work items or tasks -- break the feature up into the things that need to be
+done to implement it. Those parts might end up being done by different people,
+but we're mostly trying to understand the timeline for implementation.
+
+
+Dependencies
+============
+
+- Include specific references to specs and/or blueprints in openstack-manuals,
+  or in other projects, that this one either depends on or is related to.
+
+- Does this feature require any new library dependencies or code otherwise not
+  included in OpenStack? Or does it depend on a specific version of library?
+
+References
+==========
+
+Please add any useful references here. You are not required to have any
+reference. Moreover, this specification should still make sense when your
+references are unavailable. Examples of what you could include are:
+
+* Links to mailing list or IRC discussions
+
+* Links to notes from a summit session
+
+* Links to relevant research, if appropriate
+
+* Related specifications as appropriate
+
+* Anything else you feel it is worthwhile to refer to