@@ -14,7 +14,7 @@ Each meeting, it's agenda and recording is owned by the current chair.
## 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).
To request a presentation for a completed (or nearly completed) project. Open an [issue](https://repo1.dso.mil/platform-one/p1toc/-/issues/new), using the project presentation template.
## Quarterly Review
...
...
@@ -22,4 +22,4 @@ Once a quarter the P1TOC will pause new activity to review and discuss activitie
## 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
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.
@@ -19,7 +19,7 @@ Four additional positions will be held by engineers from within Platform One and
## 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)
- Any member of the community may nominate a prospective member by submitting a ticket [here](https://repo1.dso.mil/platform-one/p1toc/-/issues/new), using the nomination template.
- 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
...
...
@@ -44,4 +44,4 @@ Unknown scenarios will always pop up, acquisitions, contracts, employment change
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
- The path forward, must resolve the unique scenarios within 90 days
@@ -8,7 +8,7 @@ Have an idea or improvement, you're in the right place. Before proceeding please
## New proposals
1. Submit a new [issue](https://github.com/DoD-Platform-One/P1TOC/issues/new?assignees=&labels=new-project&template=new-project-proposal.md&title=)
1. Submit a new [issue](https://repo1.dso.mil/platform-one/p1toc/-/issues/new), using the newprojectproposal template.
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).
...
...
@@ -26,5 +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/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
5. When ready the project requests a project presentation by submitting an [issue](https://repo1.dso.mil/platform-one/p1toc/-/issues/new), using the project presentation template.
1. The P1TOC will coordinate in the issue and schedule a time for your presentation
