Interesting. Is it something we'd want to create a sub-project for eventually, or is it fine where it is?
It might be a good idea to copy a DISCLAIMER file into this package too then? On 17 October 2012 16:56, David Nalley <da...@gnsa.us> wrote: > On Wed, Oct 17, 2012 at 11:51 AM, Noah Slater <nsla...@apache.org> wrote: > > Hmm. Why bother putting the LICENSE.txt or CHANGES.txt there at all? (I > > have never had to deal with a sub-project in the root of a larger project > > at the ASF.) Is it intended to be built out of the source, and > > shipped separately? > > > > > Yes - it's a completely separate package. > It ships either as something like: > > http://jenkins.cloudstack.org/job/build-marvin-4.0/lastSuccessfulBuild/artifact/tools/marvin/dist/Marvin-0.1.0-140.tar.gz > (when not installed from source) > or potentially is available from things like pip. > -- NS
