DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
Common Patterns Seen in Podlings
| Pattern | What It Looks Like | Why It Matters |
|---|---|---|
| Large or complex code migration | Many modules, outside dependencies, or legacy IP | Needs careful IP checks and clear updates |
| Multi-year incubation | Long time between entry and graduation | Normal for projects with legal or technical depth |
| Change from company or university control | New contributors added gradually from other places | Builds independence and continuity |
| Visible communication with IPMC | Regular updates on migration, licensing, or releases | Keeps oversight clear and supportive |
| Regular IPMC feedback loops | Mentors summarise progress for IPMC reviews | Builds shared understanding and trust |
| Sustainability planning before graduation | Shared roles and diversity visible in reports | Reduces post-graduation risk |
These patterns appear in different forms but all show practical learning of The Apache Way.
...
This table helps mentors and PPMCs discuss whether progress in complex podlings stays visible and healthy.
It is a self-review tool, not an ASF checklist.
| Area | What to Ask | Signs of Healthy Progress | Signs That Need Attention |
|---|---|---|---|
| Transparency | Are migration or IP tasks discussed on dev@? | Regular, public updates | Silence or private tracking |
| Motivation | Is progress visible despite slow releases? | Small, celebrated steps | Declining energy |
| Governance | Is leadership widening beyond sponsors? | New committers, active contributors | One company dominates |
| Communication | Is the IPMC kept informed? | Reports explain wins and blockers | Short or missing updates |
| Sustainability | Is there a post-graduation plan? | Shared roles, active mentors | Weak continuity |
| Mentorship | Are mentors visible and consistent? | Mentors guide without taking over | Silence or mixed advice |
...
Using These Case Studies
For Mentors
...