On 3/12/12 6:09 PM, "jude" <flexcapaci...@gmail.com> wrote:
> We need the guys from Adobe to chime in and share their process, the goals,
> constraints and principles of Flex SDK development and requirements. As
> much of what they do, why they do it and how would ease the transition.
IMHO, the old Adobe process, goals, constraints and principles don't matter.
This is Apache. The goal is to get as much stuff done in as little time as
possible and improve the ecosystem of Flex.
Therefore, try not to break things, but don't waste too much time doing
stuff that computers do better like trying to compile code in your head, and
don't waste too much time on stuff that doesn't really matter. If you used
a brace on an if when you shouldn't, that doesn't really matter. I know it
bugs the heck out of some of you, but could you understand the code?
Certainly not having any comments or whitespace doesn't help, which is why
those things matter. But an extra space? Don't veto the commit, fix it
yourself if it matters to you.
>
> We can guess all we want until then (not that that's what you've done
> Justin) but if we miss things like legal clearance like you noted we'd
> suffer a setback.
I think the ASF has a process for checking the legality of all of our code
before we graduate. But when donating, I believe it is up to you to follow
the rules. Large donations require a software grant stating you have
permission. When you signed your ICLA you said you had permission to do
significant work. When folks submit patches they theoretically have checked
a box that they have the right to submit the code in the patch.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
