On 8/7/12 3 :29PM, "Greg Reddin" <gred...@gmail.com> wrote:
>On Tue, Aug 7, 2012 at 1:22 PM, Alex Harui <aha...@adobe.com> wrote: >> While that¹s fine for the vast majority of users that are just >>consumers of the SDK, my question is about the committers and other >>folks who want to make changes to the SDK. Is there any Apache policy >>that requires committers to have ³clean² source code layouts such that >>no non-compatible licensed files are mixed into the source tree? Or do >>folks just have to be careful that they don¹t accidentally modify or >>check in something they shouldn¹t? > >Apache can't control what committers do with the code once they check >it out to their machines. If they want to fold non-compatible code >into the tree they checked out they can -- so long as they don't >commit any of it back to the repo. > >I think we need a better story for this though. It seems dangerous to >me to have a working copy of a source code tree with stuff folded into >it that you don't want to commit. How hard would it be to set up some >svn:ignore properties for the files that get folded in? Is that enough >to ensure they don't get committed (at least that would ensure they >don't get committed by mistake without some kind of warning)? That's >basically what we do with Maven projects to keep from checking in the >target directory, for example. There are lots and lots of files since it is the entire AIR SDK plus some other stuff. At Adobe most of the files were ignored but I haven't done that in this repository since I don't intermix files and I want to see which files are there which aren't Apache files. Unless the files are "added" to svn they won't get committed. "svn status" is always your friend. Carol
