Initial Commit

.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?  
+

CONTRIBUTING.md

+# Contributing
+
+## Contributing to the P1TOC
+
+Open a merge request or an [issue](https://github.com/DoD-Platform-One/P1TOC/issues) for discussion.
+
+## Contributing new projects
+
+Review project [proposal guidelines](/projects/proposals/README.md)
+
+## Contributing to existing projects
+
+Find the [active project](/projects/active) and find their home repository and `CONTRIBUTING.md`
\ No newline at end of file

CONTRIBUTORS.md

+# Current Contributors of the P1TOC content and solutions
+

EMERITUS.md

+# Past members of the P1TOC
\ No newline at end of file

README.md

+# Platform One Technical Oversight Committee (P1TOC)
+*NOTICE the P1TOC is in alpha and is not yet ready for widespread contributions. In the meantime you are welcome to submit an [issue](https://github.com/DoD-Platform-One/P1TOC/issues)*
+
+P1TOC is the technical governing body of Platform One and maintainers of community engagements and contributions. While it doesn't map one to one, we are inspired heavily by the [CNCF TOC](https://github.com/cncf/toc); anything you see there is consistent with the outcome we'd like to see here.
+
+\~The P1TOC scale contributions by the DoD technical and user community, while retaining integrity and increasing quality in support of our mission. ([source](https://github.com/cncf/toc/blob/master/sigs/README.md))
+
+As we begin and evolve:
+- We desire to enable community partnerships across organizations
+- We desire to Enable colalborative developer of solutions, solving problems for the majority
+- We are not here to gatekeep, instead to connect and collaborate
+- We are not a standards body
+- We are not an avenue to get funding, nor influence funding
+
+# Members
+
+Platform One [Appointed](/policy/governance.md#platform-one-appointed)
+- Maj. Rob Slaughter - Director of Platform One
+- Mr. Jeff McCoy - CTO of Platform One
+- Matt Huston - CISO of Platform One
+- Vacant Seat 1/4 - Platform One Engineer
+- Vacant Seat 2/4 - Platform One Engineer
+- Vacant Seat 3/4 - Platform One Engineer
+- Vacant Seat 4/4 - Platform One Engineer
+  
+Community [Appointed](/policy/governance.md#community-appointed)
+- Vacant Seat 1/6
+- Vacant Seat 2/6
+- Vacant Seat 3/6
+- Vacant Seat 4/6
+- Vacant Seat 5/6
+- Vacant Seat 6/6
+
+## Meeting Time
+
+The P1TOC meets and is open to all:
+- Every other week for new projects and general agenda
+- Project presentations (completed projects) will be scheduled as needed.
+
+# Contribute
+
+Getting involved 
+- the P1TOC is open to all, join us for meetups and project presentations
+- Look for the contributors guide in any of the [Active](/projects/active/) projects
+- start [here](projects/proposals/README.md) for new ideas

WORKINGAGREEMENT.md

+# Working Agreement
+
+If it were easy, it'd already be done.
+
+What is expected of everyone:
+- To carry themselves in a respectful and professional manner
+- To contribute high quality solutions
+- To always question a solution, in the interest of improvement
+
+What is expected of you (a contributor):
+- Respect the time of contributors and members of the P1TOC
+- Present and develop quality solutions that provide unique, added benefit
+- Develop solutions that are reusable and solve common problems
+- don't expect 24/7 support from the P1TOC nor the community
+
+What is expected of the P1TOC:
+- Available during pre-defined meeting times
+- Work towards finding a solution
+- bringing professional and technical excellence to projects (in an advisory manner)
\ No newline at end of file

meetings/GENERAL_AND_PROPOSALS.md

+# Historical Minutes for General Agenda and Project Proposals
\ No newline at end of file

meetings/PROJECT_PRESENTATIONS.md

+# List of Project Presentations
+

meetings/README.md

+# Minutes and Agenda
+
+Each meeting, it's agenda and recording is owned by the current chair.
+
+*Everything reviewed will be based on time order (i.e. earliest submission to latest submission)*
+
+## General Agenda and Project Proposals
+*(see [General Minutes](GENERAL_AND_PROPOSALS.md))*
+
+- Adjudicate project proposals (10m)
+- Review new project proposals (30m)
+- Open Discussion (10m)
+
+## Project Presentations
+*(see [Presentations](PROJECT_PRESENTATIONS.md))*
+
+To request a presentation for a completed (or nearly completed) project. Open an [issue](https://github.com/DoD-Platform-One/P1TOC/issues).
+
+## Quarterly Review
+
+Once a quarter the P1TOC will pause new activity to review and discuss activities for the last quarter.
+
+## Annual Review
+
+Once a year the P1TOC will review projects and activity to ensure active engagement. Inactive projects will be marked for deprecation and fully deprecated at the next quarterly review.
\ No newline at end of file

policy/governance.md

+# Members
+
+The P1TOC will have up to 13 members at any given time. 
+- 3 Platform One default members
+- 4 Platform One appointed members
+- 6 community appointed members
+
+On a rotational basis of 6 months, one member will be nominated and designated chair. The chair is responsible for keeping the ship afloat, hosting meetings, keeping minutes, timeboxing agenda, etc...
+
+## Platform One Appointed
+
+Three positions, called chiefs, will be held by the current staff member in the position, are only restricted by their term in the position, and hold overriding authority on all issue with a majority vote (2/3).
+- The Director of Platform One
+- The Chief Technologist of Platform One
+- The Chief Security Officer of Platform One 
+
+Four additional positions will be held by engineers from within Platform One and are determined by a majority vote of the chiefs. These positions can retain their position while on Platform One "payroll" and serve up to one year terms. These members should be diverse, representing different companies/primes and components of Platform One.
+
+## Community Appointed
+
+Up to six positions can be held by community appointed members. 
+- Any member of the community may nominate a prospective member by submitting a ticket [here](https://github.com/DoD-Platform-One/P1TOC/issues) 
+- Nominee's will be announced if a seat is vacant and 
+- voted upon in the following meetup of the P1TOC. 
+  - Voting is done by the community live during the meetup
+- community apointed members will hold their seat for up to one year and then must be re-nominated and voted upon.
+- No two community members can be employed by the same entity, nor work the same program.
+
+
+## Requirements
+
+All members must adhere and agree to the following requirements:
+- Actively engage with the best interests of the entire community, regardless of employment
+- The member is high quality and highly driven to propel the DoD into the future
+- The member has sound engineering experience
+- With the exception of the chiefs, no member can serve more than two years on the P1TOC
+
+## Unique Scenarios
+
+Unknown scenarios will always pop up, acquisitions, contracts, employment changes, etc... 
+- Membership should first and foremost provide dynamic representation across the community, without vendor bias.
+- Second, the P1TOC should alwasy avoid interruption, even if this means breaking the 'rules' for a short period of time.
+
+Resolution of such unique scenarios should be addressed above all other agenda
+- The chair will be responsible for bringing this up at the next gathering
+- The P1TOC must agree upon a path forward
+- The path forward, must resolve the unique scenarios within 90 days
\ No newline at end of file

projects/proposals/README.md

+# Proposals
+
+Have an idea or improvement, you're in the right place. Before proceeding please:
+- Review the P1TOC [Working Agreement](/WORKINGAGREEMENT.md)
+- Review Active [projects](/projects/active/) and ensure you're idea isn't related.
+- Review Completed [projects](/projects/completed/) and ensure you're idea isn't related. 
+- Rejected [proposals](/projects/rejected/) and ensure you're idea isn't related or addresses the "rejected reasoning".
+
+## 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
+
+### Proposal reviews
+
+P1TOC meetups are the recommended forum to get visibility and support on your project. Proposals will undergo the following steps:
+
+1. At the first P1TOC meetup, review new submissions.
+   1. Proposer takes actions and solicits community advocacy
+2. At the second P1TOC meetup, final review of submissions.
+   1. The P1TOC moves the proposal to active or rejected
+   2. A project kickoff meeting is established with a P1TOC member and the proposers.
+3. At the kickoff meeting
+   1. A meetup cadence is established, no less than once per week, timeboxed to less than 60m
+   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

projects/proposals/proposal_template.yaml

+project:
+    name:
+    description:
+    problemStatement:
+    mvpMilestone:
+        description:
+        estimatedTime:
+    initialMembers:
+        - name:
+        - name:
+
+similarProjects:
+    - name:
+      comparison:
\ No newline at end of file