Looking back over the email trail, it seems that there is some confusion as when certain projects need to report. ManifoldCF, for instance, was asked to report monthly for approximately the first year (or was it six months?). After that we received report notices every three months: March, June, September, and December. We've been responding to report notices when we've received them and we just reported in September. We received no notice in October and did not expect one. It appears that many of the other projects you listed are in a similar situation.
Can you please clarify what our responsibilities in fact are, as far as you understand it? If we are once again expected to report every month, we'd appreciate receiving appropriate notification to that effect. Thanks, Karl -----Original Message----- From: ext Noel J. Bergman [mailto:n...@devtech.com] Sent: Tuesday, October 18, 2011 1:06 PM To: general@incubator.apache.org Subject: Projects failing to repoirt for October - appropriate actions? On most months, I have to chase down missing reports. ETCH, HAMA, HCATALOG (managed to do a release, though), KATO, MANIFOLDCF (also managed to do a release, though), RAT and WAVE all failed to report this month. RAT was discussing graduation, but still needs to report. Two others were active enough to put out releases, but failed to report. Wave has been active enough to discuss their next steps, but failed to report. What should be done with these projects? Which one(s) should be retired? --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
