And it is official, the Apache Secretary has filed the donation paperwork. Apache Flex now "owns" all of the content below. (Apache doesn't really own it, but rather, has a license to it).
I recently found out that post-graduation donations from Adobe were not handled properly by the Flex PMC. We have to get Incubator approval for all post-graduation donations so I can't just dump all of these files into our repo. So, over the course of the next several days/weeks, I will be scrubbing this donation to double-check on headers, etc, and asking for Incubator approval before they go into the repo. I will probably do this in chunks instead of one giant pile of files. I also have to do this for the BlazeDS files. To me, this is not top priority. The FalconJX/FlexJS releases are top priority along with a 4.12.1 and releasing Installer 3.0. And 360|Flex prep also takes priority over donation scrubbing. Once approved, the BlazeDS files will go into its own repo, but everything in this donation will go into the flex-utilities repo, unless someone has a better idea. Even the ADC html files until they get re-branded, unless those of you who work on our website want to see them in our site's SVN. Thanks, -Alex On 3/28/14 8:42 AM, "Alex Harui" <aha...@adobe.com> wrote: >Hi folks, > >Adobe legal and business folks have approved the donation of several >Flex-related items to Apache. The donation paperwork is on its way to get >VP signature (yes there could be some delay or reversal there, but I don't >expect any), but I'm bringing this up now because we should start thinking >about how to handle the contents of the donation. > >In the donation is: > > >1. Several Flex articles from the ADC web-site. >2. An updated version of the FDB debugger that contains support for >ActionScript Workers >3. The FlexPMD source code >4. The Mobile Trader demo application >5. The specification for the MXML language >6. An XML merging utility source code from the Flex QA team. >7. The Squiggly spell-checker source code >8. The Tour De Flex application source code >9. The source code for a prototype of a code coverage utility that I >wrote. > >Links to the original Adobe content is at the end of this email. When you >go to the Adobe links you see a complete web article, but when donated, >several things will be missing and several things will need adjusting >before hosting the content at Apache. > >A) None of the videos in the VideoTraining article are being donated >because the videos are heavily branded by Adobe "watermarks". Adobe says >our version of the article can link to the Adobe videos, but Apache does >not want us to host Adobe videos on Apache servers. At some point in >time, I will try to get these videos posted on YouTube so we don't have to >worry about them being taken off of Adobe servers someday. Adobe Legal >has ok'd posting the videos on YouTube, but I need to get some other >approvals before doing it. We also need to get approval from Apache to >link to the Adobe-hosted videos in the interim. We have approval to link >to them when posted on YouTube. > >B) All of the devnet articles load Adobe CSS files. Our version of these >articles should not look exactly like the Adobe colors so we need to >create our own CSS file and adjust the articles to load those CSS files >instead. I am not the right person to do this work, so a volunteer is >needed. > >C) The Adobe icon and all head shots of authors are not being donated. >The Apache version of these articles should not link to the head shots on >the Adobe servers. > >D) The articles have sidebars and footers that point to lots of other >Adobe content. Those sidebars and footers should be removed/replaced. > >E) Not all of the Tour De Flex content is being donated. Both TDF3 and >TDF4 source code is in the donation, but articles written by non-Adobe >authors are not in the donation. TDF will need to be adjusted to not >reference the missing articles. The non-Adobe authors need to be >contacted to donate their article to Apache. > >F) Other videos and images used in examples are missing from TDF and >devnet articles if they were of real people or third-party brands. We >will need to generate replacements, or adjust the articles to work without >the missing videos and images. We will have to be careful as the articles >may still point to the Adobe-hosted videos and images. > >G) Some articles point to zip files. In the donation, the zip files are >expanded and the actual zip file is missing because we should be checking >source and not zips into our repos. Build scripts will be needed to >create zips that go with the production articles. > >And then we need to decide where to still all of this source. I guess >flex-utilities for most of it. I would probably create a branch of >flex-sdk for the FDB code. The XML Merge code will go in the BlazeDS repo >with the rest of BlazeDS. Where should be put all of the devnet html >files until they are ready? > >Thanks, >-Alex > > >Here are links to the ADC articles: >http://www.adobe.com/devnet/flex/videotraining.html > >http://www.adobe.com/devnet/flex/testdrive.html > >http://www.adobe.com/devnet/flex/testdrivemobile.html > >http://www.adobe.com/devnet/flex/articles/mobile-development-flex-flashbui >l >der.html > >http://www.adobe.com/devnet/flex/articles/flex3and4_differences.html > >http://www.adobe.com/devnet/flex/articles/itemrenderers_pt1.html > >http://www.adobe.com/devnet/flex/articles/employee-directory-android-flex. >h >tml > >http://www.adobe.com/devnet/flex/articles/mobile-skinning-part1.html > >http://www.adobe.com/devnet/flex/articles/flex-mobile-performance-checklis >t >.html > >http://www.adobe.com/devnet/flex/articles/flashbuilder_blazeds.html > >http://www.adobe.com/devnet/flex/articles/spark_layouts.html > >http://www.adobe.com/devnet/flex/articles/flex-mobile-development-tips-tri >c >ks-pt4.html > >http://www.adobe.com/devnet/flex/articles/flex4_skinning.html > >http://www.adobe.com/devnet/flex/articles/flex4_viewport_scrolling.html > >http://www.adobe.com/devnet/flex/articles/flex4_effects_pt1.html > >FlexPMD is currently on Open@Adobe here: > >http://sourceforge.net/adobe/flexpmd/home/Home/ > >The Mobile Trader demo application is described here: >http://www.adobe.com/devnet/flex/samples/mobile-trader-application.html > >And here: http://coenraets.org/blog/2011/03/flex-on-the-ipad/ > >The XML merge utility is a small set of files that should have been in the >BlazeDS donation > >Squiggly is described here: > >http://labs.adobe.com/technologies/squiggly/ > >Tour De Flex is described here: > >http://www.adobe.com/devnet/flex/tourdeflex.html > > > > > > > > >
