From 8d0e307b3f0ed9be211596dc46f369250e6c9a7d Mon Sep 17 00:00:00 2001 From: Conor Svensson Date: Tue, 10 Sep 2024 12:37:47 +0100 Subject: [PATCH 1/3] Migrade task-force-guide.md to Governance for LFDT Signed-off-by: Conor Svensson --- .../task-force-guide.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) rename {guidelines => governing-documents}/task-force-guide.md (65%) diff --git a/guidelines/task-force-guide.md b/governing-documents/task-force-guide.md similarity index 65% rename from guidelines/task-force-guide.md rename to governing-documents/task-force-guide.md index 591c9735..bb731d1a 100644 --- a/guidelines/task-force-guide.md +++ b/governing-documents/task-force-guide.md @@ -1,13 +1,13 @@ --- layout: default title: Task Force -parent: Guidelines +parent: Governing Documents grand_parent: Hyperledger TOC -nav_order: 6 +nav_order: 11 --- # Task Force -A _task force_ is a group that is focused on a task with limited scope and fixed time to complete. A task force can be created by anyone in the Hyperledger community and must be proposed to and approved by the TOC. +A _task force_ is a group that is focused on a task with limited scope and fixed time to complete. A task force can be created by anyone in the LF Decentralized Trust (hereafter "LFDT") community and must be proposed to and approved by the TOC. ## Propose a Task Force To propose a task force, create an issue in [the TOC GitHub repository](https://github.com/hyperledger/toc/issues). The issue should be named "Task Force Proposal: _\_". The issue should include the following information: @@ -21,10 +21,10 @@ To propose a task force, create an issue in [the TOC GitHub repository](https:// ## Approval Process The TOC will review the task force proposal first by providing comments in the issue and secondly by bringing the task force proposal to a discussion and vote in a TOC meeting. -The decision of the vote will be documented in the issue. If the task force is approved, a page in the [Task Force section of the Hyperledger wiki](https://wiki.hyperledger.org/display/TF/Task+Forces+Home) will be created. +The decision of the vote will be documented in the issue. If the task force is approved, a page in the [Task Force section of the LFDT wiki](https://wiki.hyperledger.org/display/TF/Task+Forces+Home) will be created. ## Reporting on Task Force Completion of Deliverables Upon completion of the task force's deliverables, the task force should arrange a time with the TOC chair to present the deliverables at a TOC meeting. This can be accomplished by sending an email to [the TOC mailing list](https://lists.hyperledger.org/g/toc) at [toc@lists.hyperledger.org](mailto:toc@lists.hyperledger.org). ## Requesting an Extension on Completion Date -If the task force is not able to complete the deliverables by the specified completion date, then the leader of the task force should arrange a time with the TOC chair to discuss the extension at a TOC meeting. This discussion should include information on the current status, the delays, and the expected updates to the schedule. This can be accomplished by sending an email to [the TOC mailing list](https://lists.hyperledger.org/g/toc) at [toc@lists.hyperledger.org](mailto:toc@lists.hyperledger.org). +If the task force is unable to complete the deliverables by the specified completion date, then the leader of the task force should arrange a time with the TOC chair to discuss the extension at a TOC meeting. This discussion should include information on the current status, the delays, and the expected updates to the schedule. This can be accomplished by sending an email to [the TOC mailing list](https://lists.hyperledger.org/g/toc) at [toc@lists.hyperledger.org](mailto:toc@lists.hyperledger.org). From dcf939eb4093ed461105c5e1759e8ac5679a2d5b Mon Sep 17 00:00:00 2001 From: Conor Svensson Date: Thu, 12 Sep 2024 18:16:55 +0100 Subject: [PATCH 2/3] Update governing-documents/task-force-guide.md Co-authored-by: Tracy Kuhrt Signed-off-by: Conor Svensson --- governing-documents/task-force-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/governing-documents/task-force-guide.md b/governing-documents/task-force-guide.md index bb731d1a..48ad2c0b 100644 --- a/governing-documents/task-force-guide.md +++ b/governing-documents/task-force-guide.md @@ -21,7 +21,7 @@ To propose a task force, create an issue in [the TOC GitHub repository](https:// ## Approval Process The TOC will review the task force proposal first by providing comments in the issue and secondly by bringing the task force proposal to a discussion and vote in a TOC meeting. -The decision of the vote will be documented in the issue. If the task force is approved, a page in the [Task Force section of the LFDT wiki](https://wiki.hyperledger.org/display/TF/Task+Forces+Home) will be created. +The decision of the vote will be documented in the issue. If the task force is approved, a page in the [Task Force section of the wiki](https://wiki.hyperledger.org/display/TF/Task+Forces+Home) will be created. ## Reporting on Task Force Completion of Deliverables Upon completion of the task force's deliverables, the task force should arrange a time with the TOC chair to present the deliverables at a TOC meeting. This can be accomplished by sending an email to [the TOC mailing list](https://lists.hyperledger.org/g/toc) at [toc@lists.hyperledger.org](mailto:toc@lists.hyperledger.org). From 74845b6f1ff2f49c40b7c5663e1f036a49ea64a8 Mon Sep 17 00:00:00 2001 From: Conor Svensson Date: Thu, 12 Sep 2024 18:17:18 +0100 Subject: [PATCH 3/3] Apply suggestions from code review Co-authored-by: Tracy Kuhrt Signed-off-by: Conor Svensson --- governing-documents/task-force-guide.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/governing-documents/task-force-guide.md b/governing-documents/task-force-guide.md index 48ad2c0b..e8d12b58 100644 --- a/governing-documents/task-force-guide.md +++ b/governing-documents/task-force-guide.md @@ -19,12 +19,12 @@ To propose a task force, create an issue in [the TOC GitHub repository](https:// * Initial participant list ## Approval Process -The TOC will review the task force proposal first by providing comments in the issue and secondly by bringing the task force proposal to a discussion and vote in a TOC meeting. +The TAC will review the task force proposal first by providing comments in the issue and secondly by bringing the task force proposal to a discussion and vote in a TAC meeting. The decision of the vote will be documented in the issue. If the task force is approved, a page in the [Task Force section of the wiki](https://wiki.hyperledger.org/display/TF/Task+Forces+Home) will be created. ## Reporting on Task Force Completion of Deliverables -Upon completion of the task force's deliverables, the task force should arrange a time with the TOC chair to present the deliverables at a TOC meeting. This can be accomplished by sending an email to [the TOC mailing list](https://lists.hyperledger.org/g/toc) at [toc@lists.hyperledger.org](mailto:toc@lists.hyperledger.org). +Upon completion of the task force's deliverables, the task force should arrange a time with the TAC chair to present the deliverables at a TAC meeting. This can be accomplished by sending an email to [the TAC mailing list](https://lists.lfdecentralizedtrust.org/g/toc) at [tac@lists.lfdecentralizedtrust.org](mailto:tac@lists.lfdecentralizedtrust.org). ## Requesting an Extension on Completion Date -If the task force is unable to complete the deliverables by the specified completion date, then the leader of the task force should arrange a time with the TOC chair to discuss the extension at a TOC meeting. This discussion should include information on the current status, the delays, and the expected updates to the schedule. This can be accomplished by sending an email to [the TOC mailing list](https://lists.hyperledger.org/g/toc) at [toc@lists.hyperledger.org](mailto:toc@lists.hyperledger.org). +If the task force is unable to complete the deliverables by the specified completion date, then the leader of the task force should arrange a time with the TOC chair to discuss the extension at a TOC meeting. This discussion should include information on the current status, the delays, and the expected updates to the schedule. This can be accomplished by sending an email to [the TOC mailing list](https://lists.lfdecentralizedtrust.org/g/tac) at [tac@lists.lfdecentralizedtrust.org](mailto:tac@lists.lfdecentralizedtrust.org).