tree: d301f5394ab17239f4943f0a142cd76d15791dff [path history] [tgz]
  1. brand_blur.twee
  2. conflicting_mentors.twee
  3. cultural_misunderstanding.twee
  4. employer_dominated.twee
  5. heated_thread.twee
  6. lazy_consensus.twee
  7. mentor_dependancy.twee
  8. README.md
  9. release_vote.twee
  10. slient_mentor.twee
simulations/incubator/README.md

ASF Mentor Scenarios

This directory contains a collection of interactive learning scenarios designed for Apache Incubator mentors.
Each .twee file represents a branching, narrative-style exercise (compatible with Twine/SugarCube) that allows mentors to explore different approaches to real-world situations.

Purpose

These scenarios are drawn from Practicing The Apache Way.
They help mentors reflect on complex or ambiguous mentoring situations by practicing The Apache Way, which emphasizes transparency, collaboration, independence, and community-led decision making.

Each scenario presents:

  • A realistic situation based on discussions and experiences from the Incubator mailing list.
  • Multiple possible responses or actions.
  • Outcomes and reflections tied to ASF values and policies.

How to Use

You can run or adapt these scenarios in several ways:

  1. Interactive Training

    • Import .twee files into Twine and play them interactively using the SugarCube story format.
    • Use them during mentor onboarding sessions, workshops, or group discussions.
  2. Self-Study or Reflection

    • Read through each scenario to consider how ASF values apply to different outcomes.
    • Reflect on the reasoning behind both positive and negative results.
  3. Group Discussion

    • Use the scenarios in mentor meetings or office hours to prompt dialogue.
    • Encourage participants to share how they would respond and what ASF principles guide their thinking.

⚠Important Notes and Disclaimers

  • These scenarios are illustrative, not prescriptive.
    They are designed to provoke thought and discussion, not to dictate a single correct course of action.

  • Every podling is unique.
    Each community’s dynamics, size, and maturity differ, so what works well in one situation may not in another.

  • Mentors have different styles.
    Some may provide hands-on guidance, while others focus on enabling independence. Both can be valid when grounded in ASF values.

  • Podling lifecycle matters.
    The most appropriate response can depend on where a podling is in its incubation journey.
    Early-stage podlings may need more mentor involvement, while those nearing graduation should be largely self-governing.

  • Real outcomes may differ.
    The scenarios simplify real-world complexities for training purposes. In practice, decisions often require nuance and consensus.

  • ASF policies and practices evolve.
    These scenarios align with current ASF and Incubator guidelines but may not reflect future updates.
    Always verify against the latest Incubator documentation and ASF policies.

Goal

The goal of these scenarios is to strengthen mentor judgment, not to test policy knowledge.
By exploring the consequences of different choices, mentors can better understand how to:

  • Reinforce community independence
  • Model transparent communication
  • Avoid procedural shortcuts
  • Build trust and collaboration within podlings

Contributing

New scenarios are welcome. To add or modify a scenario:

  1. Create or edit a .twee file using the Twine 2 editor.
  2. Use the SugarCube 2 story format for compatibility.
  3. Follow the established structure and comment style used in the existing files.
  4. Test the story interactively in Twine before committing changes.
  5. Where possible, base scenarios on real mentoring experiences that illustrate ASF values in practice.

Acknowledgment

These training scenarios were developed with input and examples contributed by members of the Apache Incubator community. They draw inspiration from anonymized real cases and collective mentoring experience shared on the Incubator mailing list.