Merge branch 'feature/issue-templates-new-proposal' into 'master'

Feature/issue templates new proposal

See merge request !1

.github/ISSUE_TEMPLATE/config.yml

+blank_issues_enabled: false
+contact_links:
+  - name: Mattermost ChatOps
+    url: https://chat.il2.dso.mil/platform-one/channels/topic---p1toc
+    about: Join us here if you have a Platform One SSO
+  - name: P1TOC Meetups
+    url: https://github.com/DoD-Platform-One/P1TOC/blob/master/README.md#meeting-time
+    about: Join us during our meetups, we'll make time for general Q&A
\ No newline at end of file

.github/ISSUE_TEMPLATES/community_nomination.md

----
-name: community nomination
-about: community nomination
-title: "[Community Nominee] name"
-labels: nominee
-
----
-
-Thank you for your nomination! 
-
-# Nominee
-Name:  
-Organization:
-Employer:  
-Bio:
-
-
-## Nominator
-Name:  
-Organization:  
-Employer:  

.github/ISSUE_TEMPLATES/project_presentation.md

----
-name: project presentation request
-about: request for a spot to present your completed project
-title: "[PROJECT PRESENTATION] project"
-labels: presentation
-
----
-
-We look forward to your presentation!
-
-Please confirm and provide the following:
-
-- [ ] Project has reached the proposed MVP maturity
-- [ ] Project has previously been proposed and is a P1TOC active project
-- [ ] Your project has a `CONTRIBUTING.md` file with guidelines at the root of your project.
-
-What is the URL of your project?  
-

projects/proposals/README.md

@@ -8,11 +8,9 @@ Have an idea or improvement, you're in the right place. Before proceeding please
 
 ## New proposals
 
-Begin by completing the [proposal template](proposal_template.yaml), when ready submit a merge request. The request will be reviewed at the next P1TOC meetup (time permitting, reviewed in order of submission).
-
-Merge Request checklist:
-- [ ] File name matches the naming convention *projectName_proposal_submission.yaml*, replacing projectName with your project.
-- [ ] File has every component populated
+1. Submit a new [issue](https://github.com/DoD-Platform-One/P1TOC/issues/new?assignees=&labels=new-project&template=new-project-proposal.md&title=)
+2. Wait for the P1TOC to grant access and/or provide initial feedback. (This will be done offline through comments on the issue)
+3. Create a branch, complete the [proposal template](proposal_template.yaml), when ready submit a pull request. The request will be reviewed at the next P1TOC meetup (time permitting, reviewed in order of submission).
 
 ### Proposal reviews
 
@@ -28,4 +26,5 @@ P1TOC meetups are the recommended forum to get visibility and support on your pr
    2. A general project timeline is established
    3. Code repository is clearly identified and includes a `CONTRIBUTING.md` created the the proposer.
 4. Development iterates
-5. When ready the project requests a project presentation by submitting an [issue](https://github.com/DoD-Platform-One/P1TOC/issues)
\ No newline at end of file
+5. When ready the project requests a project presentation by submitting an [issue](https://github.com/DoD-Platform-One/P1TOC/issues/new?assignees=&labels=show-and-tell&template=project-presentation.md&title=Presentation%3A+%5BPROJECT%5D)
+   1. The P1TOC will coordinate in the issue and schedule a time for your presentation
\ No newline at end of file