Merge pull request #1 from makerdao/master

DefiSaver Polling Vote

MIP0/General-MIP-Template.md

@@ -0,0 +1,38 @@
+# General MIP Template
+
+## Preamble
+```
+MIP#:
+Title:
+Author(s): 
+Contributors:
+Type: 
+Status: <Assigned by MIP Editor>
+Date Proposed: <yyyy-mm-dd>
+Date Ratified: <yyyy-mm-dd>
+Dependencies:
+Replaces:
+```
+## References
+
+- A list of supporting materials referenced by this MIP.
+
+## Sentence Summary
+
+- A description of what the Maker Improvement Proposal (MIP) is focused on. Suggest 30 words max.
+
+## Paragraph Summary
+
+- A description of what the Maker Improvement Proposal (MIP) is focused on. Suggest 100 words max.
+
+## Component Summary
+
+- A description of the purpose of each component in the MIP . Suggest 30 words max per component.
+
+## Motivation
+
+- A short description of the motivation behind the MIP. 
+
+## Specification / Proposal Details
+
+- Proposed process standard details - describes the new process or feature and the problem it is solving.

MIP0/MIP0c12-Subproposal-Template.md

@@ -0,0 +1,28 @@
+# MIP0c12: Subproposal Template for Core Personnel Onboarding
+
+## Preamble
+
+```
+MIP0c12-SP#: #
+Author(s):
+Contributors: 
+Status:
+Date Applied: <yyyy-mm-dd>
+Date Ratified: <yyyy-mm-dd>
+---
+Core Personnel Role: MIP Editor or Governance Facilitator
+Proposed applicant: Name of applicant
+```
+
+## Application
+
+### Motivation
+- Explanation of why and how you want to fulfil this role. 
+
+### Credentials
+- Past work experience.
+
+### Relevant Information
+- Github Account
+- MakerDAO Forum Account 
+- Other relevant Accounts

MIP0/MIP0c13-Subproposal-Template.md

@@ -0,0 +1,22 @@
+# MIP0c13: Subproposals Template for Core Personnel Offboarding
+
+## Preamble
+```
+MIP0c13-SP#: #
+Author(s):
+Contributors: 
+Status:
+Date Proposed: <yyyy-mm-dd>
+Date Removed: <yyyy-mm-dd>
+---
+Core Personnel Role: MIP Editor or Governance Facilitator
+Core Personnel to be removed:
+```
+
+## Removal Application and Supporting Evidence
+
+### Motivation
+- The explanation behind the removal of the person from the role listed above.
+
+### Relevant Information
+-  Links to evidence further backing the motivation behind the removal of the person from the role listed above.

MIP0/Technical-MIP-Template.md

@@ -0,0 +1,67 @@
+# Technical MIP Template
+
+## Preamble
+```
+MIP#: <# to be assigned>
+Title: <MIP title>
+Author(s): <list of authors' names and/or email addresses and GitHub handles>
+Contributors:
+Type: MIP Type
+Status: <Assigned by MIP Editor>
+Date Proposed: <yyyy-mm-dd>
+Date Ratified: <yyyy-mm-dd>
+Dependencies: <List of depdendent MIPs>
+Replaces: <List of MIP it is replacing>
+License: <added by MIP Author>
+```
+## References
+
+- A list of supporting materials referenced by this MIP.
+
+## Sentence Summary
+
+- A description of what the Maker Improvement Proposal (MIP) is focused on. Suggest 30 words max.
+
+## Paragraph Summary
+
+- A description of what the Maker Improvement Proposal (MIP) is focused on. Suggest 100 words max.
+
+## Component Summary
+
+- A description of the purpose of each component in the MIP . Suggest 30 words max per component.
+
+
+## Motivation
+
+- A short description of the motivation behind the proposed technical solution. 
+
+## Specification
+
+The details of the proposed technical solution. The specification should be detailed enough to allow an implementation team to begin development as well as testing. The specification for technical MIPs must  include the following components:
+
+
+### Proposed Code
+   -  The final code that can be used directly in the executive vote to accept or reject the MIP.
+
+
+### Test Cases
+   - For the implementation or testing of the proposed code
+
+### Security Considerations
+
+   - This is one of the most important aspects of the Technical MIP proposal. The purpose of this section is to proactively document any security-relevant design information, decisions, potential failure modes, implementation details, and important discussions related to the proposed change. This section helps to optimize the MIP process by providing proactive guidance on security considerations when proposing a change that will affect the Maker Protocol.
+   - Backwards compatibility
+
+### Auditor Information and Report
+
+   - This section includes the audit partner details and the final audit report for the proposed code.
+
+### Licensing
+   - Recommended licenses for developed code:
+        -   MIT: [Expat/MIT/X11 license](https://opensource.org/licenses/MIT)
+        -   BSD-2-Clause: [OSI-approved BSD 2-clause license](https://opensource.org/licenses/BSD-2-Clause)
+        -   BSD-3-Clause: [OSI-approved BSD 3-clause license](https://opensource.org/licenses/BSD-3-Clause)
+        -   CC0-1.0: [Creative Commons CC0 1.0 Universal](https://creativecommons.org/publicdomain/zero/1.0/)
+        -   GNU-All-Permissive: [GNU All-Permissive License](http://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html)
+        -   Apache-2.0: [Apache License, version 2.0](http://www.apache.org/licenses/LICENSE-2.0)
+