On 3/28/12 5 :21PM, "Bertrand Delacretaz" <[email protected]> wrote:
>Hi, > >I've created http://incubator.apache.org/flex/timeline.html to >document Flex's incubation "adventure", feedback is welcome and/or >feel free to fix - I probably missed a few things. > >The idea is to focus on things that are relevant to the incubation >process, and not too specific to Flex so that other podlings or >would-be podlings can learn from our experience without getting bogged >in Flex-specific details. I am not sure if this is relevant but I've been following some of the activity on incubator_general and legal because there are two things that have me very confused and I gather from the activity other incubation projects are confused about the same things as well. 1. Apache projects only release SOURCE. Binary packages are for convenience and are not approved by Apache. You are not suppose to have dependent jars, and for us, swcs, checked into svn, even if they have appropriate licenses. I think that means a source kit by itself is not enough to build Flex although http://incubator.apache.org/guides/releasemanagement.html#best-practice-sou rce-build in the Dependencies section implies you can include them in the package even though Roy and others are quite adamant that they can not go in the source package. Somewhere in the Apache docs I read, but can't find at the moment, builds can prompt to ask permission to download optional third-party dependencies. Is the prompt always necessary or only in some cases? In our case the downloads aren't optional. Flex won't build without most of them. What about dependencies on other Apache projects? Do we have to include the source in our project since we can't include the jar or do we download the jar as part of the build? 2. I'm pretty confused about what goes into the LICENSE file and what goes into the NOTICE file and it is clear from the volume on the lists it is not just me. I know there is a lot of information out on the Apache site and the mailing lists which I keep rereading as I learn more. For example I just read on a mailing list that the LICENSE for the binary distro needs to include the source distro LICENSE and appended to that should be all the licenses for all the third-party dependencies include in the binary distro. There is also some discussion about nested dependencies. I don't think any of this is in Apache documentation. I know this stuff is 2nd nature to Roy and he is obviously frustrated we don't get it but how to do it correctly isn't that obvious. An example project with some amount of dependencies would be a huge help. I've been looking at how other projects do it but if they aren't doing it correctly that just propagates the problems. If Apache Open Office can figure out how to do it with their multiple pages of dependencies Flex should be able to do it too. Carol
