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. Greg
