It is a bit tricky right now. What is not obvious is that there is a README.txt in the root of the source code and this the starting point for getting the source code to compile. The instructions are complete, but a bit terse, which is something that is being worked on. Another source of information is the Adobe website which does have some documentation on the structure and content of the source code.
I agree with your suggestion on improving the wiki and one thing you can do to help is to keep a journal of your findings so others can learn from your experience. Please watch the mailing lists for announcements on improvements to the "getting started" section and happy trailblazing! Brian On 4/19/12 2:41 AM, "Martin Heidegger" <m...@leichtgewicht.at> wrote: >Actually there is a flex-users mailing-list which should separate dev >talk from chit-chat. The Tasks are in the Jira - and anyways: its a Task >putting Tasks there - and they should contain the things that is >known(resources, etc.). The working environment is not yet 100% >definable because we don't have all code yet, the rest is described in >the Readme.txt. Did you read the Wiki [1] > >yours >Martin. > >[1] https://cwiki.apache.org/confluence/display/FLEX/Getting+Started > > >On 19/04/2012 16:32, איליה גזמן wrote: >> I didn't found enough info in order to join you and help. I downloaded >>the >> source code, I downloaded FlexUnit<http://flexunit.org/>, but >> >> I don't know how to use it, >> I don't know what are the tasks, >> I don't know what is the priority of tasks, >> I don't know who is doing what, and what is left for me to do, >> >> And I don't know where to ask for help beyond this form, with is not >>100% >> technical as I understood till now.. >> >> My suggestion is improve this page >> http://incubator.apache.org/flex/get-involved.html >> >> + Add steps to set up working environment. >> - Add system requirements >> + Add task list >> - add pending and approved requests for requests to do this task >> + Add skills requirements for each task, >> for instance: knowledge in c++ or just flex or may be html >> + Add relative sources for each task >> >> And may be we need another channel, to discuss non technical >> issues which some times may be impotent same if not more then technical. >> >> >
