Personally, while I think Justin is more than capable to be the chair, things are running smooth right now and we do have some momentum behind us. No need to change things right now so long Alex wishes to remain the PMC Chair.
-Nick On Sun, Dec 1, 2013 at 10:49 AM, Alex Harui <aha...@adobe.com> wrote: > > > On 12/1/13 6:28 AM, "Justin Mclean" <jus...@classsoftware.com> wrote: > > >Hi, > > > >> "There's the additional rationale keeping Alex in the position as I > >>think > >> it would be less likely for folks at Adobe to assign him to some > >>non-Flex > >> position if he's the Flex PMC chair." > > > >I'd be concerned if we thought that Alex needed to be the chair for > >Adobe's continual involvement in the project. I would assume it really > >doesn't matter to them one little bit. > Definitely, Adobe should not (and does not) have such influence. Whether > I am chair or not won't affect Adobe's investment in Apache Flex. > > Right now, I can always find time to do the PMC duties since I essentially > get paid by Adobe to do it. This won't be true forever, and I never > really saw myself being chair forever. The question is more about when to > change. I was waiting to see if this thread would conjure up more folks > who wanted to take a turn as chair eventually, but Jeffry may be right > that nobody is paying attention during this long US holiday weekend. If > there were more folks interested in PMC Chair duties, it would make sense > to rotate more often. If there are only a few, should we change less > often, or just keep cycling through those few, or is that, once you've had > your turn, you can't return to the role? > > > what is important is that Alex is working on an internal project that > >uses FlexJS. But then I don't work for Adobe so that is just speculation > >on my part. > Technically, I am not working on an internal project, I am working on > Apache Flex and FlexJS which an internal project is evaluating as a way > forward. > > -Alex > >
