Skip to content

Commit 6e38a30

Browse files
committed
added responibility and escalation
1 parent f85fb82 commit 6e38a30

1 file changed

Lines changed: 38 additions & 0 deletions

File tree

  • content/Apache/Incubator/NeutralityInPractice/src/main/asciidoc

content/Apache/Incubator/NeutralityInPractice/src/main/asciidoc/index.adoc

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -372,6 +372,44 @@ Supporting newcomers grows independence and reduces load on the dominant contrib
372372
If an entity contributes infrastructure, shared oversight prevents hidden dependencies.
373373
--
374374

375+
== Responsibility for Monitoring Neutrality
376+
* PPMC monitors openness and independence.
377+
* All PPMC members notice and surface issues.
378+
* Mentors help identify risks early.
379+
* ASF groups may provide signals.
380+
381+
[.notes]
382+
--
383+
Explain that neutrality monitoring is not the job of mentors alone; the PPMC carries responsibility throughout incubation.
384+
385+
PPMC members should raise questions early when they notice signals such as private decision patterns, unclear processes, or branding concerns.
386+
387+
Mentors provide external perspective that helps uncover issues that may not be obvious to project participants.
388+
389+
Other ASF groups like trademarks, infra, and the IPMC often detect issues indirectly during their regular work.
390+
391+
Reinforce that anyone may raise concerns, but the PPMC is accountable for understanding and addressing them.
392+
--
393+
394+
== Raising, Escalating, and Resolving Neutrality Concerns
395+
* Raise concerns on public lists with context.
396+
* PPMC reviews and adjusts processes.
397+
* Document outcomes on the list.
398+
* Escalation paths: mentors, IPMC, trademarks, infra.
399+
400+
[.notes]
401+
--
402+
Explain that concerns should be raised openly and constructively, with enough context for the PPMC and mentors to understand them.
403+
404+
The goal is clarity, not accusation: identify what happened, why it matters, and how governance can remain open.
405+
406+
The PPMC should review communication patterns, tooling choices, or workflow habits that may need adjustment.
407+
408+
Outcomes should always be written to the list so the community has a visible governance trail.
409+
410+
Escalation is supportive, not punitive: mentors for additional guidance, IPMC for broader incubation expectations, trademarks for branding issues, and infra for release or build concerns.
411+
--
412+
375413
== Mentor Toolkit: What to Check Monthly
376414
* Are decisions on list?
377415
* Is release work visible?

0 commit comments

Comments
 (0)