This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/training.git
The following commit(s) were added to refs/heads/asf-site by this push:
new f38f5e5 Site checkin for project Training: Website
f38f5e5 is described below
commit f38f5e5458f83e2622bc240a964dee485853f0bb
Author: jenkins <[email protected]>
AuthorDate: Mon Sep 8 13:41:26 2025 +0000
Site checkin for project Training: Website
---
presentations/apache/incubator/mentors/index.html | 53 +++++++++++------------
presentations/apache/training/demo/index.html | 4 +-
2 files changed, 28 insertions(+), 29 deletions(-)
diff --git a/presentations/apache/incubator/mentors/index.html
b/presentations/apache/incubator/mentors/index.html
index 7ee9936..ee2be99 100644
--- a/presentations/apache/incubator/mentors/index.html
+++ b/presentations/apache/incubator/mentors/index.html
@@ -415,24 +415,24 @@ ul.byline li + li {
}
</style><link rel="stylesheet"
href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.1/css/all.min.css";
/><link rel="stylesheet"
href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.1/css/v4-shims.min.css";
/></head><body><div class="header"><div class="left"></div><div
class="right"></div></div><div class="reveal"><div class="slides"><section
id="talk"><div class="slide-content"><div class="paragraph"><p>๐ Welcome to ASF
Mentor Training</p></div>
<div class="paragraph"><p>Supporting Projects Using the Apache Way</p></div>
-<aside class="notes"><div class="paragraph"><p>Welcome everyone, explain that
this training is designed to prepare mentors for supporting Apache Incubator
podlings, emphasize that the focus is on both technical processes and ASF
culture, and share briefly your background with ASF to establish
context.</p></div></aside></div></section>
+<aside class="notes"><div class="paragraph"><p>Welcome everyone, explain that
this training is designed to prepare mentors for supporting Apache Incubator
podlings, emphasize that the focus is on both technical processes and ASF
culture, and share briefly your background with The ASF to establish
context.</p></div></aside></div></section>
<section id="table-of-contents"><h2>Table of Contents</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐งญ ASF Values &
Culture</p></li><li><p>๐ Releases & Graduation</p></li><li><p>๐ฅ Community
& Oversight</p></li><li><p>๐งโ๐ซ Mentoring in Practice</p></li><li><p>๐ฅ
Handling Conflict</p></li><li><p>๐ง Wrap-Up & Resources</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Present the training roadmap,
explain the six main sections, highlight that we will move from values and
governance, to releases and graduation, to community and oversight, to
practical mentoring and conflict resolution, then finish with resources, and
encourage participants to follow along with this
structure.</p></div></aside></div></section>
-<section id="what-youll-learn"><h2>What You’ll Learn</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐งญ ASF Values & Culture
- What makes ASF different</p></li><li><p>๐ Releases & Graduation -
Processes and pitfalls</p></li><li><p>๐ฅ Community & Oversight - Building
sustainable projects</p></li><li><p>๐งโ๐ซ Mentoring in Practice - What mentors
actually do</p></li><li><p>๐ฅ Handling Conflict - Resolution and
escalation</p></li><li><p>๐ง Wrap-Up & Resources - W [...]
-<aside class="notes"><div class="paragraph"><p>Explain that the session covers
both theory and practice, emphasize that mentors will learn not just the ASF
rules but also how to guide communities through them, and point out that each
section has practical examples and advice to take back to real mentoring
situations.</p></div></aside></div></section>
+<section id="what-youll-learn"><h2>What You’ll Learn</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐งญ ASF Values & Culture
- What makes The ASF different</p></li><li><p>๐ Releases & Graduation -
Processes and pitfalls</p></li><li><p>๐ฅ Community & Oversight - Building
sustainable projects</p></li><li><p>๐งโ๐ซ Mentoring in Practice - What mentors
actually do</p></li><li><p>๐ฅ Handling Conflict - Resolution and
escalation</p></li><li><p>๐ง Wrap-Up & Resources [...]
+<aside class="notes"><div class="paragraph"><p>Explain that the session covers
both theory and practice, emphasize that mentors will learn not just The ASF
rules but also how to guide communities through them, and point out that each
section has practical examples and advice to take back to real mentoring
situations.</p></div></aside></div></section>
<section id="asf-values-culture"><h2>ASF Values & Culture</h2><div
class="slide-content"><div class="paragraph"><p>๐ ASF Culture: The Foundation
of Everything</p></div>
-<div class="paragraph"><p>Understanding the values that make ASF
unique</p></div>
-<aside class="notes"><div class="paragraph"><p>Introduce the ASF cultural
foundation, stress that this culture is what differentiates ASF from
vendor-driven projects, and explain that every decision and process flows from
these values.</p></div></aside></div></section>
+<div class="paragraph"><p>Understanding the values that make The ASF
unique</p></div>
+<aside class="notes"><div class="paragraph"><p>Introduce the ASF cultural
foundation, stress that this culture is what differentiates The ASF from
vendor-driven projects, and explain that every decision and process flows from
these values.</p></div></aside></div></section>
<section id="core-values"><h2>Core Values</h2><div class="slide-content"><div
class="ulist"><ul><li><p>๐ฅ Community over Code</p></li><li><p>๐ Meritocracy:
Earned through contribution</p></li><li><p>๐ณ๏ธ Consensus-driven
decision-making</p></li><li><p>๐ Transparency in all actions</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Walk through each value,
explain that community over code means people and process come first,
meritocracy ensures recognition through contributions, consensus
decision-making prioritizes agreement over authority, and transparency requires
that discussions and decisions happen publicly on mailing
lists.</p></div></aside></div></section>
-<section id="why-it-matters"><h2>Why It Matters</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ Distinguishes ASF from
vendor-led models</p></li><li><p>๐ฑ Enables sustainable growth</p></li><li><p>๐ค
Builds trust and inclusion</p></li></ul></div>
+<section id="why-it-matters"><h2>Why It Matters</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ Distinguishes The ASF
from vendor-led models</p></li><li><p>๐ฑ Enables sustainable
growth</p></li><li><p>๐ค Builds trust and inclusion</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Explain that these values
protect projects from capture, they allow communities to grow sustainably over
time, and they create trust and inclusivity by making participation open to
everyone.</p></div></aside></div></section>
-<section id="red-flags-to-watch"><h2>Red Flags to Watch</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ Private
decision-making</p></li><li><p>๐ช Leadership by title or company
role</p></li><li><p>๐ค Silent or disengaged community</p></li><li><p>๐ข
Over-reliance on one company</p></li></ul></div>
+<section id="red-flags-to-watch-for"><h2>Red Flags to Watch For</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ Private
decision-making</p></li><li><p>๐ช Leadership by title or company
role</p></li><li><p>๐ค Silent or disengaged community</p></li><li><p>๐ข
Over-reliance on one company</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Warn about these red flags,
explain that private decision-making undermines transparency, leadership by
company role breaks meritocracy, silence signals disengagement, and reliance on
a single company threatens project
independence.</p></div></aside></div></section>
<section id="mentors-role-values-culture"><h2>Mentorโs Role (Values &
Culture)</h2><div class="slide-content"><div class="ulist"><ul><li><p>๐ฌ Model
and reinforce ASF values</p></li><li><p>๐ Spot and address
misalignments</p></li><li><p>๐ Encourage openness and merit</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Explain that mentors lead by
example, they should model ASF values in their behavior, they must point out
when podlings drift from those values, and they should encourage contributions
and recognition based on merit rather than
hierarchy.</p></div></aside></div></section>
-<section id="asf-governance-where-mentors-fit-in"><h2>ASF Governance: Where
Mentors Fit In</h2><div class="slide-content"><div class="ulist"><ul><li><p>๐ฅ
ASF Board โ Oversees all ASF projects and PMCs</p></li><li><p>๐ข IPMC โ Manages
incubation and mentors podlings</p></li><li><p>๐จโ๐ฉโ๐งโ๐ฆ PPMC โ Runs the
day-to-day of the podling</p></li><li><p>๐งโ๐ซ Mentors โ Bridge between the ASF
and the podling</p></li></ul></div>
-<aside class="notes"><div class="paragraph"><p>Explain the structure of ASF
governance, clarify that mentors serve as a bridge between podlings and the
ASF, stress that mentors are not managers but guides, and show how
responsibilities flow from Board to IPMC to
PPMC.</p></div></aside></div></section>
+<section id="asf-governance-where-mentors-fit-in"><h2>ASF Governance: Where
Mentors Fit In</h2><div class="slide-content"><div class="ulist"><ul><li><p>๐ฅ
The ASF Board โ Oversees all ASF projects and PMCs</p></li><li><p>๐ข IPMC โ
Manages incubation and mentors podlings</p></li><li><p>๐จโ๐ฉโ๐งโ๐ฆ PPMC โ Runs the
day-to-day of the podling</p></li><li><p>๐งโ๐ซ Mentors โ Bridge between The ASF
and the podling</p></li></ul></div>
+<aside class="notes"><div class="paragraph"><p>Explain the structure of ASF
governance, clarify that mentors serve as a bridge between podlings and The
ASF, stress that mentors are not managers but guides, and show how
responsibilities flow from Board to IPMC to
PPMC.</p></div></aside></div></section>
<section id="releasing-at-apache"><h2>Releasing at Apache</h2><div
class="slide-content"><div class="paragraph"><p>๐ Community, Not Just
Code</p></div>
<div class="paragraph"><p>Releases are not just technical, theyโre community
milestones</p></div>
<aside class="notes"><div class="paragraph"><p>Introduce releases as community
achievements, emphasize that releases demonstrate community maturity and
collaboration, and highlight that ASF releases go beyond shipping
code.</p></div></aside></div></section>
@@ -444,11 +444,11 @@ ul.byline li + li {
<aside class="notes"><div class="paragraph"><p>Describe the most frequent
mistakes, explain why these issues block releases, and stress that mentors
should encourage podlings to catch and fix them
early.</p></div></aside></div></section>
<section id="mentors-role-releases"><h2>Mentorโs Role (Releases)</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ฃ Walk them through the
process</p></li><li><p>๐งผ Review for clarity and correctness</p></li><li><p>๐
Encourage asking questions early</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Explain that mentors guide
podlings through their first releases, review artifacts and process for
correctness, and encourage communities to ask questions early instead of
waiting until votes fail.</p></div></aside></div></section>
-<section id="asf-branding-trademarks"><h2>ASF Branding &
Trademarks</h2><div class="slide-content"><div class="paragraph"><p>๐จ Branding
isnโt just visual - itโs how the project represents the ASF</p></div>
+<section id="asf-branding-trademarks"><h2>ASF Branding &
Trademarks</h2><div class="slide-content"><div class="paragraph"><p>๐จ Branding
isnโt just visual - itโs how the project represents The ASF</p></div>
<aside class="notes"><div class="paragraph"><p>Introduce branding as central
to ASF identity, stress that it prevents confusion with vendor products, and
explain that podlings must respect ASF branding guidelines throughout
incubation.</p></div></aside></div></section>
<section id="branding-rules"><h2>Branding Rules</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ Respect ASF branding and
naming guidelines</p></li><li><p>๐ท๏ธ Use โApache Foo (incubating)โ during
incubation</p></li><li><p>๐ซ Avoid project names that are already
trademarked</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Explain each branding rule,
stress that podlings must include โ(incubating)โ in the name until graduation,
and remind mentors to help communities check for trademark conflicts before
finalizing names.</p></div></aside></div></section>
-<section id="asf-name-misuse"><h2>ASF Name Misuse</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ข Donโt use the ASF Name to
Promote Vendor Products</p></li><li><p>๐ ASF project != your
product</p></li><li><p>๐ฃ Marketing must not imply ASF
endorsement</p></li><li><p>โ๏ธ When in doubt, ask <a
href="mailto:[email protected]";>[email protected]</a></p></li></ul></div>
+<section id="asf-name-misuse"><h2>ASF Name Misuse</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ข Donโt use the ASF Name to
promote vendor products</p></li><li><p>๐ ASF project != your
product</p></li><li><p>๐ฃ Marketing must not imply ASF
endorsement</p></li><li><p>โ๏ธ When in doubt, ask <a
href="mailto:[email protected]";>[email protected]</a></p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Warn against ASF name misuse,
explain that ASF projects cannot be tied to commercial marketing, and encourage
mentors to tell podlings to contact the trademarks team for advice if
unsure.</p></div></aside></div></section>
<section id="trademarks-in-practice"><h2>Trademarks in Practice</h2><div
class="slide-content"><div class="ulist"><ul><li><p>โ
Do: Use โApache Foo
(incubating)โ, clarify ASF ownership, follow guidelines</p></li><li><p>๐ซ Donโt:
Alter ASF logos, imply ASF endorsement</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Provide examples of correct and
incorrect usage, explain that mentors should review websites and materials for
compliance, and emphasize the importance of consistency in
branding.</p></div></aside></div></section>
@@ -458,12 +458,12 @@ ul.byline li + li {
<aside class="notes"><div class="paragraph"><p>Introduce graduation as the
ultimate milestone, explain that it signals readiness for independence, and
stress that graduation reflects community health more than code
maturity.</p></div></aside></div></section>
<section id="graduation-criteria"><h2>Graduation Criteria</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ฅ Diverse, active
community</p></li><li><p>๐ฆ ASF releases completed</p></li><li><p>๐งพ IP clearance
finalized</p></li><li><p>๐ Self-governance (no mentors
needed)</p></li><li><p>๐ท๏ธ Branding understood</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Walk through the criteria,
explain why each matters, and emphasize that graduation requires both community
diversity and process maturity.</p></div></aside></div></section>
-<section id="graduation-process"><h2>Graduation Process</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ฃ๏ธ PPMC discusses
readiness</p></li><li><p>๐ณ๏ธ PPMC votes</p></li><li><p>๐ฅ IPMC
votes</p></li><li><p>๐๏ธ ASF Board approves</p></li></ul></div>
+<section id="graduation-process"><h2>Graduation Process</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ฃ๏ธ PPMC discusses
readiness</p></li><li><p>๐ณ๏ธ PPMC votes</p></li><li><p>๐ฅ IPMC
votes</p></li><li><p>๐๏ธ The ASF Board gives final approval</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Explain the graduation process
step by step, stress that each layer of ASF governance must agree, and clarify
that this ensures accountability and
consensus.</p></div></aside></div></section>
<section id="more-than-a-checklist"><h2>More Than a Checklist</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐งฉ Independence over
dependence</p></li><li><p>๐งโ๐ฌ Meritocracy over control</p></li><li><p>๐งโ๐พ
Growth over code alone</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Explain that graduation is not
a box-ticking exercise, emphasize that independence, meritocracy, and growth of
the community are more important than simply completing
requirements.</p></div></aside></div></section>
-<section id="what-happens-after-graduation"><h2>What Happens After
Graduation</h2><div class="slide-content"><div class="ulist"><ul><li><p>๐๏ธ
Project becomes a Top-Level Project</p></li><li><p>๐ Reports directly to ASF
Board</p></li><li><p>๐ฆ Manages own releases and branding</p></li><li><p>๐ Drops
โ(incubating)โ from its name</p></li></ul></div>
-<aside class="notes"><div class="paragraph"><p>Explain what changes after
graduation, emphasize that the podling becomes fully independent, reports
directly to the ASF Board, and no longer requires mentor
oversight.</p></div></aside></div></section>
+<section id="what-happens-after-graduation"><h2>What Happens After
Graduation</h2><div class="slide-content"><div class="ulist"><ul><li><p>๐๏ธ
Project becomes a Top-Level Project</p></li><li><p>๐ Reports directly to The
ASF Board</p></li><li><p>๐ฆ Manages own releases and branding</p></li><li><p>๐
Drops โ(incubating)โ from its name</p></li></ul></div>
+<aside class="notes"><div class="paragraph"><p>Explain what changes after
graduation, emphasize that the podling becomes fully independent, reports
directly to The ASF Board, and no longer requires mentor
oversight.</p></div></aside></div></section>
<section id="mentors-role-graduation"><h2>Mentorโs Role (Graduation)</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ฌ Help assess readiness
honestly</p></li><li><p>โ Support discussions about retiring if
needed</p></li><li><p>๐ช Guide the transition to TLP</p></li><li><p>๐ Disengage
and let PMC lead</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Explain that mentors must be
honest about readiness, even if that means considering retirement, stress that
they should help with transition to independence, and remind them that their
final role is to step back and let the PMC govern
itself.</p></div></aside></div></section>
<section id="community-oversight"><h2>Community & Oversight</h2><div
class="slide-content"><div class="paragraph"><p>๐ Podling Community
Building</p></div>
@@ -478,32 +478,31 @@ ul.byline li + li {
<aside class="notes"><div class="paragraph"><p>Explain that before graduation,
podlings must demonstrate independence, growth, and openness, emphasize that
mentors should support but not lead these
decisions.</p></div></aside></div></section>
<section id="asf-voting-decision-making"><h2>ASF Voting & Decision
Making</h2><div class="slide-content"><div class="paragraph"><p>๐ณ๏ธ Voting isnโt
just procedure, itโs consensus</p></div>
<aside class="notes"><div class="paragraph"><p>Introduce ASF voting, explain
that it formalizes consensus, and emphasize that it reflects community
agreement rather than authority.</p></div></aside></div></section>
-<section id="decision-making-the-apache-way"><h2>Decision-Making the Apache
Way</h2><div class="slide-content"><div class="ulist"><ul><li><p>๐ณ๏ธ Votes
enable consensus</p></li><li><p>๐ฌ dev@ is the central place for
decisions</p></li><li><p>๐ค Consensus > control</p></li><li><p>๐ Documented
> assumed</p></li></ul></div>
+<section id="decision-making-the-apache-way"><h2>Decision-Making the Apache
Way</h2><div class="slide-content"><div class="ulist"><ul><li><p>๐ณ๏ธ Votes can
record consensus</p></li><li><p>๐ฌ dev@ is the central place for
decisions</p></li><li><p>๐ค Consensus > control</p></li><li><p>๐ Documented
> assumed</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Explain how ASF makes
decisions, stress that votes record consensus, mailing lists ensure
transparency, and documentation ensures clarity for
everyone.</p></div></aside></div></section>
<section id="what-needs-a-vote"><h2>What Needs a Vote</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ฆ Releases</p></li><li><p>๐ค
Adding committers/PMC</p></li><li><p>๐ Graduation/resolutions</p></li><li><p>๐๏ธ
Formal policy changes</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>List the actions that require
votes, explain why formal consensus is needed, and remind mentors to teach
podlings these requirements.</p></div></aside></div></section>
-<section id="how-voting-works"><h2>How Voting Works</h2><div
class="slide-content"><div class="ulist"><ul><li><p>โ
+1 =
Approve</p></li><li><p>โ 0 = No opinion</p></li><li><p>โ -1 = Block (with
explanation)</p></li><li><p>Binding = IPMC member</p></li></ul></div>
+<section id="how-voting-works"><h2>How Voting Works</h2><div
class="slide-content"><div class="ulist"><ul><li><p>โ
+1 =
Approve</p></li><li><p>โ 0 = No opinion</p></li><li><p>โ -1 = Block (with
explanation)</p></li><li><p>Binding = IPMC member (during
incubation)</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Explain voting mechanics,
stress that binding votes come from IPMC members in incubation, and emphasize
that -1 votes must be explained to allow discussion and
resolution.</p></div></aside></div></section>
<section id="lazy-consensus"><h2>Lazy Consensus</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ No objections in 72h โ
proceed</p></li><li><p>๐ข Use [DISCUSS]</p></li><li><p>๐งผ Great for routine
changes</p></li><li><p>๐งโ๐ซ Mentors should model this early
on</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Explain lazy consensus, stress
that it enables efficient decision-making when no objections arise, and
encourage podlings to use it for non-critical issues while keeping
transparency.</p></div></aside></div></section>
<section id="mentors-role-voting"><h2>Mentorโs Role (Voting)</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ฌ Explain
expectations</p></li><li><p>๐ Watch for rushed decisions</p></li><li><p>๐งญ
Encourage discussion first</p></li><li><p>๐ช Help shift to
self-management</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Explain that mentors should
teach voting expectations, ensure discussions happen before votes, watch for
rushed or unclear decisions, and encourage communities to become
self-reliant.</p></div></aside></div></section>
-<section id="independence-vs-corporate-influence"><h2>Independence vs
Corporate Influence</h2><div class="slide-content"><div class="paragraph"><p>๐ข
Independence isnโt just ideal - itโs essential to ASF governance</p></div>
+<section id="independence-vs-corporate-influence"><h2>Independence vs
Corporate Influence</h2><div class="slide-content"><div class="paragraph"><p>๐ข
Independence isnโt just ideal - itโs essential to The ASF and it’s
projects</p></div>
<aside class="notes"><div class="paragraph"><p>Introduce the principle of
independence, emphasize that ASF projects must not be controlled by one
company, and explain that mentors are responsible for safeguarding this
value.</p></div></aside></div></section>
<section id="signs-of-vendor-control"><h2>Signs of Vendor Control</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ผ All committers from one
company</p></li><li><p>๐ Decisions from internal meetings</p></li><li><p>๐งต
Little dev@ activity</p></li><li><p>๐ค Dismissive or unwelcoming to outside
contributors</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Describe the warning signs of
vendor control, explain that they threaten ASF values, and stress that mentors
should act if they see these patterns.</p></div></aside></div></section>
<section id="mentors-role-independence"><h2>Mentorโs Role
(Independence)</h2><div class="slide-content"><div class="ulist"><ul><li><p>๐
Watch for dominance</p></li><li><p>๐ Encourage diverse voices</p></li><li><p>๐ค
Broaden participation</p></li><li><p>๐ข Raise concerns if imbalance
persists</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Explain that mentors must
actively encourage diversity, support contributions from multiple
organizations, and escalate if vendor control remains
unresolved.</p></div></aside></div></section>
-<section id="podling-reporting-oversight"><h2>Podling Reporting &
Oversight</h2><div class="slide-content"><div class="paragraph"><p>๐ Reporting
isnโt just paperwork - itโs how we ensure accountability and support</p></div>
+<section id="podling-reporting-oversight"><h2>Podling Reporting &
Oversight</h2><div class="slide-content"><div class="paragraph"><p>๐ Reporting
isnโt just paperwork - itโs shows progress and ensures support</p></div>
<aside class="notes"><div class="paragraph"><p>Introduce reporting as a
governance requirement, explain that it builds transparency and allows the IPMC
to support projects, and stress that it should not be seen as
bureaucracy.</p></div></aside></div></section>
-<section id="why-reporting-matters"><h2>Why Reporting Matters</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ Keeps ASF
informed</p></li><li><p>๐ Identifies risks</p></li><li><p>๐ข Builds
transparency</p></li><li><p>๐ ๏ธ Enables mentor/IPMC support
-๐ฎ Due quarterly โ add to wiki</p></li></ul></div>
-<aside class="notes"><div class="paragraph"><p>Explain the value of reports,
emphasize that they inform the ASF, surface risks, and invite support from
mentors and the IPMC when needed.</p></div></aside></div></section>
+<section id="why-reporting-matters"><h2>Why Reporting Matters</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ Keeps The ASF
informed</p></li><li><p>๐ Identifies risks</p></li><li><p>๐ข Builds
transparency</p></li><li><p>๐ ๏ธ Enables mentor/IPMC support</p></li><li><p>๐ฎ Due
quarterly โ add to wiki</p></li></ul></div>
+<aside class="notes"><div class="paragraph"><p>Explain the value of reports,
emphasize that they inform The ASF, surface risks, and invite support from
mentors and the IPMC when needed.</p></div></aside></div></section>
<section id="what-goes-in-a-podling-report"><h2>What Goes in a Podling
Report</h2><div class="slide-content"><div class="ulist"><ul><li><p>๐ Progress
since last report</p></li><li><p>๐ฅ Community activity</p></li><li><p>๐ฆ Release
activity</p></li><li><p>๐ Issues or concerns</p></li><li><p>๐ช Steps toward
graduation</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Explain the components of a
podling report, stress that honesty is more important than perfection, and
remind mentors to help podlings cover each
area.</p></div></aside></div></section>
<section id="what-the-ipmc-looks-for"><h2>What the IPMC Looks For</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ง Shared work, not one
person</p></li><li><p>๐ฌ dev@ activity beyond GitHub</p></li><li><p>โฑ Timely
releases</p></li><li><p>๐ Evidence of self-governance</p></li><li><p>๐งญ
Alignment with ASF values</p></li></ul></div>
-<aside class="notes"><div class="paragraph"><p>Describe the IPMC perspective,
explain that they want to see broad participation, activity on mailing lists,
consistent releases, independence, and cultural alignment with
ASF.</p></div></aside></div></section>
-<section id="oversight-red-flags"><h2>Oversight Red Flags</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ Declining community
activity</p></li><li><p>๐ Private decisions</p></li><li><p>๐ข One-company
dominance</p></li><li><p>๐ซ Missed or unclear reports</p></li><li><p>๐ฏ Repeated
release or IP issues</p></li></ul></div>
+<aside class="notes"><div class="paragraph"><p>Describe the IPMC perspective,
explain that they want to see broad participation, activity on mailing lists,
consistent releases, independence, and cultural alignment with The
ASF.</p></div></aside></div></section>
+<section id="oversight-red-flags"><h2>Oversight Red Flags</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ Declining community
activity</p></li><li><p>๐ Private decisions</p></li><li><p>๐ข One-company
dominance</p></li><li><p>๐ซ Missed or unclear reports</p></li><li><p>๐ฏ Repeated
release issues or IP issues</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>List red flags, explain why
they matter, and remind mentors to raise these issues early with the IPMC so
support can be provided.</p></div></aside></div></section>
<section id="mentors-role-reporting"><h2>Mentorโs Role (Reporting)</h2><div
class="slide-content"><div class="ulist"><ul><li><p>โ๏ธ Help with early
reports</p></li><li><p>โ๏ธ Be honest, donโt sugarcoat</p></li><li><p>๐ Raise
issues if needed</p></li><li><p>๐ฃ Advocate for podling</p></li><li><p>๐ช Step
back as PPMC takes over</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Explain that mentors often help
with first reports, but must encourage podlings to take ownership, stress
honesty, raise issues transparently, and gradually step
back.</p></div></aside></div></section>
@@ -527,15 +526,15 @@ ul.byline li + li {
<aside class="notes"><div class="paragraph"><p>Normalize conflict, explain
that it occurs even in healthy communities, and emphasize that how conflict is
handled defines community health.</p></div></aside></div></section>
<section id="conflict-happens"><h2>๐ฅ Conflict Happens</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ง Technical
debates</p></li><li><p>๐ฃ๏ธ Interpersonal friction</p></li><li><p>๐ข
Company-driven tension</p></li><li><p>๐ถ Silence or passive
resistance</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Conflict is a natural part of
ASF projects, it can show up as technical debates where contributors strongly
disagree, interpersonal friction between community members, company-driven
tension when corporate interests clash with community goals, or silence and
passive resistance where contributors disengage instead of voicing concerns,
mentors should normalize conflict as a chance to reinforce ASF values,
encourage open discussion on the maili [...]
-<section id="signs-of-dysfunction"><h2>Signs of Dysfunction</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ก Heated
arguments</p></li><li><p>๐ Decisions without discussion</p></li><li><p>๐ค
Newcomers ignored</p></li><li><p>๐ Declining dev@ engagement</p></li><li><p>๐ง
One person doing all work</p></li></ul></div>
+<section id="signs-of-dysfunction"><h2>Signs of Dysfunction</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ก Heated
arguments</p></li><li><p>๐ Decisions without discussion</p></li><li><p>๐ค
Newcomers ignored</p></li><li><p>๐ Declining dev@ engagement</p></li><li><p>๐ง
One person doing all the work</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>List dysfunction signs, explain
that unresolved conflict, lack of discussion, ignoring newcomers, declining
participation, or over-reliance on one person are warning signals that mentors
should act on.</p></div></aside></div></section>
<section id="conflict-resolution-strategies"><h2>Conflict Resolution
Strategies</h2><div class="slide-content"><div class="ulist"><ul><li><p>๐ง
De-escalate</p></li><li><p>๐จ๏ธ Focus on facts</p></li><li><p>๐ฌ Move to
dev@</p></li><li><p>๐งโ๐ผ Mediate neutrally</p></li><li><p>๐ Return to ASF
values</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Provide strategies for
resolving conflict, explain that de-escalation calms tension, focusing on facts
keeps discussion rational, moving to dev@ ensures transparency, mediation helps
balance, and ASF values provide a common
framework.</p></div></aside></div></section>
<section id="mentors-role-conflict"><h2>Mentorโs Role (Conflict)</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ Listen
first</p></li><li><p>๐งพ Keep conversations on dev@</p></li><li><p>๐ Find root
causes</p></li><li><p>๐ Intervene early</p></li><li><p>๐ข Know when to
escalate</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Explain that mentors should
listen to all sides, ensure transparency by keeping discussions on list,
identify underlying issues, step in early to guide resolution, and escalate if
needed.</p></div></aside></div></section>
-<section id="escalation-paths"><h2>Escalation Paths</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ค Resolve on dev@
first</p></li><li><p>๐ง Contact <a
href="mailto:[email protected]";>[email protected]</a></p></li><li><p>โ๏ธ
Escalate to IPMC</p></li><li><p>๐ ๏ธLegal/misconduct โ ASF
Board</p></li></ul></div>
-<aside class="notes"><div class="paragraph"><p>Explain the escalation ladder,
emphasize starting with dev@, then moving to private@ if unresolved, escalating
to the IPMC for ongoing issues, and involving the ASF Board for legal or
serious misconduct.</p></div></aside></div></section>
-<section id="whats-next"><h2>Whatโs Next?</h2><div class="slide-content"><div
class="paragraph"><p>๐ฑ Mentoring at ASF means growing communities, not just
guiding projects</p></div>
+<section id="escalation-paths"><h2>Escalation Paths</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ค Resolve on dev@
first</p></li><li><p>๐ง Contact <a
href="mailto:[email protected]";>[email protected]</a></p></li><li><p>โ๏ธ
Escalate to IPMC</p></li><li><p>๐ ๏ธLegal/misconduct โ The ASF
Board</p></li></ul></div>
+<aside class="notes"><div class="paragraph"><p>Explain the escalation ladder,
emphasize starting with dev@, then moving to private@ if unresolved, escalating
to the IPMC for ongoing issues, and involving The ASF Board for legal or
serious misconduct.</p></div></aside></div></section>
+<section id="whats-next"><h2>Whatโs Next?</h2><div class="slide-content"><div
class="paragraph"><p>๐ฑ Mentoring at The ASF means growing communities, not just
guiding projects</p></div>
<aside class="notes"><div class="paragraph"><p>Summarize the role of mentors,
emphasize that their goal is to grow sustainable communities that can thrive
independently, and remind participants that mentoring is about enabling, not
directing.</p></div></aside></div></section>
<section id="key-takeaways"><h2>Key Takeaways</h2><div
class="slide-content"><div class="ulist"><ul><li><p>๐ฑ Model ASF
culture</p></li><li><p>๐ฅ Support diversity</p></li><li><p>๐ฆ Releases show
readiness</p></li><li><p>๐ Graduation = independence</p></li><li><p>๐ฉ Spot red
flags early</p></li><li><p>๐งญ Guide, donโt control</p></li></ul></div>
<aside class="notes"><div class="paragraph"><p>Reinforce the most important
lessons, remind mentors to model culture, encourage diversity, treat releases
as milestones, aim for graduation independence, watch for red flags, and
remember that guidance is different from
control.</p></div></aside></div></section>
diff --git a/presentations/apache/training/demo/index.html
b/presentations/apache/training/demo/index.html
index 8addf78..013437c 100644
--- a/presentations/apache/training/demo/index.html
+++ b/presentations/apache/training/demo/index.html
@@ -414,7 +414,7 @@ ul.byline li + li {
margin-top: 0.25em;
}
</style><link rel="stylesheet"
href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.1/css/all.min.css";
/><link rel="stylesheet"
href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.15.1/css/v4-shims.min.css";
/></head><body><div class="header"><div class="left"></div><div
class="right"></div></div><div class="reveal"><div class="slides"><section
id="example-presentation"><h2>Example Presentation</h2><div
class="slide-content"><div class="paragraph"><p>Doc Writer <<a hr [...]
-2025-09-01
+2025-08-30
:revnumber: 1.0.0-SNAPSHOT
:example-caption!:</p></div></div></section>
<section id="introduction"><h2>Introduction</h2><div
class="slide-content"><div class="ulist"><ul><li class="fragment"><p>This is a
presentation for an example project.</p></li><li class="fragment"><p>This
project does something.</p></li><li class="fragment"><p>We just haven’t
decided what that is yet.</p></li></ul></div></div></section>
@@ -442,7 +442,7 @@ Neat huh?</p></div></aside></div></section>
<aside class="notes"><div class="ulist"><ul><li><p>Find icons here: <a
href="https://fontawesome.com/v4.7.0/icons/";
class="bare">https://fontawesome.com/v4.7.0/icons/</a></p></li><li><p>Color
icons by defining css styles in apache.css and referencing them with
"role"</p></li></ul></div></aside></div></section>
<section><section id="diagrams"><h2>Diagrams</h2><div
class="slide-content"><div class="paragraph"><p>Press the down arrow key to see
the different types of diagrams</p></div></div></section><section
id="ditaa-diagram"><h2>Ditaa Diagram</h2><div class="slide-content"><div
class="imageblock"><img src="images/asciidoctor-diagram-process.png"
alt="asciidoctor diagram process"></div></div></section><section
id="plantuml-diagram"><h2>PlantUML Diagram</h2><div class="slide-content"><div
class= [...]
convert: unable to read font `Impact' @ error/annotate.c/RenderFreetype/1396.
-convert: no images defined `/tmp/meme20250905-1-8m2gwv.png' @
error/convert.c/ConvertImageCommand/3229.</pre></div></div></div></section><section
id="entity-relation-diagram"><h2>Entity Relation Diagram</h2><div
class="slide-content"><div class="imageblock"><img src="images/erd-test.svg"
alt="erd test"></div>
+convert: no images defined `/tmp/meme20250908-1-fjhphw.png' @
error/convert.c/ConvertImageCommand/3229.</pre></div></div></div></section><section
id="entity-relation-diagram"><h2>Entity Relation Diagram</h2><div
class="slide-content"><div class="imageblock"><img src="images/erd-test.svg"
alt="erd test"></div>
<aside class="notes"></aside></div></section><section
id="mermaid-flowchart"><h2>Mermaid: Flowchart</h2><div
class="slide-content"><div class="listingblock"><div
class="content"><pre>Failed to generate image: mmdc failed:
Error: Failed to launch the browser process!
/root/.cache/puppeteer/chrome/linux-1108766/chrome-linux/chrome: error while
loading shared libraries: libnss3.so: cannot open shared object file: No such
file or directory
