I have a BA in English and worked as a Technical Writer for a big software company (writing software manuals). If there's a need to edit and review the Wiki Pages so they present themselves as unbiased, professional, with a single voice, I'm happy to help.
On Thu, Mar 1, 2012 at 10:18 AM, Carol Frampton <cfram...@adobe.com> wrote: > Omar, > > I am sorry that this is going to sound a little snippy but would you > prefer we stop working on getting the compiler and mustella ready and work > on moving the new spark components over to apache? I'm guessing not. I > think calling it vaporware is a bit strong. I think on your chart you > should note "potential contribution" from Adobe or some such wording, not > because we wouldn't donate them but there might be others versions that > have been done in the community that people prefer to ours. > > Carol > > On 3/1/12 3 :13AM, "Omar Gonzalez" <omarg.develo...@gmail.com> wrote: > > >Hello all, > > > >I've added a page to the wiki to keep track of the current inventory of MX > >components, their Spark counterparts, and whether they are currently > >missing. This list does not take into account work that Adobe has done > >that > >is not yet donated. While it is great that there are more components they > >have either completed or have worked on the truth of the matter is that at > >this point its vaporware. Until the code is donated by someone the status > >of missing components on the status page will remain as missing. If I've > >missed any components please feel free to add them, or post to this thread > >and I'll make sure to add them to the list. Because of the nature of the > >information the list can also be used as a migration guide, and it also > >contains links to the documentation pages for each component. > > > >https://cwiki.apache.org/confluence/display/FLEX/Missing+Spark+Components > > > >-- > >Omar Gonzalez > >s9tpep...@apache.org > >Apache Flex PPMC Member > >
