Hi Aditi, I think what Justin is getting at is that graduation from the Incubator is not related to the maturity of the technology, but rather the maturity of the community.
Apache is largely technology-agnostic -- the Foundation, and the Board of Directors acting on the Foundation's behalf when they oversee our projects, do not set technical direction for the projects, beyond requiring that they adhere to various policies. And thus they Incubator PMC, when evaluating whether a podling should graduate from the Incubator and be recommended as a TLP, does not care about project-specific technical milestones. Take a look at this "Apache Project Maturity Model" to see the kinds of things that the are more relevant for graduation: https://community.apache.org/apache-way/apache-project-maturity-model.html The Maturity Model is relatively new, but some podlings have started evaluating their progress against it as a step just prior to graduation, and that seems to be working out well. Marvin Humphrey On Tue, Nov 3, 2015 at 9:19 AM, aditi hilbert <[email protected]> wrote: > It’s a good point. I wondered about this esp. after the discussion we had > yesterday about next steps. How about: > > “Add configuration subsystem and interface (API) to manage and monitor > embedded devices” > > thanks, > aditi > > >> On Nov 3, 2015, at 3:24 AM, Justin Mclean <[email protected]> wrote: >> >> Hi, >> >> Looks good to me. >> >>> 2. Add support for additional micro controller architectures. >> >> Very minor. It’s a nice to have, but that's not really a requirement for >> graduation. Can we think of something else to replace it? >> >> Thanks, >> Justin >> >
