Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1257)
Subject: Re: [OT] What are we doing here?
From: Justin Mclean <justin@classsoftware.com>
In-Reply-To: 
 <CAEFz_vuW12m+UMxmDMiCkFAz0cHouvp-z9-aTBEvPi=5B_XY+w@mail.gmail.com>
Date: Tue, 13 Mar 2012 10:41:39 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <29C76ADB-B3D6-4F19-973B-CC5F5A0B580A@classsoftware.com>
References: 
 <CAE0mPOv2rGrU=9MOAw2Eha-THXat+mkf5P8dudjO3cXjAHE5NQ@mail.gmail.com>
 <D5C621B8-89EC-4982-BFBD-84C564026938@classsoftware.com>
 <CAE0mPOuVHz-e+5T=3U4isXswaHca5_VOfR=Bn3pG2tt3HQSVgg@mail.gmail.com>
 <656A1D62-2AB4-4B79-BB76-84BAA6CCC67F@classsoftware.com>
 <172793AE-1B8A-49B0-9F65-CCAA618D2EFE@tink.ws>
 <CAEFz_vuW12m+UMxmDMiCkFAz0cHouvp-z9-aTBEvPi=5B_XY+w@mail.gmail.com>
To: flex-dev@incubator.apache.org

Hi,

> We probably need a list of requirements, such as does it have ASDoc, =
comments, unit tests, Mustella
> tests, etc.

Here's a list I've been working on - it still needs more work.

1. Does the submitted code fill a need for users of the SDK?
Could the code better exist as an optional component? Ask yourself does =
it need to be part of the SDK at all?

2. Can the code be legally donated?
Any there any IP issues with the code? eg If it was contributed by a =
full time employee do you have permission to donation the code?
Has the contributor signed a CLR?

3. Is it backward compatible with the existing SDK.
If not what are the reasons and is there a clear well documented =
migration path?

4. Has the code been reviewed?
Is the code at least the same quality as existing code in the SDK?
Has feedback been provided on the mailing list?
Have any outstanding concerns or issues been resolved?
Has a consensus been reached?
Any outstanding structural or architectural issues? Have these been =
documented?

5. Are there any performance issues with the code?
Is performance measurably better or worse?

6. Is the code formatted according to the Flex SDK code style?
Do all files have the Apache header?

7. Are all of the properties and methods documented in same way as =
methods and properties in the Flex SDK?
Can ASdocs be generated from the code?

6. Can the classes be easily extended if needed?

5. Does the code work on desktop, browser and mobile?

8. Are there working examples showing how the code can be used?

9. Is the code fully unit tested and can those tests be easily run?

10. Have all locale and globalisation issues been addressed?
Has the code been localised to the standard set of Flex SDK locales?

12. Do the class names and name spaces fit in with the he existing SDK?
Should the code use an existing package name or a new package name?
What framework project should the code be added to?

13. Have the manifest and build scrips been updated?

Probably need something added about accessibility, events, styles and =
skins to the above.

What do we put for Flash player and Flex version  numbers in method =
headers? Do with go with 10.2 and Apache Flex 4.8 or something else?

Thanks,
Justin