> -----Original Message-----
> From: jude [mailto:flexcapaci...@gmail.com]
> Sent: Friday, January 27, 2012 10:02 AM
> To: flex-dev@incubator.apache.org
> Subject: Re: Port some mobile components to web
>
> Performance and memory are my top considerations for any code in the
> framework.
>
> If I submit a patch who reviews it? Does it go straight to the list?
>
>
Once we get JIRA bugs ported over (my new estimate is now Jan 31), you can
submit patches as sub-tasks to issues. The way I would like it to work is that
the issue you attach to needs to have a lot of votes and committers will be
trolling the high-vote bugs and will review your patch. And thus, you will
have to lobby others to agree that your issue is important. But I think it
that lobbying on the mailing list will be too noisy so you just need to lobby a
committer any way you see fit. And if you establish yourself as a person who
submits good patches, you can get nominated to be a committer yourself and then
you can just check in what you want (although every commit is reviewed and can
be vetoed by other committers).
Alex Harui
Flex SDK Developer
Adobe Systems Inc.
Blog: http://blogs.adobe.com/aharui
