On 10/13/16, 2:42 PM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >What do you think? (yes even Alex ... I guess you can come out now ;-) >
I agree with Chris that is great to hear this feedback. Roadmaps, schedules, priorities are just plain difficult in a volunteer-driven project. As you can see from several responses, folks just run out of time. IMO, the one thing I think will help us most is getting some FlexJS apps into production. That's why Harbs and Yishay often get quicker responses from me. If anybody else can get going on trying to get a FlexJS app into production, they will also get priority on my list. Yes, it is a rough and bumpy road right now, but on the other hand, you will hopefully get better response time from the other committers on your issues, which is sort of like free engineering resources. It is true as Piotr pointed out that it is hard for me to see where the holes are since I am under-the-hood so much. I know there is agreement that documentation is lacking, but I am still not clear on what words we could write and where we could publish them that would make the biggest difference. There is no way we can quickly replace the entire body of written information about Flex, so I think we need to find the highest value information and figure out how best to publish it. So I would appreciate continued discussion on that. For those of you who responded on this thread and have time, it would help me if you can add the next level of detail by filling in the template "such as ...., that would be solved by .....", or "such as ...., but when using the Flex SDK I get unstuck by ....." In other words: "I tried to do something advanced, such as ..., but got stuck, and that would be solved by ..." or "I tried to do something advanced, such as ..., but got stuck, but when using the Flex SDK I get unstuck by ..." One more thing: The community also could use at least one more independent consultant who understand FlexJS. I've been asked twice to sit down with a company considering FlexJS and help them estimate what the porting effort would be. I can't do that without a lot of hassle due to employee agreement restrictions. Those companies have subsequently decided not to go with FlexJS because there isn't someone they can bring in to guide them through the process. Thanks, -Alex
