Add SwiftPM proposal template

This adds a new proposal template for SwiftPM proposals. The existing
Swift proposal template is renamed to 0000-swift-template.md and both
templates are moved into a directory called `proposal-templates/`.

Author: aciidgh

process.md

@@ -52,7 +52,7 @@ Swift, please consider how your proposal fits in with the larger goals
 of the upcoming Swift release. Proposals that are clearly out of scope
 for the upcoming Swift release will not be brought up for review. If you can't resist discussing a proposal that you know is out of scope, please include the tag `[Out of scope]` in the subject.
 * **Socialize the idea**: propose a rough sketch of the idea in the ["pitches" section of the Swift forums](https://forums.swift.org/c/evolution/pitches), the problems it solves, what the solution looks like, etc., to gauge interest from the community.
-* **Develop the proposal**: expand the rough sketch into a complete proposal, using the [proposal template](0000-template.md), and continue to refine the proposal on the forums. Prototyping an implementation and its uses along with the proposal is *required* because it helps ensure both technical feasibility of the proposal as well as validating that the proposal solves the problems it is meant to solve.
+* **Develop the proposal**: expand the rough sketch into a complete proposal, using the [proposal template](proposal-templates/0000-swift-template.md), and continue to refine the proposal on the forums. Prototyping an implementation and its uses along with the proposal is *required* because it helps ensure both technical feasibility of the proposal as well as validating that the proposal solves the problems it is meant to solve.
 * **Request a review**: initiate a pull request to the [swift-evolution repository][swift-evolution-repo] to indicate to the core team that you would like the proposal to be reviewed. When the proposal is sufficiently detailed and clear, and addresses feedback from earlier discussions of the idea, the pull request will be accepted. The proposal will be assigned a proposal number as well as a core team member to manage the review.
 * **Address feedback**: in general, and especially [during the review period][proposal-status], be responsive to questions and feedback about the proposal.
 

0000-template.md renamed to proposal-templates/0000-swift-template.md

@@ -0,0 +1,62 @@
+# Package Manager Feature name
+
+* Proposal: [SE-NNNN](NNNN-filename.md)
+* Authors: [Author 1](https://github.com/swiftdev), [Author 2](https://github.com/swiftdev)
+* Review Manager: TBD
+* Status: **Awaiting implementation**
+
+*During the review process, add the following fields as needed:*
+
+* Implementation: [apple/swift-package-manager#NNNNN](https://github.com/apple/swift-package-manager/pull/NNNNN)
+* Decision Notes: [Rationale](https://forums.swift.org/), [Additional Commentary](https://forums.swift.org/)
+* Bugs: [SR-NNNN](https://bugs.swift.org/browse/SR-NNNN), [SR-MMMM](https://bugs.swift.org/browse/SR-MMMM)
+* Previous Revision: [1](https://github.com/apple/swift-evolution/blob/...commit-ID.../proposals/NNNN-filename.md)
+* Previous Proposal: [SE-XXXX](XXXX-filename.md)
+
+## Introduction
+
+A short description of what the feature is. Try to keep it to a single-paragraph
+"elevator pitch" so the reader understands what problem this proposal is
+addressing.
+
+Swift-evolution thread: [Discussion thread topic for that
+proposal](https://forums.swift.org/)
+
+## Motivation
+
+Describe the problems that this proposal seeks to address. If the problem is
+that some functionality is currently hard to use, show how it is currently used
+and describe its drawbacks. If it's completely new functionality that cannot be
+emulated, motivate why this new functionality would help Swift developers create
+better Swift packages.
+
+## Proposed solution
+
+Describe your solution to the problem. Provide examples and describe how they
+work. Show how your solution is better than current workarounds: is it cleaner,
+easier, or more efficient?
+
+## Detailed design
+
+Describe the design of the solution in detail. If it involves adding or
+modifying functionality in the package manager, explain how the package manager
+behaves in different scenarios and with existing features. If it's a new API in
+the `Package.swift` manifest, show the full API and its documentation comments
+detailing what it does.  The detail in this section should be sufficient for
+someone who is *not* one of the author of the proposal to be able to reasonably
+implement the feature.
+
+## Security
+
+Does this change have any impact on security, safety, or privacy?
+
+## Impact on exisiting packages
+
+Explain if and how this proposal will affect the behavior of existing packages.
+If there will be impact, is it possible to gate the changes on the tools version
+of the package manifest?
+
+## Alternatives considered
+
+Describe alternative approaches to addressing the same problem, and
+why you chose this approach instead.