You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@training.apache.org by jm...@apache.org on 2025/10/14 08:10:19 UTC
(training) branch develop updated (cb0233d -> c0a149f)
This is an automated email from the ASF dual-hosted git repository.
jmclean pushed a change to branch develop
in repository https://gitbox.apache.org/repos/asf/training.git
from cb0233d Add Incubator community building slide deck
new f7259a5 minor improvements
new 55a5a97 update meritocracy to be more inclusive
new c0a149f update Meritocracy
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../CommunityBuilding/src/main/asciidoc/index.adoc | 24 ++++++++---------
.../Goverance/src/main/asciidoc/index.adoc | 30 +++++++++++-----------
.../src/main/asciidoc/index.adoc | 14 +++++-----
3 files changed, 33 insertions(+), 35 deletions(-)
(training) 03/03: update Meritocracy
Posted by jm...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
jmclean pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/training.git
commit c0a149f6a349e53798b60b02f975649aff5fcbb6
Author: Justin Mclean <jm...@apache.org>
AuthorDate: Tue Oct 14 19:09:31 2025 +1100
update Meritocracy
---
.../VotingAndConsensus/src/main/asciidoc/index.adoc | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/content/Apache/Incubator/VotingAndConsensus/src/main/asciidoc/index.adoc b/content/Apache/Incubator/VotingAndConsensus/src/main/asciidoc/index.adoc
index bf4316e..32719af 100644
--- a/content/Apache/Incubator/VotingAndConsensus/src/main/asciidoc/index.adoc
+++ b/content/Apache/Incubator/VotingAndConsensus/src/main/asciidoc/index.adoc
@@ -56,9 +56,9 @@ Consensus gives contributors a voice, prevents dominance by any one entity, and
== Principles of Consensus Building
-* *Community Over Code:* decisions belong to the community, not individuals or companies.
-* *Meritocracy:* every voice matters; influence is earned through constructive contribution.
-* *Transparency:* decisions are made publicly on the project mailing list.
+* *Community Over Code:* decisions belong to the community, not individuals or companies.
+* *Trust Through Contribution:* influence is earned by showing up, contributing, and engaging respectfully.
+* *Transparency:* decisions are made publicly on the project mailing list.
* *Respect and Inclusiveness:* dialogue and differing views strengthen decisions.
[.notes]
@@ -95,12 +95,12 @@ Not every decision needs a formal vote, in fact, most don’t.
The three main types are lazy consensus, consensus after discussion, and formal votes.
--
-=== Lazy Consensus
+== Lazy Consensus
* The default ASF decision model.
* A proposal is posted; if no one objects within 72 hours, it’s approved.
* Works well for routine or low-risk actions like website or documentation updates.
-* Encourages forward progress without bureaucracy.
+* Encourages forward progress without bureaucracy.
_Example:_
“I’ll merge this pull request in 72 hours unless anyone objects.”
@@ -112,7 +112,7 @@ It works best when contributors actively follow the mailing list and feel welcom
Silence from disengaged participants isn’t consensus, it’s apathy, which mentors should watch for.
--
-=== Consensus After Discussion
+== Consensus After Discussion
* Used when objections arise.
* Discuss until all significant concerns are addressed.
@@ -126,7 +126,7 @@ It’s about inclusion and progress, not unanimity.
The key is active listening, understanding and adapting to valid concerns until the community feels comfortable moving forward.
--
-=== Formal Votes
+== Formal Votes
* Used when ASF policy or legal requirements require a clear decision.
* Common examples:
(training) 02/03: update meritocracy to be more inclusive
Posted by jm...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
jmclean pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/training.git
commit 55a5a97414dc306f7f8e3f182e040e3a75c941a7
Author: Justin Mclean <jm...@apache.org>
AuthorDate: Tue Oct 14 19:09:02 2025 +1100
update meritocracy to be more inclusive
---
.../CommunityBuilding/src/main/asciidoc/index.adoc | 24 ++++++++++------------
1 file changed, 11 insertions(+), 13 deletions(-)
diff --git a/content/Apache/Incubator/CommunityBuilding/src/main/asciidoc/index.adoc b/content/Apache/Incubator/CommunityBuilding/src/main/asciidoc/index.adoc
index 6b74003..25db0a2 100644
--- a/content/Apache/Incubator/CommunityBuilding/src/main/asciidoc/index.adoc
+++ b/content/Apache/Incubator/CommunityBuilding/src/main/asciidoc/index.adoc
@@ -125,25 +125,23 @@ Assign mentors or “buddies” to guide new contributors through their first fe
Encourage experienced contributors to mentor others in turn, this builds continuity and community depth.
--
-== Encouraging Meritocracy and Growth
+## Building Trust and Recognising Growth
-* Recognize sustained effort, not status.
-* Nominate new committers and PPMC members openly and transparently.
-* Avoid “in-crowds” or hidden decision-making.
-* Encourage shared ownership and delegate trust, empower others to lead.
-* Pair recognition with empowerment, trust contributors with meaningful work.
+* Recognize sustained effort and impact, not titles or status.
+* Nominate new committers and PPMC members through open, transparent discussions.
+* Avoid “in-crowds” or informal hierarchies, ensure decisions are visible and fair.
+* Encourage shared ownership: delegate trust, empower others to lead.
+* Pair recognition with opportunity, invite contributors to take on meaningful roles.
[.notes]
--
-Meritocracy is central to The Apache Way, but it’s often misunderstood.
-At Apache, “meritocracy” means *trust built through contribution*, not authority by seniority.
-Merit is demonstrated collaboration, not individual status.
+Trust in Apache communities is earned through consistent contribution and collaboration.
+Recognition (such as committership) reflects responsibility, not privilege or rank.
-A committer is not a privileged title, it’s a recognition of responsibility.
-Nominate and vote for new committers or PPMC members openly on the private list.
-Make sure everyone understands how merit is earned and shared.
+When adding new committers or PPMC members, conduct nominations and votes openly on the private list, ensuring everyone understands the process.
+Highlight that trust is granted through demonstrated participation and care for the community.
-Balance recognition of effort with opportunities to grow. Invite contributors to help with releases, votes, or documentation leadership.
+Aim to balance recognition with growth: when you acknowledge someone’s contributions, also create space for them to learn, lead, and mentor others.
--
== Retaining and Motivating Contributors
(training) 01/03: minor improvements
Posted by jm...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
jmclean pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/training.git
commit f7259a5a479c064a2d854d91f73f711543515957
Author: Justin Mclean <jm...@apache.org>
AuthorDate: Tue Oct 14 18:43:26 2025 +1100
minor improvements
---
.../Goverance/src/main/asciidoc/index.adoc | 30 +++++++++++-----------
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/content/Apache/Incubator/Goverance/src/main/asciidoc/index.adoc b/content/Apache/Incubator/Goverance/src/main/asciidoc/index.adoc
index 9285dcd..ed02e76 100644
--- a/content/Apache/Incubator/Goverance/src/main/asciidoc/index.adoc
+++ b/content/Apache/Incubator/Goverance/src/main/asciidoc/index.adoc
@@ -51,17 +51,17 @@ Each podling develops its own rhythm, but all must show progress toward ASF-styl
This session explains what that looks like in practice and how mentors can help guide the process.
--
-== Core Principles in Practice
-* **Community over Code** - Decisions made through open consensus
-* **Meritocracy** - Responsibility grows with contribution and trust
-* **Transparency** - All decisions visible on public mailing lists
-* **Independence** - Project can thrive beyond any one employer
+## Core Principles in Practice
+* **Community over Code** - Decisions made through open consensus.
+* **Trust through Contribution** - Responsibility grows with demonstrated participation and collaboration.
+* **Transparency** - All decisions visible on public mailing lists.
+* **Independence** - Projects can thrive beyond any one employer.
[.notes]
--
These four principles are the foundation of ASF governance.
-They are interdependent: transparency enables meritocracy, meritocracy strengthens independence, and community-driven decisions keep projects healthy long term.
-Podlings are expected to practice and demonstrate all four before graduation.
+They are interdependent: transparency builds trust, trust supports independence, and community-driven decisions keep projects healthy long term.
+Podlings are expected to practice and demonstrate all four before graduation.
--
== Decision-Making at the ASF
@@ -189,17 +189,17 @@ If any answer raises concerns, it’s an opportunity for mentoring and cultural
Self-awareness and reflection are marks of a healthy ASF community.
--
-== Summary
-* ASF governance matures through practice
-* Mentors guide, PPMC leads
-* Transparency and inclusiveness are essential
-* Healthy podlings govern themselves, *the Apache Way*
-* Graduation isn’t a checklist, it’s recognition that the community already operates as an ASF project
+## Summary
+* ASF governance matures through practice.
+* Mentors guide, PPMC leads.
+* Transparency and inclusiveness are essential.
+* Healthy podlings govern themselves, *the Apache Way*.
+* Graduation isn’t a checklist. It’s recognition that the community already operates as an ASF project.
[.notes]
--
Wrap up by emphasizing that governance is learned through doing, not documentation.
Mentors succeed when they become nearly unnecessary.
-Graduation happens when the PPMC already behaves like an ASF PMC,transparent, meritocratic, and sustainable.
-That’s what makes the ASF model so enduring.
+Graduation happens when the PPMC already behaves like an ASF PMC, transparent, trusted, and self-sustaining.
+That’s what defines a lasting and resilient Apache community.
--