I think it would be okay to move the Flex coding standard over to Apache. We/I updated the standard about a year ago with some changes people wanted, like allowing line lengths up to 100 chars. We didn't take the time to eliminate all the TBDs.
I will strongly advocate for 4 spaces rather than tabs. Too many apps mess up the tabs or use 8 spaces rather than 4 by default. I'm not sure I want to see existing code reformatted because it gets very hard to go back to earlier revisions and see what changed. New modules should be written to whatever the coding standard is. Bug fixes should be done in the style of the code around it. Carol -----Original Message----- From: "j...@realeyes.com" <j...@realeyes.com> Reply-To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org> Date: Thu, 5 Jan 2012 14:01:50 -0800 To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org> Subject: Re: Flex SDK code conventions > >> +1 for the coding conventions. > >I'll give that a second +1 > >> >> Although I do want to point out that the coding conventions at >> http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions are >>not >> complete and there are a lot of "TBD"'s in the document. > >I think our podling can have a Wiki right? Any legal issues with moving >over what's at opensource.adobe.com and then using that as our base? > >> >> We've been using a variant subset of these conventions (so much for >>coding >> conventions) > >Same at my company. I think the Adobe ones are a good start and with some >tweaks would make everyone happy. >> >> Other changes are tabs instead of spaces, braces alignment and a few >>others. > >Yes, tabs instead of spaces, agree. >> >> If there is a discussion being set up to discuss and finish the >>document, >> I'm willing to participate. > >So would I. > >-Jun >
