Kato implements a specification. Work on this specification is currently suspended and its future is unknown. IMHO Kato was healthy and progressing towards eventual graduation before this external problem stopped work.
Creating, reading and review reports for podlings in this unusual situation is a burden for the IPMC and the board. As Mentor, I propose that the IPMC acts to resolve this situation by winding down Kato in a way that allows an easy restart (by a simple vote) whilst preserving the legal work done in open sourcing this code base. For short, 'parking' rather than 'termination'. Robert --8<------------------------------------------------------------------------- [ ] +1 Park Kato [ ] +0 [ ] -0 [ ] -1 Do not park Kato ------------------------------------------------------------------------------ Parking ====== Aim to retain legal work and code base, allowing an easy restart if these problems are resolved. Suggested Action Items For Mentors ---------------------------------------------- * Review and commit accurate final status * Move kato.xml status to projects/parked * Update Incubator web site * Update disclaimers * Review source and create final Apache source release * Move source to read-only 'incubator/parked/kato' * Use final source release to seed repository on GitHub * Suspend mailing lists --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
