Changes based on the September 4, 2024 TAC meeting

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

docs/governance/deliverable-lifecycle.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-This document outlines the process for publishing deliverables in the OpenWallet Foundation technical community. These deliverables will be created by either [task forces](./task-force-process.md) or [special interest groups](./special-interest-group-process.md). The types of deliverables they can create depend on their goals, 
+This document outlines the process for publishing deliverables in the OpenWallet Foundation technical community. These deliverables will be created by [task forces](./task-force-process.md), [special interest groups](./special-interest-group-process.md), or projects. The types of deliverables they can create depend on their goals, 
 objectives, and scope. Here are some examples:
 
 1. **Reports**: Summarize findings or recommendations.  These might be formal or informal.
@@ -38,40 +38,44 @@ flowchart
   c -->|Create Release| v
 ```
 
-A deliverable begins as a "draft" and retains this status until submitted to the community for review. At this point, the deliverable will be considered to be in the "review" stage and retains this status until the review period has ended. After the review period has ended, the task force or special interest group will determine if the deliverable is ready for release. If the task force or special interest group chooses to make changes, the deliverable will return to a "draft" stage where they can address the concerns of the community. The task force or special interest group can also determine that the deliverable is ready for release. In which case, a "released" version can be created. See [required contents](#required-contents) for more information on what should be included within a "released" deliverable.
+A deliverable begins as a "draft" and retains this status until submitted to the community for review. At this point, the deliverable will be considered to be in the "review" stage and retains this status until the review period has ended. After the review period has ended, the task force, special interest group, or project will determine if the deliverable is ready for release. If the task force, special interest group, or project chooses to make changes, the deliverable will return to a "draft" stage where they can address the concerns of the community. The task force, special interest group, or project can also determine that the deliverable is ready for release. In which case, a "released" version can be created. See [required contents](#required-contents) for more information on what should be included within a "released" deliverable.
 
 ### Draft
 
-During the "draft" stage, the deliverable is being prepared by the task force or special interest group. This includes writing the technical content and ensuring that it meets the standards of the OWF technical community. If there are any concerns about the technical content that cannot be addressed by consensus of the task force or special interest group members, then the community may address these concerns during the "review" stage.
+During the "draft" stage, the deliverable is being prepared by the task force, special interest group, or project. This includes writing the technical content and ensuring that it meets the standards of the OWF technical community. If there are any concerns about the technical content that cannot be addressed by consensus of the task force, special interest group, or project members, then the community may address these concerns during the "review" stage.
 
 ### Submission
 
-The task force or special interest group lead may submit a version of their deliverable to the community for review. They can do this by sending an email to the [TAC mailing list](mailto:tac@lists.openwallet.foundation). The email should include the following information:
+The task force, special interest group, or project lead may submit a version of their deliverable to the community for review. They can do this by sending an email to the [TAC mailing list](mailto:tac@lists.openwallet.foundation). The email should include the following information:
 
 - A brief description of the deliverable.
 - A link to the deliverable. Ideally, this should be a link to a pull request that contains the version of the deliverable where people in the community will be able to provide their feedback.
-- A link to the task force or special interest group that submitted the deliverable.
+- A link to the task force, special interest group, or project that submitted the deliverable.
 
 ### Review
 
-The applicable period to review a submitted deliverable will be no shorter than four weeks. The community will make reasonable efforts to provide feedback on the submitted version during the review period and provide any critical comments or objections, with sufficient specificity for the task force or special interest group members to respond and, if required, to facilitate resolution. 
+The applicable period to review a submitted deliverable will be no shorter than four weeks. The community will make reasonable efforts to provide feedback on the submitted version during the review period and provide any critical comments or objections, with sufficient specificity for the task force, special interest group, or project members to respond and, if required, to facilitate resolution. 
 
 !!! info
 
     Comments and feedback can be provided by anyone in the OWF community.
 
 ### Ready for Release
 
-After the applicable review period has elapsed, the task force or special interest group members can review the feedback received and determine if the deliverable is ready for review. If the task force or special interest group chooses to make changes, the deliverable will return to a "draft" stage where they can address the concerns of the community. The task force or special interest group can also determine that the deliverable is ready for release. In which case, a "released" version can be created. 
+After the applicable review period has elapsed, the task force, special interest group, or project members can review the feedback received and determine if the deliverable is ready for review. If the task force, special interest group, or project chooses to make changes, the deliverable will return to a "draft" stage where they can address the concerns of the community. The task force, special interest group, or project can also determine that the deliverable is ready for release. In which case, a "released" version can be created. 
 
 ### Released
 
-The task force or special interest group should ensure that the [required contents](#required-contents) are included in any release.
+The task force, special interest group, or project should ensure that the [required contents](#required-contents) are included in any release.
 
 ## Required Contents
 
 ### Copyright Notice
 
+!!! important
+
+    If the deliverable originated from an external entity that has already provided a copyright notice, there is no need to replace that notice.
+
 The copyright notice must be included in all versions of the deliverable. The copyright notice should include the OpenWallet Foundation as well as the year of publication.
 
 !!! quote
@@ -86,18 +90,10 @@ The license notice must be included in all versions of the deliverable. The lice
 
     These materials are made available under and are subject to the Creative Commons Attribution 4.0 International license (http://creativecommons.org/licenses/by/4.0/legalcode).
 
-### "Non-Representative" Disclaimer
-
-A "non-representative" disclaimer should be included in all versions of the deliverable. The "non-representative" disclaimer should include the following text:
-
-#### For a Task Force
-
-!!! quote
-
-    These materials are a deliverable of the _task force name_ Task Force and were created by the contributors to that Task Force. It has not been reviewed, approved, or endorsed by the OpenWallet Foundation ("OWF") and its members.
+### Disclaimer
 
-#### For a SIG
+A disclaimer should be included in all versions of the deliverable. The disclaimer should include the following text:
 
 !!! quote
 
-    These materials are a deliverable of the _sig name_ SIG and were created by the contributors to that SIG. It has not been reviewed, approved, or endorsed by the OpenWallet Foundation ("OWF") and its members.
+    These materials are a deliverable of the OWF community. If you have concerns or suggestions regarding the content, please file a pull request.