Hi, On Fri, Apr 6, 2012 at 12:38 AM, Alex Harui <aha...@adobe.com> wrote: > Per advice from our Mentors, I have edited the text in the “how can incubation > run more smoothly” section of the Flex report for April.
OK, thanks. I'm sorry about the infrastructure trouble you're experiencing. I guess we should signal to the board that increased funding or other means of helping the infra situation would be appreciated. On the other hand much of the ASF infrastructure is still being run on volunteer basis, so meeting them half-way or even having someone from the Flex team volunteer to become a member of the infra team could help bridge the apparent gap. Another way of dealing with issues like this could be to keep projects like Flex on existing pre-Apache infrastructure until the migration path is tested and ready. If you have access to appropriate hardware outside the ASF, my recommendation would be for you to use that until the migration issues have been solved. As long as the hardware in question is under the control of and overseen by the (P)PMC, it's fine for you to use it for development until the move to official Apache infrastructure is possible. Having development blocked because of infrastructure issues is IMHO the worst of possible options. More generally it sounds like it would be useful if we were able to involve the infra team closer with podlings that have complex infrastructure needs. That seems to have worked fairly well for OpenOffice, but less so for Flex. CloudStack mentors, please consider this as you prepare for the task ahead! Beyond the infrastructure issues it sounds like you're steadily making progress on other fronts. Please keep us posted especially about the outcome of the custom trademark deal being worked on. BR, Jukka Zitting --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
