Project update template and schedule

Signed-off-by: Tracy Kuhrt <[email protected]>

tac/project-updates/0000-annual-review-template.md

@@ -1,6 +1,6 @@
 ---
 layout: default
-title: Project Name
+title: YYYY Annual Review Project Name
 parent: Project Updates
 grand_parent: LF Decentralized Trust TAC
 nav_exclude: true

tac/project-updates/0000-quarterly-update-template.md

@@ -0,0 +1,50 @@
+---
+layout: default
+title: YYYY Qn Project Name
+parent: Project Updates
+grand_parent: LF Decentralized Trust TAC
+nav_exclude: true
+---
+
+<mark>_Copy this template to the subdirectory for the current year and name the file `YYYY-Qn-Project-Name.md` (e.g., `2023-Q1-Hyperledger-Iroha.md`). Update the information above to change the `title` to the `YYYY Qn Project Name` (e.g., `2023 Q1 Hyperledger Iroha`), the `parent` to `YYYY` (e.g., 2023), the `grand_parent` to `Project Updates`, and remove the `nav_exclude` line. Text between `<mark></mark>` are instructions. Please remove when section has been completed._
+</mark>
+
+# Project Health
+
+<mark>_Required: Sum up the status and health of your project and the community in a few sentences. Consider this the TL;DR for the rest of the report. How is your community doing health-wise? Are questions being answered? Are contributors acting appropriately? Are there new contributors showing up?_
+</mark>
+
+# Questions/Issues for the TAC
+
+<mark>_Required: If there are any specific issues that the TAC should be aware of or specifically address, then please call them out. If not, then it is helpful to state something like: "There are no issues at this time." When in doubt, it is better to include information or questions, rather than waiting._
+</mark>
+
+# Releases
+
+<mark>_Required: Regular software product releases are a sign of a healthy project. Reports should list the releases made since your last report, along with the release date of each. NOTE: If no releases were made, list the date of the most recent prior release._
+</mark>
+
+# Overall Activity in the Past Quarter
+
+<mark>_Required: Discuss briefly how active the project mailing lists and chat channels are. Are emails or user questions regularly read and responded to? What technical changes is the project working on? Is there new development happening, or just bug fixes? NOTE: If the activity is minimal, verify whether or not there are at least three active maintainers who can step in when needed, and include this information in the report._
+</mark>
+
+# Current Plans
+
+<mark>_Required: A healthy project will often be working towards a common goal, or have a shared understanding of what is being done next - even if individual contributors have their own "itches". What are the main features planned? What releases are planned? Are there any specific efforts or branches of development underway? This does not need to be described in technical detail. Conversely, if the activity is minimal, discuss how the project plans to address that - whether through seeking out new contributors, maintaining in a dormant but available state, or planning towards a move to a Deprecated (and ultimately End of Life) state._
+</mark>
+
+# Maintainer Diversity
+
+<mark>_Required: Please include the maintainers that were added since your last report. This information will allow us to track the diversity and growth of the maintainers of the project. NOTE: If no maintainers were added since your last report, provide the list of existing maintainers._
+</mark>
+
+# Contributor Diversity
+
+<mark>_Required: A healthy project should survive the departure of any single contributor or employer of contributors. Healthy projects also serve the needs of many parties. Include information on the number of unique organizations currently contributing to the project. NOTE: The contributions do not need to be source code._
+</mark>
+
+# Additional Information
+
+<mark>_Optional: Please provide any additional information that you feel would be useful for TAC to be aware._
+</mark>

tac/project-updates/2024/2024-schedule.md

@@ -0,0 +1,27 @@
+---
+layout: default
+title: 2024 Schedule
+parent: 2024
+grand_parent: Project Updates
+has_children: false
+has_toc: false
+---
+
+# 2024 Schedule
+
+| Quarter     | Date       | Project   |
+| ----------- | ---------- | --------- |
+| Q4          | 2024-10-10 | Cacti     |
+| Q4          | 2024-10-10 | Fabric    |
+| Q4          | 2024-10-10 | Identus   |
+| Q4          | 2024-10-10 | Web3j     |
+| Q4          | 2024-11-07 | Aries     |
+| Q4          | 2024-11-07 | Indy      |
+| Q4          | 2024-11-07 | AnonCreds |
+| Q4          | 2024-11-07 | Iroha     |
+| Q4          | 2024-11-14 | Bevel     |
+| Q4          | 2024-11-21 | Solang    |
+| Q4          | 2024-11-28 | Cello     |
+| Q4          | 2024-12-05 | Firefly   |
+| Q4          | 2024-12-05 | Besu      |
+| Q4          | 2024-12-05 | Caliper   |

tac/project-updates/2024/index.md

@@ -0,0 +1,12 @@
+---
+layout: default
+title: 2024
+parent: Project Updates
+grand_parent: LF Decentralized Trust TAC
+has_children: true
+has_toc: true
+child_nav_order: reversed
+---
+[//]: # (SPDX-License-Identifier: CC-BY-4.0)
+
+# 2024 Project Updates