Merge pull request #2 from oudod/template

Add RFC template

Author: oudod

0000-template.md

@@ -0,0 +1,58 @@
+- Feature Name: (fill me in with a unique ident, my_awesome_feature)
+- Start Date: (fill me in with today's date, YYYY-MM-DD)
+- RFC PR: (leave this empty)
+- Exonum Issue: (leave this empty)
+
+# Summary
+[summary]: #summary
+
+One para explanation of the feature.
+
+# Motivation
+[motivation]: #motivation
+
+Why are we doing this? What use cases does it support? What is the expected outcome?
+
+# Detailed design
+[design]: #detailed-design
+
+This is the bulk of the RFC. Explain the design in enough detail for somebody
+familiar with the Exonum architecture to understand, and for somebody familiar
+with the programming language to implement. This should get into specifics and
+corner-cases, and include examples of how the feature is used.
+
+# How We Teach This
+[how-we-teach-this]: #how-we-teach-this
+
+What names and terminology work best for these concepts and why?
+How is this idea best presented — as a continuation of existing Exonum concepts,
+or as a wholly new one?
+
+Would the acceptance of this proposal change how Exonum is presented to new users
+at any level?
+How should this feature be introduced and taught to existing Exonum users?
+
+What additions or changes to the [Exonum documentation] does it entail?
+
+What would the outline of a new section in the documentation look like? What
+should the reader be able to understand by the end of the section in the
+documentation?
+
+What's an example that would show off this feature?
+
+# Drawbacks
+[drawbacks]: #drawbacks
+
+Why should we *not* do this?
+
+# Alternatives
+[alternatives]: #alternatives
+
+What other designs have been considered? What is the impact of not doing this?
+
+# Unresolved questions
+[unresolved]: #unresolved-questions
+
+What parts of the design are still TBD?
+
+[Exonum documentation]: https://github.com/exonum/exonum-doc