Author: mamsellem
Date: Tue Apr 1 11:10:47 2014
New Revision: 1583621
URL: http://svn.apache.org/r1583621
Log: (empty)
Modified:
flex/site/trunk/content/community-thirdparty.cmsPage
Modified: flex/site/trunk/content/community-thirdparty.cmsPage
URL:
http://svn.apache.org/viewvc/flex/site/trunk/content/community-thirdparty.cmsPage?rev=1583621&r1=1583620&r2=1583621&view=diff
==============================================================================
--- flex/site/trunk/content/community-thirdparty.cmsPage (original)
+++ flex/site/trunk/content/community-thirdparty.cmsPage Tue Apr 1 11:10:47
2014
@@ -1,61 +1,136 @@
-Title: Get Involved!
+Title: Project HistoryXXX
-Getting involved with the Apache Flex® Community is easy!
+The goal of this page is to document the history of the Apache Flex, starting
with Adobe
+deciding to donate it to the Apache Software Foundation (ASF), incubation and
Apache Flex becoming a top level project.
-We are an open-source community governed by the Apache Software Foundation.
Everything we do is out in the open with
-the entire community involved. All decisions are made on our mailing lists,
and all source code is developed
-within our source control system.
-
-<div class="headline"><h4>Find out what is going on</h4></div>
-If you are interested in what is going on with the project, subscribe to our
mailing lists. Our [[email protected]][1] mailing
-list is where additions and changes to the SDK are discussed. The list is
open to everybody and everybody is encouraged
-to give their opinions on anything discussed on the list. This is a great
place to introduce yourself and let us know
-how you can help.
-
-If you are interested in helping end-users of the SDK, we also host the
[[email protected]][1] mailing list. This list
-is designed for end-users to talk about how to use the SDK and how to build
applications that utilize the SDK.
-
-<div class="headline"><h4>Contributing Documentation</h4></div>
-If you are ready to help us document code, provide tips and tricks, or
anything else that is not straight-up code, we
-have a [WIKI][2] that allows for community contribution. Simply let us know
on the [email protected] mailing list
-that you wish to get write access to the WIKI. If you would like to let us
know about any blog entries, videos,
-screencasts, etc. that you have created, we would love to help publicize them!
-
-<div class="headline"><h4>Reporting Bugs</h4></div>
-All of the bugs that we are aware of are housed in the Apache Foundation's
JIRA system. You can take a look at everything
-we have in the system on [Flex JIRA][3]. To let us know about a bug, create
an issue in the JIRA system. The JIRA
-system automatically emails the dev mailing list and hopefully somebody will
take a look at it. It is really important
-that you give us as much information on the bug as possible. Even better, if
you have a way to reproduce the bug, submit
-a code sample that can help us reproduce it. Feel free to contribute to the
comments as the bug gets worked on.
-
-<div class="headline"><h4>Squashing Bugs</h4></div>
-Bugs happen, and you might know how to fix one! Because we don't allow
everybody write access to the official code repository
-(everybody has access to read, though!), there is an additional process that
has to occur to get fixes in. To help us
-squash bugs, do the following :
-
-1. Find a bug you want to work on, or submit one into [JIRA][3]. We have some
marked as "easy" if you play with the JIRA filters if you want to start with an
easy one. Make a comment on the ticket that you plan on working on it so
others don't duplicate your work.
-2. Check out the source code from GIT. More information is available on the
[Source][4] page.
-3. Setup your build environment. Check out the README included in the source
code on how to do this. You will want to make sure that you can perform a
compile before you go much further.
-4. Fix the bug. If you need help, ask the [email protected] mailing list.
I'm sure we have pointers to help you out.
-5. (optional) Run the functional test suite called [Mustella][5] on your code.
The [Mustella tests][5] are available from the ANT script, but make sure you
set it up first.
-6. Create a .patch file. If you are using an IDE, check your application
menus for this option. [SourceTree][6] has it under the Actions menu. If you
are using git from the command line, use `git format-patch <BRANCH> --stdout >
<FLEX-007>.patch` where <BRANCH> is the branch you want your patch be
merged into from whether the branch you're working on, you can omit it if the
origin and destination branch are the same and <FLEX-007>, the Jira Issue
Id relative to your patch.
-7. Attach the .patch file to the JIRA ticket you noted earlier. A committer
will review the patch and make sure it dosen't break anything else.
-8. Sit back and bask in the glory that you helped make Flex better!
-
-<div class="headline"><h4>Contributing Code</h4></div>
-Due to legal reasons, only people who have been elected as committers have
access to update or contribute code directly to the project.
-We at Apache take the legality of code seriously, and nothing would be worse
than somebody contributing code that
-they don't own and a 3rd party having a legal claim to our framework.
-
-That being said, if you are interested in contributing code, you can submit
patches to the project via [JIRA][3].
-To do this, create a new issue that describes what the code you are
contributing, and submit a .patch file with your
-code changes, just like from the bug squashing directions above. If you
submit a few patches that meet the Apache
-standards, you will probably be contacted by the PMC to get you direct access
to the GIT and for you to be recognized
-for your work as a committer.
-
- [1]: community-mailinglists.html
- [2]: https://cwiki.apache.org/confluence/display/FLEX/Apache+Flex+Wiki
- [3]: https://issues.apache.org/jira/browse/FLEX
- [4]: dev-sourcecode.html
- [5]: https://cwiki.apache.org/FLEX/mustella-overview.html
- [6]: http://www.sourcetreeapp.com/
\ No newline at end of file
+It might be useful for other similar projects, or any incubating project, as
an example of the steps involved in
+an Apache incubation.
+
+See [http://incubator.apache.org](http://incubator.apache.org) for the
official Incubator documentation, and
+in particular the [incubation process
description](http://incubator.apache.org/incubation/Process_Description.html)
page.
+
+<div class="headline"><h4> 2011: Adobe decides to contribute Flex to the ASF
</h4></div>
+
+The decision is made within Adobe to incubate Flex at the ASF. Work starts on
the incubation proposal, on explaining
+internally what this means, on the legal/IP clearance steps required to donate
the code and on recruiting
+initial committers who will help get the project started.
+
+<div class="headline"><h4> December 12, 2011: Flex Summit </h4></div>
+
+The [Flex
Summit](http://tv.adobe.com/show/flex-community-summit-december-2011) is
organized to make
+the Flex community aware of the upcoming changes, and to allow initial Flex
committers to sign up and network.
+
+Among the available videos, these two provide interesting insights on how
Apache projects work, by Roy Fielding,
+one of the ASF's founders:
+
+- [What it means to be an Apache project, part
1](http://tv.adobe.com/watch/flex-community-summit-december-2011/what-it-means-to-be-an-apache-project-part-1/)
+- [What it means to be an Apache project, part
2](http://tv.adobe.com/watch/flex-community-summit-december-2011/what-it-means-to-be-an-apache-project-part-2/)
+
+The following blog posts provide other views on the event, and show that it
was useful for the Flex community
+and for the upcoming Apache Flex project:
+
+- [Flex given to the Apache Software Foundation round-up and
opportunities](http://www.flex-tutorial.fr/2011/12/17/flex-given-to-the-apache-software-foundation-round-up-and-opportunities)
+- [Huge Adobe Partnership to Open Source Flex with Apache Software Foundation
](http://www.adamflater.net/2011/12/14/apache-flex-beginning/)
+
+<div class="headline"><h4> December 20, 2011: Incubation proposal submitted
</h4></div>
+
+The [Incubation proposal](http://wiki.apache.org/incubator/FlexProposal) is
submitted
+and
[discussed](http://mail-archives.apache.org/mod_mbox/incubator-general/201112.mbox/%3CCB14DCA2.3885F%25aharui%40adobe.com%3E)
on the incubator-general mailing list, followed after a few days (once the
+discussion dies down) by the Incubator PMC vote mentioned below.
+
+The list of incubation mentors is completed during the proposal's discussion
phase, after asking for volunteers
+when submitting the proposal.
+
+A few initial committers are also added during the discussion phase.
+
+<div class="headline"><h4> December 22, 2011: Vote for Anne and Dave as
incubator PMC members </h4></div>
+
+Project mentors need to be members of the Incubator PMC, ASF members just need
to ask to get this membership.
+
+Committers who are not (yet) Apache members need to be voted in by the
Incubator PMC, which is done
+around December 22 for Anne and Dave.
+
+<div class="headline"><h4> December 27, 2011: [VOTE] Flex to join the Apache
Incubator </h4></div>
+
+The [Incubator PMC vote](http://markmail.org/message/puo2rtrvby65lb3m)
+lasts at least 72 hours, after which whoever started it
+[tallies
it](http://mail-archives.apache.org/mod_mbox/incubator-general/201112.mbox/%3CCAEWfVJmMq390Hinafg%2Bjik8VqboYG1ixe_gnz5O2bV5q5mtKPw%40mail.gmail.com%3E).
+the vote for Flex passes on December 30th.
+
+<div class="headline"><h4> Late December 2011: Basic infrastructure is created
</h4></div>
+
+See for example the
+[INFRA-4260](https://issues.apache.org/jira/browse/INFRA-4260) (create mailing
lists)
+and
+[INFRA-4262](https://issues.apache.org/jira/browse/INFRA-4262) (create JIRA
instance)
+issues.
+
+Flex is added to the Incubator's [reporting
schedule](http://wiki.apache.org/incubator/ReportingSchedule).
+
+The [Flex incubation status
page](http://incubator.apache.org/projects/flex.html) is created.
+
+People are invited to subscribe to the new Apache Flex [mailing
lists](/flex/mailing-lists.html)
+
+Those lists are added to [flex.markmail.org](http://flex.markmail.org) for
convenience, using the markmail feedback form.
+
+Discussions and consensus building start, including clarifications about the
role of the PPMC, committers
+and community, whether to create roadmaps or just let things evolve
organically, etc.
+
+<div class="headline"><h4> Late 2011 and early 2012: User accounts </h4></div>
+
+Mentors request creation of Apache accounts for the initial committers listed
in the
+[incubation proposal](http://wiki.apache.org/incubator/FlexProposal), after
asking people which Apache ID
+they would like, avoiding collisions with [existing
IDs](http://people.apache.org/committer-index.html).
+
+Initial committers, who are also PPMC members, are invited to subscribe to the
Flex private mailing list
+(which is used for discussions about people, new committers etc. and as little
as possible besides that) and
+made aware of the [Apache guide for new
committers](http://www.apache.org/dev/new-committers-guide.html).
+
+Flex committers are granted write access to the [subversion
repository](http://svn.apache.org/repos/asf/incubator/flex/)
+and [JIRA issue tracker](https://issues.apache.org/jira/browse/FLEX) and can
start actual coding work.
+
+<div class="headline"><h4> January 17, 2012: Software grant received
</h4></div>
+
+Adobe's [software grant](http://www.apache.org/licenses/software-grant.txt) is
received by the ASF's
+secretary, the Flex code can now be imported into Apache Flex's code
repository.
+
+<div class="headline"><h4> February 22, 2012: First committer voted in
</h4></div>
+
+Justin Mclean is the first Flex committer (besides the initial committers
listed in the incubation proposal) to
+be voted in, after a short discussion and a vote on the Flex private
+mailing list, as per the [incubator's
instructions](http://incubator.apache.org/guides/ppmc.html).
+
+<div class="headline"><h4> March 27, 2012: MXMLC donation announced </h4></div>
+
+The legal/IP clearance work for that module is done on the Adobe side, that
code is ready to be donated.
+
+<div class="headline"><h4> August 30, 2012: Falcon legalities completed
</h4></div>
+
+Apache recorded Adobe's donation documents for the source code to the
next-generation Falcon compiler.
+
+<div class="headline"><h4> September 10, 2012: Falcon code committed
</h4></div>
+
+The source code for the Falcon compiler was committed to Apache's Subversion
repository.
+
+<div class="headline"><h4> December 19, 2012: Apache Flex becomes a top level
Apache Software Foundation project </h4></div>
+
+Apache Flex is voted in as a top level project at the December board meeting
of the Apache Software Foundation.
+
+<div class="headline"><h4> December 27, 2012: Apache Flex SDK 4.9 released
</h4></div>
+
+After seven release candidates Apache Flex SDK 4.9 is released as the first
release after becoming an Apache Software Foundation top level project.
+
+<div class="headline"><h4> February, 2013: Apache Flex SDK 4.9 released
</h4></div>
+
+<div class="headline"><h4> April, 2013: Apache Flex SDK Installer 2.5 released
</h4></div>
+
+<div class="headline"><h4> August, 2013: Apache Flex SDK Installer 2.6
released </h4></div>
+This version allows to track the number of downloads.
+
+<div class="headline"><h4> August, 2013: Apache Flex SDK 4.10.0 released
</h4></div>
+
+<div class="headline"><h4> October, 2013: Apache Flex SDK Installer 2.7
released </h4></div>
+
+<div class="headline"><h4> October, 2013: Apache Flex SDK 4.11.0 released
</h4></div>
+
+<div class="headline"><h4> March, 2014: Apache Flex SDK 4.12.0 released
</h4></div>
