diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8aa44378c822bebc5947f06c219e2b33e021f21e..6c724dc5d63f99ea2170e14e9af16f24ca80cb56 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,7 +2,7 @@ ## Contributing to the P1TOC -Open a merge request or an [issue](https://github.com/DoD-Platform-One/P1TOC/issues) for discussion. +Open a merge request or an [issue](https://repo1.dso.mil/platform-one/p1toc/-/issues/new) for discussion. ## Contributing new projects @@ -10,4 +10,4 @@ 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 +Find the [active project](/projects/active) and find their home repository and `CONTRIBUTING.md` diff --git a/meetings/GENERAL_AND_PROPOSALS.md b/meetings/GENERAL_AND_PROPOSALS.md index 8feb67a6cade1dcf8a5646df47762a4ca0e1874f..34eca7e72722c994d7597ffb40e529382eb531f6 100644 --- a/meetings/GENERAL_AND_PROPOSALS.md +++ b/meetings/GENERAL_AND_PROPOSALS.md @@ -1 +1 @@ -# Historical Minutes for General Agenda and Project Proposals \ No newline at end of file +# Historical Minutes for General Agenda and Project Proposals diff --git a/meetings/README.md b/meetings/README.md index 822d78b32d4956a471bcd4407fbbc2689d481ab3..c3e4dee126218a0eff5e28f9fc0a6b7b824c584c 100644 --- a/meetings/README.md +++ b/meetings/README.md @@ -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. diff --git a/policy/governance.md b/policy/governance.md index 395722ef8902861868b90c30fa79b2cd068b9f55..e42f829f3ebd87ea3a2abaaf24fde6185cd2dc6d 100644 --- a/policy/governance.md +++ b/policy/governance.md @@ -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 diff --git a/projects/proposals/README.md b/projects/proposals/README.md index 8f22ce31617e9a048aeaaf04cceb608bebb34009..3e365e84bc22b69fa3d1584d6f0ed97a5fd63825 100644 --- a/projects/proposals/README.md +++ b/projects/proposals/README.md @@ -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 new project proposal 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