community call and module deprecation updates

docs/content/_index.md

@@ -5,6 +5,16 @@ type: home
 description: 'Azure Verified Modules - The Microsoft IaC Module Strategy'
 ---
 
+{{% notice style="important" %}}
+
+Join the AVM team for our next **external community call**, held on **July 1st, 2025**! 🎉
+
+**Register here to attend**: [https://aka.ms/AVM/CommunityCall](https://aka.ms/AVM/CommunityCall)
+
+To find out more about future calls and watch the recordings of previous ones, see the [Community Calls page](/Azure-Verified-Modules/resources/community)!
+
+{{% /notice %}}
+
 {{% notice style="important" %}}
 Get ready to accelerate your Azure platform journey with Azure Verified Modules! In our latest **Microsoft Build** [**session**](https://aka.ms/BUILD25/BRK196), we showcased how AVM streamlines cloud deployment with speed, reliability, and best practices—empowering you to build smarter and faster on Azure.
 

docs/content/help-support/issue-triage/avm-issue-triage.md

@@ -269,6 +269,7 @@ If a module meets the criteria described in the "[Deprecated Modules]({{% sitepa
       - Place the information notice - with the text below - in the `README.md` file, in the module's root.
       - Archive the module's repository on GitHub.
     - Once the information notice is placed, submit a Pull Request.
+5. Keep the module's `-owners-` and `-contributors-` GitHub teams, as these will keep granting access to the source code of the module.
 
 Place the following information notice in the module's repository:
 

docs/content/resources/community.md

@@ -18,16 +18,29 @@ Let's make each community call a celebration of connection and collaboration!
 
 ## Upcoming Events
 
-Stay tuned, to be announced! 👂
+<!-- Stay tuned, to be announced! 👂 -->
 
-<!-- {{% notice style="note" %}}
+### 1st July 2025
 
-This occurrence is optimized for EMEA/APAC time zones.
+{{% notice style="note" %}}
+
+This occurrence is optimized for EMEA/ATZ time zones.
 
 {{% /notice %}}
 
-- [Registration]()
-- [GitHub Issue for Q&A section]() -->
+#### High level agenda (WIP)
+
+- Road to AVM v1
+- AVM integration to Copilot experiences
+- Website Updates
+- Terraform Migration tool
+- Guest speakers (MVPs, Partner, Customer and/or PG teams)
+- Q&A / Open discussion: attendees can ask questions, share experiences/stories, provide feedback and suggestions
+
+#### Call to action
+
+- [Register](https://aka.ms/AVM/CommunityCall) for this event
+- Lave a comment on this [GitHub Issue for the Q&A section](https://github.com/Azure/Azure-Verified-Modules/issues/2109)
 
 ## Previous Events
 

docs/content/specs-defs/module-lifecycle.md

@@ -8,20 +8,24 @@ This section outlines the different stages of a module's lifecycle:
 
 {{< mermaid zoom="false">}}
 flowchart LR
-    Proposed["1 - Proposed ⚪"] --> Available["2 - Available 🟢"]
-    Proposed --> |Acceptance criteria not met| Rejected[Rejected]
+    Proposed["1 - Proposed ⚪"] --> |Acceptance criteria met ✅| Available["2 - Available 🟢"]
+      click Proposed "{{% siteparam base %}}/specs/shared/module-lifecycle/#1-proposed-modules"
+      click Available "{{% siteparam base %}}/specs/shared/module-lifecycle/#2-available-modules"
+    Proposed --> |Acceptance criteria not met ❌| Rejected[Rejected]
     Available --> |Module temporarily not maintained| Orphaned["3 - Orphaned 🟡"]
     Orphaned --> |End of life| Deprecated["4 - Deprecated 🔴"]
+      click Orphaned "{{% siteparam base %}}/specs/shared/module-lifecycle/#3-orphaned-modules"
     Orphaned --> |New owner identified| Available
     Available --> |End of life| Deprecated
+      click Deprecated "{{% siteparam base %}}/specs/shared/module-lifecycle/#4-deprecated-modules"
     style Proposed fill:#ADD8E6,stroke:#333,stroke-width:1px
     style Orphaned fill:#F4A460,stroke:#333,stroke-width:1px
     style Available fill:#8DE971,stroke:#333,stroke-width:4px
     style Deprecated fill:#000000,stroke:#333,stroke-width:1px,color:#fff
     style Rejected fill:#A2A2A2,stroke:#333,stroke-width:1px
 {{< /mermaid >}}
 
-{{% notice style="info" %}}
+{{% notice style="important" %}}
 If a module proposal is rejected, the issue is closed and the module's lifecycle ends.
 {{% /notice %}}
 
@@ -41,6 +45,12 @@ The proposal should include the following information:
 
 The AVM core team will review the proposal, and administrate the module.
 
+{{% notice style="info" %}}
+
+To **propose a new module**, submit a [module proposal](https://aka.ms/AVM/ModuleProposal) issue in the AVM repository.
+
+{{% /notice %}}
+
 ## 2. Available modules
 
 Once a module has been fully developed, tested and published in the main branch of the repository and the corresponding public registry (Bicep or Terraform), it is then considered to be "available" and can be used by the community. The module is maintained by the module owner(s). Feature or bug fix requests and related pull requests can be submitted by anyone to the module owner(s) for review.
@@ -55,6 +65,12 @@ It is critical to the consumers experience that modules continue to be maintaine
 4. While a module is in an orphaned state, only security and bug fixes **MUST** be made, no new feature development will be worked on until a new owner is found that can then lead this effort for the module.
 5. An issue will be created on the central AVM repo (`Azure/Azure-Verified-Modules`) to track the finding of a new owner for a module.
 
+{{% notice style="info" %}}
+
+To **orphan a module**, submit an [orphaned module](https://aka.ms/AVM/OrphanedModule) issue in the AVM repository.
+
+{{% /notice %}}
+
 ### Notification of a Module Becoming Orphaned
 
 {{% notice style="important" %}}
@@ -83,6 +99,7 @@ Once a module reaches the end of its lifecycle (e.g., it's permanently replaced
 4. It will be a clearly indicated on the module's repo that new issues can no longer be submitted for the module:
     - Bicep: The module will be taken off the list of available modules in related issue templates.
     - Terraform: The module's repo will be archived.
+5. The module's `-owners-` and `-contributors-` GitHub teams will be retained indefinitely as these grant access to the source code of the module.
 
 It is recommended to migrate to a replacement/alternative version of the module, if available.
 
@@ -101,7 +118,9 @@ The information notice **MUST** include the following statement:
 {{% /notice %}}
 
 {{% notice style="info" %}}
-The module's `-owners-` and `-contributors-` GitHub teams will be retained indefinitely as these grant access to the source code of the module.
+
+To **deprecate a module**, submit a [deprecated module](https://aka.ms/AVM/DeprecatedModule) issue in the AVM repository.
+
 {{% /notice %}}
 
 {{% expand title="➕ Retrieve the available versions of a deprecated module" %}}