Add project update process

Signed-off-by: Tracy Kuhrt <tracy.a.kuhrt@accenture.com>

tac/governing-documents/project-updates.md

@@ -0,0 +1,31 @@
+---
+layout: default
+title: Project Updates
+parent: Governing Documents
+grand_parent: LF Decentralized Trust TAC
+nav_order: 7
+---
+[//]: # (SPDX-License-Identifier: CC-BY-4.0)
+
+# Project Updates
+
+## Overview
+Project updates are:
+- used by the TAC to determine the health of a project
+- provided to the Governing Board on a monthly basis in the TAC Update
+- used to highlight interesting updates to the Governing Board about the projects
+- used by the TAC chair and staff to provide project updates at events
+- used to share interesting information with member companies by both the staff and TAC members
+- suggested as a point of reference to newcomers to determine if a project would be worth joining based on information like the contributor diversity, as well as, the type of feature work that is ongoing within the project
+
+## Submitting Project Updates
+Project updates are to be submitted as a pull request to the [LF-Decentralized-Trust/governance](https://github.com/LF-Decentralized-Trust/governance) repository. For instructions on how to file see: [Filing a Project Update](https://lf-decentralized-trust.github.io/governance/project-updates/#instructions-for-filing)
+
+## Merging
+Project updates will be merged after 14 days from submission unless (1) there is still ongoing discussion regarding the report or (2) a majority of the TAC has not approved the PR. If all TAC members have approved the PR before 14 days, then the PR will be merged.
+
+## History
+The following section captures the history of project reporting (aka project updates).
+* 2017-10-08 - New Governing Process: [Project Reporting Proposal](https://github.com/hyperledger/toc-docs/blob/main/documents/Project%20Reporting%20Proposal.pdf) - [approved by email vote on 2017-10-11](https://lists.hyperledger.org/g/toc/topic/17552164#1183)
+* 2023-01-10 - [Proposal to move project reporting to GitHub](https://github.com/hyperledger/toc/issues/43) - [approved by voice vote 26 JAN 2023](https://wiki.hyperledger.org/display/TSC/2023+01+26+TOC+Meeting+Record)
+* 2023-02-16 - [Discussion on when to merge project updates](https://toc.hyperledger.org/meeting-minutes/2023/2023-02-16-TOC-meeting-record.html#discussion)

tac/project-updates/index.md

@@ -0,0 +1,27 @@
+---
+layout: default
+title: Project Updates
+parent: LF Decentralized Trust TAC
+has_children: true
+child_nav_order: reversed
+has_toc: true
+nav_order: 6
+---
+[//]: # (SPDX-License-Identifier: CC-BY-4.0)
+
+# Project Updates
+Project updates are:
+- used by the TAC to determine the health of a project, including whether project should be moved to Dormant state
+- provided to the Governing Board on a monthly basis in the TAC Update
+- used to highlight interesting updates to the Governing Board about the projects
+- used by the TAC chair and staff to provide project updates at events
+- used to share interesting information with member companies by both the staff and TAC members
+- suggested as a point of reference for newcomers to determine if a project would be worth joining based on information like the contributor diversity, as well as, the type of feature work that is ongoing within the project
+
+# Instructions for Filing
+1. Copy the `0000-quarterly-update-template.md` file to the subdirectory for the current year and name the file `YYYY-Qn-Project-Name` (e.g., `2024-Q1-Besu.md`).
+1. Update the information at the top of the file:
+    - change the `parent` line to `YYYY` (e.g., `parent: 2024`)
+    - change the `grand_parent` to `Project Updates` (i.e., `grand_parent: Project Updates`)
+    - remove the `nav_exclude` line
+1. Text between `<mark></mark>` are instructions. Please remove when section has been completed.