Add expanded, branded README

Add TEMPLATE.md

Author: emilypi

LICENSE

@@ -0,0 +1,13 @@
+Copyright 2021 Haskell Foundation
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

README.md

@@ -1 +1,13 @@
+<p align="center">
+<img src="https://haskellfoundation.github.io/static/images/logos/hf-logo-alpha.png" width="350" height="282" alt="Haskell Foundation" title="Haskell Foundation">
+</p>
+
 # Haskell Foundation Tech Proposals
+
+[![Hackage](https://img.shields.io/static/v1?label=Haskell%20Foundation&message=official&color=purple&style=for-the-badge)](https://haskell.foundation)
+
+This repository is for the [Haskell Foundation](https://haskell.foundation) tech proposals. Haskell Foundation tech proposals are similar to [GHC proposals](https://github.com/ghc-proposals/ghc-proposals) in that they are the venue by which items are added to the HF technical agenda, pending final review from its Board of Directors. This repository is maintained by the Haskell Foundation and its volunteers. If you would like to get started with a merge request, please consult the documentation below.
+
+## License
+
+This site is open source, and covered under the Apache 2.0 license.

TEMPLATE.md

@@ -2,15 +2,15 @@
 
 
 
-This template is for Haskell Foundation technical agenda proposals. You may find existing proposals and more examples at the [tech-proposals](https://github.com/haskellfoundation/tech-proposals) repository. 
+This template is for Haskell Foundation technical agenda proposals. You may find existing proposals and more examples at the [tech-proposals](https://github.com/haskellfoundation/tech-proposals) repository.
 
 
 
 ## Introduction
 
 This section should detail the following: A summary of the proposal’s
 motivation, implementation, risks, timeline, and goals. It should aim to
-be an abstract for the proposals.
+be an abstract for the proposal.
 
 ## Background
 
@@ -19,7 +19,6 @@ needed to understand the proposal’s motivation (e.g. a high level
 overview of the technical details and some history).
 
 
-
 ## Motivation
 
 This section should explain the motivation in terms of why Haskell
@@ -37,10 +36,10 @@ for undertaking the project.
 
 This section should detail the following people:
 
--   **Performers:** the project leads and main developers/resources who will be directly involved in the day to day work.
-    
+-   **Performers:** the project leads and main developers/resources who will be directly involved in the day to day work. If your project needs performers to be sourced by the Haskell Foundation, please say so here.
+
 -   **Reviewers:** people who will be signing off on work done for the proposal at different stages.
-    
+
 -   **Stakeholders:** A sample of people who will be directly affected by the project, who can serve as coordinators and advisors.
 
 ## Resources
@@ -58,23 +57,23 @@ months and years.
 
 ## Lifecycle:
 
-This section should detail the SDLC of the project, including a
+This section should detail the development lifecycle of the project, including a
 high-level description of the following criteria:
 
 -   **Implementation:** A high-level overview of the implementation details of the project, including how the leaders expect to make progress on individual goals and key progress indicators. This
     section should not be as granular as individual merge requests that will be made, but that would be a bonus!
-    
+
 -   **Compatibility issues:** highlight any potential compatibility issues that may arise from the changes brought by this project, including any work that needs to be done on the part of
     stakeholders or performers.
-    
+
 -   **Performance impact:** An overview of the potential performance impact of this project on the ecosystem, if applicable.
 
 ## Deliverables
 
 This section should describe the individual deliverables this project
 will bring as a result of the changes described above. These
 deliverables should support the end goals of the project and define what
-HF is actually delivering to the community.
+this project is actually delivering to the community.
 
 ## Outcomes